July 12, 2009 at 10:04 am
Comments posted to this topic are about the item Restore Database from network location
July 24, 2009 at 4:01 am
True you can use a UNC path in a scripted backup \ restore as per the example given, but you can also use UNC paths within Enterprise Manager or Management Studio too. You don't need to use a script if you don't want to.
Although only local drives on the server appear within the selection of backup \ restore locations within the GUI, you can simply type the full UNC path (excluding file name) into the path box, and the file name itself in the second box.
One good gotcha to watch out for is to ensure that the account used to run the SQL Server services is a domain account as opposed to a local system account. Otherwise the share will not be accessible.
Also, said domain account will need permissions to access the share where the file is housed \ to be written to.
July 27, 2009 at 3:27 am
The other point to consider is whether the backup file was compressed by Sql Server (Enterprise/Dev edition only). If not, depending on the computing power available and the capacity/capability of the link, it may be quicker to zip/transfer/unzip/restore.
May 11, 2010 at 8:38 am
Andy Hogg (7/24/2009)
True you can use a UNC path in a scripted backup \ restore as per the example given, but you can also use UNC paths within Enterprise Manager or Management Studio too. You don't need to use a script if you don't want to.
Agreed. I've set up backup plans in both that backup to a network location rather than the local machine. Probably not recommended if you have 200Gb database backups, but the sort of database backup sizes I've generally been dealing with (less than 3Gb) haven't ever had an issue.
May 19, 2016 at 6:59 am
Thanks for the script.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply