Restoring 2003 Server with Registry
Updated: 21 May 2010 | 4 comments
I have a server which I am currently trying to recover from tape, I have a full backup with System State and Shadow Copy Components. I have done a full restore to my new systems which is defined under my user defined section ..The server appears to fully restore with no problem but when I login to the new system none of the registry components are there, the machine still has the same name, same IP address and none services are coming over. Is there an option i am missing during the restore ...I am not sure what i am missing here ..
Thanks
John
discussion Filed Under:
Comments
Couple of technotes for
Couple of technotes for you
• HOWTO: Use NetBackup to perform a restore for a total and complete recovery of Windows XP, 2000 or 2003 client(s) that includes C: (and other system) drive(s), Shadow Copy Component, and/or System_State from a reliable full Windows-NT backup without IDR or BMR in the event of a Disaster (or need to fall back to a known working state).
• During a System_State restore, not all of the registry keys are recovered, causing the system to go into a reboot cycle.
In order to change this default behavior, it will be necessary to run the w2koption. This is an executable that is included with NetBackup. This set of instructions assumes that the restore is going to a PC with exactly the same hardware as the PC that contains the backup information.
Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.
• If this provides help, please vote or mark appropriate solution.
Not Original Machine
So if I want to perform the restore to another machine, including the system state ... as the orignal machine and hardware is no longer available ... From the Redirect windows I enter the following
computername\System?State
This still did not work .... can a restore be down when using a redirect ...including the registry ..
I apologize .... but the version I am using is BackExec 10d
Thanks
This is usually a NetBackup
This is usually a NetBackup forum.
Can I be so bold as to suggest that you might get a better response if you were to re-post your query in the BackupExec forum?
Good luck.
I am having the same
I am having the same problem. I am using NetBackup 6.5.3. I had a DC that crashed today. The DC is a Windows Server 2003 x64 bit. I followed the exact directions below given in the HOWTO and also the "During a System_State restore..." document. I mean, I followed those directions perfectly. I ran the w2koption before I started the System State restore, restored System State (which restored successfully) and then ran the w2koption again after the System State restore. I then rebooted the machine as directed by the documents, and now the server is still stuck in a reboot loop. I cannot access the desktop via Safe Mode or Last Known Good Config...following both sets of directions led me to no where and now I am back to sqaure 1 where I am looking at having to install the OS again. Any other ideas to follow than just these two documents below? By the way, I restored the C:\ and System State (Shadow Copy Components) to the ORIGINAL hardware, so following the w2koption was a must to run. Please HELP! Any ideas are greatly appreciated!
***
Yvonne
• HOWTO: Use NetBackup to perform a restore for a total and complete recovery of Windows XP, 2000 or 2003 client(s) that includes C: (and other system) drive(s), Shadow Copy Component, and/or System_State from a reliable full Windows-NT backup without IDR or BMR in the event of a Disaster (or need to fall back to a known working state).
• During a System_State restore, not all of the registry keys are recovered, causing the system to go into a reboot cycle.
In order to change this default behavior, it will be necessary to run the w2koption. This is an executable that is included with NetBackup. This set of instructions assumes that the restore is going to a PC with exactly the same hardware as the PC that contains the backup information.
Would you like to reply?
Login or Register to post your comment.