Hi Everyone, Vivek Kumar here from the Data Protection Manager (DPM) support team. DPM 2010 comes with Bare Metal Restore (BMR) capabilities that are much talked about and have helped us in many of our crucial disaster recovery scenarios. Many of my friends have talked about backup and restore process for BMR and you can read more about it here:
Data Protection Manager 2010 and Bare Metal Restore - http://blogs.technet.com/b/dpm/archive/2011/11/01/data-protection-manager-2010-and-bare-metal-restore.aspx
Performing a Bare Metal Restore with DPM 2010 - http://blogs.technet.com/b/dpm/archive/2010/05/12/performing-a-bare-metal-restore-with-dpm-2010.aspx
Deciding between System State Backup and Allcritical Backup in Windows Server 2008 - http://blogs.technet.com/b/filecab/archive/2009/05/04/deciding-between-system-state-backup-and-allcritical-backup-in-windows-server-2008.aspx
Below are some of the questions that some of my customer have inquired about while protecting BMR data along with the answers:
NOTE This article applies only to Windows Server 2008 R2 and DPM 2010 and above
Q: When we perform a BMR backup, why don’t we see the data transfer rate in the monitoring tab in the DPM console?
Answer: We don’t see the data transfer rate as BMR backups are using WSB (Windows Server Backup) and we cannot show you the data transfer rate of the WSB thread. We only show you details of DPMRA under monitoring.
Q: We have applied network throttling for a server but our BMR backup doesn’t get throttled. Why is that?
Answer: Bandwidth Throttling is a network related feature (Controlled by QOS) that gets applied on DPMRA and WSB is independent of it, so the rule applied for bandwidth throttling on DPRA won’t be applied on WSB (this is expected behavior). For more information on this see http://technet.microsoft.com/en-us/library/cc161325.aspx.
Q: I restored my BMR backup to a share but why doesn’t the WSB console recognize it?
Answer: This is a key recommendation. When you restore the BMR backup to any drive, you need to restore it to the root of the drive so that the WSB console can recognize it. If it’s under a folder then WSB won’t be able to discover it. For example, you will want to put it in D: or E:, not in D:\Restore\Date, etc. For more information on this see http://technet.microsoft.com/en-us/library/cc731602.aspx#BKMK_no_disk.
Vivek Kumar | System Center Support Engineer
Get the latest System Center news on Facebook and Twitter:
App-V Team blog: http://blogs.technet.com/appv/ ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ DPM Team blog: http://blogs.technet.com/dpm/ MED-V Team blog: http://blogs.technet.com/medv/ Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ Operations Manager Team blog: http://blogs.technet.com/momteam/ SCVMM Team blog: http://blogs.technet.com/scvmm Server App-V Team blog: http://blogs.technet.com/b/serverappv Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/ The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
I always recommending before any disaster happens to run a backup test first so you can see how long it can take.