Thanka to all who replied.

What we've found is that we get our best bang for the time by performing a native back up locally and then moving it across the LAN to the new DB Server and doing a native DB restore as opposed to using Microsoft's DPM2012 (Data Protection manager 2012). The IT Admin is not sure why DPM takes so much longer to do a DB restore then it takes to move a backed up copy of the Db between servers and then restore it but it does. DPM is almost twice as long to use versus native SQL Backup & Restore.

DPM however does have 2 key advatanges that make it the preferrred recovery method for normal day to day use (as oppose dto a one time relocation of the DB between servers) and they are

(1) Space - DPM does not require a copy of the DB (backed up) be placed on the SQL Server locally before restoring the DB.

(2) Real Time Recovery Availability - DPM is always ready to restore the DB where as the native process require we get a backup foirst and then move it, restore it and then dump the copy of the bak file.

Thanks to all who replied.