This is a procedure that has been reported to allow you to perform a full bare metal recovery on a Windows 2003 server. Note that these directions have not been widely tested at all, so be very, very careful in relying on them! There is no guarantee that they work at all, let alone in your environment! At a minimum, you should test them out on a test system before you even think about relying on them. Also, there is a interesting wiki documentation project called Baculapedia (for reference), at: http://bacula.neocodesoftware.com
In order to create a suitable backup, you need a ClientRunBeforeJob script. It should create a system snapshot, and shut down any services that are not safe to back up. This example will create the backup in d:\backup\server1\system_state_Backup.bkf
rem Create a system state snapshot using the built in ntbackup utility. ntbackup.exe backup systemstate /J "SERVER1 Backup" /F "D:\backup\server1\system_state_Backup.bkf" /R:yes /L:f /SNAP:on rem Stop any services required to ensure a consistent snapshot of their data. net stop FirebirdGuardian net stop "File Server"
An accompanying ClientRunAfterJob should restart any suspended services.
net start FirebirdGuardian net start "File Server" rem etc.
An ASR set should periodically be manually created and included in the backup. This requires running ntbackup.exe, selecting advanced mode if it starts in Wizard Mode, and selecting the Automated System Recovery wizard.
An ASR set contains a backup of your operating system files and a bootable floppy disk that can be used to start your computer if it will not start normally. Before creating an ASR set, make sure that you have a 3.5-inch floppy disk available to make the boot disk. If your server does not have a floppy drive, you can still perform an ASR backup by copying the asr.sif and asrpnp.sif files located in the systemroot \repair directory to another computer with a floppy drive, then copy those files onto a floppy disk. However, before running the ASR restore procedure, you must attach a floppy drive to your server.
Before beginning of restoration bare-metal you must have:
Support Tools, and Resource Kit Tools.
and asrpnp.sif.
Assuming that you are not installing on identical hardware, ensure that the replacement system
During carrying out of emergency restoration (ASR) operational system:
First you must create a working copy of Windows on the new system. This can typically take 30 to 90 minutes.
This will require the following files, from Bacula, the system state snapshot, and the ARS set:
At this point, the ASR Wizard should complete installation based on the system recovery files and automatically reboot.
Now that the server is in a minimally functional state, you can begin reloading the last known good system state and user data.
You will want to install the Support Tools and Resource Kit Tools to help in troubleshooting.
One problem you may run into is the File Server service does not start, or starts with errors, due to numerous missing files. This is typically because while the OS has been restored via ASR, none of the user data has been restored yet. Things should start working properly again once the full restore and reboot has been completed.
If for some reason you do not have a good ASR floppy set (ie, the floppy media failed), you can still recreate the appropriate boot floppies if you have the data files backed up elsewhere.
On a functional system, restore the relevant ntbackup archive file. From this archive, you should be able to restore the asr.sif and asrpnp.sif files, and copy them over to a floppy set. This floppy set should then function as the original.
If the Event Log Application contains
Source: MSDTC Type: Warning Category: SVC Event ID: 53258 Description: MS DTC could not correctly process a DC Promotion/Demotion event. MS DTC will continue to function and will use the existing security settings. Error Specifics: %1
Source: MSDTC Type: Error Category: Tracing Infrastructure Event ID: 4404 Description: MS DTC Tracing infrastructure: the initialization of the tracing infrastructure failed. Internal Information: msdtc_trace: File: d:\srvrtm\com\complus\dtc\dtc\trace\src\tracelib.cpp, Line: 1107, StartTrace Failed, hr=0x80070070
Source: Userenv Type: Error Event ID: 1058 Description: Windows cannot access the file gpt.ini for GPO CN = {31B2F340-016D-11D2-945F-00C04FB984F9}, CN=Policies, CN=System, DC=test, DC=net. The file must be present at the location <\\ test.net \sysvol \test.net \Policies \ {31B2F340-016D-11D2-945F-00C04FB984F9} \gpt.ini>. (The network location cannot be reached. For information about network troubleshooting, see Windows Help.). Group Policy processing aborted.
or also
Source: Userenv Type: Error Event ID: 1030 Description: Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.
A full description of the solution is contained in article Microsoft #842804 at http://support.microsoft.com/?id=842804 . Be sure that:
Domain Controllers Policy.
http://support.microsoft.com/kb/814583/en-us
© 2006 Yuri Timofeev