Microsoft Office Tutorials and References
In Depth Information
Bare Metal Backup and Recovery
5.
Now go ahead and start the System State recovery using the
following command:
wbadmin START SYSTEMSTATERECOVERY -version:<Version identifier>
-backupTarget:<\\server\sharename> -machine:<SERVERNAME THE
SYSTEMSTATE WAS TAKEN FROM>
Bare Metal Backup and Recovery
Imaging a server creates an exact copy of a live machine for a complete backup,
this is like taking a picture of that server. This allows you to restore the server
back to its current state in the event of total failure. Server imaging provides very
comprehensive data protection. In many IT departments today imaging of servers is
a common practice because of its reliability and ease of restores. In recent years Bare
Metal Backup and Recovery has become a very popular added feature of imaging.
Microsoft has its own imaging tools and with DPM has added a solid BMR solution.
We are going to discuss BMR in more detail and show you how this is done in DPM.
What is Bare Metal Backup and Recovery?
Bare Metal Recovery is needed in the event of a server disaster. BMR is similar to
imaging servers. It can restore the entire system including the operating system, any
applications and all the data. BMR typically only protects the operating system drive
by default. This means if your server has multiple disks you will need to protect the
data on those drives as well. It is also similar to System State in that it contains the
components needed to get the operating system. The key difference between imaging
a server or having the System State backed up on a server is that BMR can restore
like an image but to dissimilar hardware. This means you can take the BMR and
restore it on an entirely different hardware platform from the platform the server
was originally running on.
This is key for administrators because if your server dies you might have extra
hardware around but it is not the same type of hardware. Before BMR if you tried to
restore on dissimilar hardware you would get the blue screen of death with errors.
That was because of the HAL (Hardware Abstraction Layer) differences between the
hardware platforms. Before BMR you would have needed to rely on System State
and the restore does not always work; restore is also a time-consuming process. With
BMR if your server dies and you have a different piece of hardware you can restore it
if the hardware can handle your server.
 
Search JabSto ::




Custom Search