BESR 2010 DR test

This doesn't sound very good.  I have a similar setup to yourself with SBS running as a Virtual guest in hyper-v.

I have BESR 2010 installed on both the host and the SBS and back both up.

Restoring the vhd on the host seems to work well, but I can't seem to find out if it sets the flag for AD to show that it has been restored and needs to update from the other domain controllers and not perform a rollback.

I haven't tried restoring the SBS by booting from the recovery cd yet.

As your hardware is different, then you would need to use the restore anywhere option.

Did you use the VSS option when backing up the SBS??

I never used the VSS option when creating the one time backup. Yes my hardware is different, but the restore anywhere option would result in a restored server that has no taskbar, no right-click, no nothing, just a SBS Console window. If I restored without the "restore anywhere", then the restore would work, just had the problem with AD authentication. I spoke to a Symantec technician, who said that the restored virtual guest would have a different SID to the original and since I had only backed up the virtual guest and not the host, it would not work. He said I would need to refresh the SID's on AD, but couldn't explain how and that I should take that up with MS.

So new plan, remove BESR 2010 from the virtual guest and install on the host and try again. If that's unsuccessfull, then try MS Data Protection Manager 2010.

Right,  In order to properly backup a sbs, you must use the VSS so that it correctly backs up Sharepoint, Exchange, Active Directory.......... and so on.

I finally did get around to testing out some restore options in hyper-v.

First method was to boot a vm with the restore cd. 

Issues

It wouldn't recognise the VM Bus Network adapter, but would recognise the legacy network adapter. I installed all the original VM Bus Adapters and a legacy adapter to allow me to map a drive during the restore.  Even creating a custom iso did not solve this.

Tthe mouse doesn't work as the integration drivers are not installed until the system is restored.

The system did restore correctly and after the reboot, I removed the legacy adapter and reran the connect to the internet wizard.  All previously joined clients were able to connect to the sbs without having to be rejoined.  The only thing I didn't test was replication with the other production domain controllers as I would still like verification that it won't perform a usn rollback.

Method 2 & 3 - Only if you backup the host as well

On the SBS, I run the standard SBS backup as well as BESR 2010.  I also backup the host with BESR 2010 (must also use VSS so that it is hyper-v aware).

Restore the vhd file and attach it to a new vm

Copy the backup files to another vhd (either sbs backup or besr 2010) and attach this the the new vm.

Boot the SBS with no network connectivity (this will prevent it from performing a usn rollback if you have additional domain controllers)

Restore the system from the backup files - (system state for SBS Backup or full recovery for BESR 2010)

Hope this makes sense. 

Would love to know about DC restores with BESR, but will just stick with performing an additional system state restore using ntbackup to be 100% safe before rejoining it to the network.

Are you restoring SBS 2003 or 2008?

Moving BESR 2010 to the host this weekend and then will perform a full host and vm backup. Will then test this on the other server.

Its SBS 2003.

Think the key is to use full VSS backup option on both.