Some time ago, someone contacted me regarding configuration data he lost during cluster disk migrations. Apparently he performed a wrong action whereby all the share information was lost. It should be quiet easy to recreate them, but the customer had no documentation or whatsoever about it.
So there was only one solution… trying to restore the system state of the server to another location. During this process we came across with the issue that share information of a cluster is not stored in the “normal” location.
In previous versions of clustering, the cluster service maintained cluster file share information in the registry key HKLM\System\CurrrentControlSet\Services\LanmanServer\Shares. (source)
As of Windows 2008, those shares are stored in the cluster resources within the registry. For Example: HKLM\System\Cluster\Resources\…
Basically registry data is stored in files. Those files can be found in the following locations:
- For SYSTEM, SAM, COMPONENTS, SECURITY, etc. : C:\Windows\System32\config;
- For CLUSDB : C:\Windows\Cluster;
Below is a procedure how you can obtain your configuration data again with minimal impact on the environment.
In the Backup Exec 2012 console go to “Backup & Restore” and select the server of which you would like to restore the registry files. In the ribbon, you can select “restore“.
On the next screen select “Active Directory, ADAM/AD LDS, and/or System State“.
In the backup navigation pane, browse to the backup session you like to restore.
Select the option to restore the data “to a different location“. In my case I created a folder on the C-drive.
Afterwards collect the data and move it to a test server and mount/load (File > Load Hive…) the files in the registry. During this process, you’ll need to give this loaded hive a name. Mostly I choose something like RESTSYS or RESTCLUSDB.
Now you have the ability to browse to the configuration data you would like to restore. In my case I performed an export of the configuration data to file (*.reg) and performed a find&replace of the key location. Once done, I just needed to import the *.reg file and restarted the server again. If you do not have the ability to reboot the server, you can always opt to restart the server service… But this will also haven an impact on the operational state (hick-up) of your system. If you don’t have the ability for planing downtime, a manual recreation is necessary.
I hope this helps!