Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Backing Up/Restore to non-local drive Expand / Collapse
Author
Message
Posted Wednesday, September 5, 2012 10:06 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Monday, July 21, 2014 9:59 AM
Points: 886, Visits: 1,544
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.


Kindest Regards,

Just say No to Facebook!
Post #1354719
Posted Thursday, September 6, 2012 5:32 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Yesterday @ 7:36 AM
Points: 76, Visits: 213
I agree with tim.cloud that you should have a backup drive attached to your database system.

I normally set up the following when creating new SQL server
C: for OS ~ 60GB (nothing else on this than primary and shared SQL stuff)
D: allways CD or DVD drive
E: Datafiles (ask or check initial size, annual growth and usage before deciding size and RAID)
F: Logfiles (I choose 1,5 times the size of calculated Datafiles, at least RAID 5)
G: backup (I choose at least 2 times the size of calculated Datafiles)

Considerations has to be made of instances, Analyzing Services and such, depending on how many drives one should have.
There is also on heavily loaded system sometimes a need for a TEMPDB drive.
Post #1355227
Posted Thursday, September 6, 2012 9:50 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Yesterday @ 5:46 PM
Points: 235, Visits: 981
EXEC xp_cmdshell 'net use v: \\ServerName\foldername'


Here we are assigning V as drive letter to the \\ServerName\foldername'

-----------------------------------
BACKUP DATABASE [XYZ] TO
DISK = N'v\xyz.bak'
WITH stats = 10, format
Post #1355441
Posted Friday, September 7, 2012 3:32 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 3:28 AM
Points: 1,629, Visits: 5,567
Sqlism (9/6/2012)
EXEC xp_cmdshell 'net use v: \\ServerName\foldername'


Here we are assigning V as drive letter to the \\ServerName\foldername'

-----------------------------------
BACKUP DATABASE [XYZ] TO
DISK = N'v\xyz.bak'
WITH stats = 10, format


What's the point of mapping the drive letter? SQL will back up to the UNC path quite happily provided the permissions at both ends are set up properly (and if they're not properly configured, mapping the drive isn't going to help anyway). Mapping the UNC path as a drive letter doesn't make the network more reliable or faster in any way, so it's still not the best idea unless you're dealing with relatively small databases (a few gigabytes, maybe).
Post #1355865
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse