| Author |
Topic |
|
jparker
Posting Yak Master
118 Posts |
 Posted - 2005-05-17 : 08:50:23
|
| I wish to run a scheduled backup under SQL Server 2000 -> SQL Server Agent -> JobsIt works fine backup up to my local disk yet when I put in a mapped drive as the destination it doesn't work and the task fails. Any ideas?E.g.BACKUP DATABASE [sample_database] TO DISK = N'V:\mybackup\drbackup' WITH INIT , NOUNLOAD , NAME = N'DR backup', NOSKIP , STATS = 10, NOFORMAT |
|
|
AndyB13
Aged Yak Warrior
583 Posts |
Posted - 2005-05-17 : 11:09:38
|
Have a look at this article[url]http://www.sqlteam.com/item.asp?ItemID=408[/url]Probably best to back up locally 1st then do a copy to the network serverAndyBeauty is in the eyes of the beerholder  |
 |
|
|
SreenivasBora
Posting Yak Master
164 Posts |
Posted - 2005-05-17 : 18:09:32
|
| Copy it in the local disk and again copy into Network drive is very round trip process.Create a Device like TestDB_Device which maps to network drive and use the device for backups.Ex: BACKUP DATABASE TestDB TO TestDB_Device WITH INITWith RegardsSreenivas Reddy B |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2005-05-17 : 18:23:17
|
| It might be a very round trip process, but it is A LOT more reliable than direct network backups. I've had numerous instances where packet loss or some other minor network hiccup corrupted a backup file. I've never had this problem backing up to a local disk and then copying the file to a network drive. Your mileage may vary, but unless you absolutely have no choice I'd recommend doing the local backup and copy.Also, DO NOT use mapped drive letters, always use UNC paths. Drive letters are relative and not 100% consistent. |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-05-17 : 19:36:16
|
quote:
Originally posted by robvolk
It might be a very round trip process, but it is A LOT more reliable than direct network backups. I've had numerous instances where packet loss or some other minor network hiccup corrupted a backup file. I've never had this problem backing up to a local disk and then copying the file to a network drive. Your mileage may vary, but unless you absolutely have no choice I'd recommend doing the local backup and copy.
What about turning on backup verification? |
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2005-05-17 : 21:07:08
|
| A verfied backup can still be corrupted and unrestorable, I've had plenty of those too. |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-05-17 : 22:04:38
|
quote:
Originally posted by robvolk
A verfied backup can still be corrupted and unrestorable, I've had plenty of those too.
that verification code must totally suck then. I'm afraid to even take a backup now!-ec |
|
|
|
kish
Starting Member
45 Posts |
Posted - 2005-05-18 : 08:18:52
|
| I dont agree. I have been using network backups since last 5 years now. If you have a good network infrastructure, you should not been having problems. Packet loss are all a cause of unreliable networks. This could also effect your OLTP server if you have such network issues.--Kishore |
|
|
|
cyblue
Starting Member
1 Post |
Posted - 2006-03-07 : 17:46:45
|
| Sorry for digging up the old post, but I found this post on a search. So for anyone else stumbling across it as I did, I believe the answer is that the SQL Server service must be started as a user who has privileges to the network share. Even a locally mapped drive will not work. By default, SQL Server 2000 starts as local system and can't access network shares. |
|
|
|
|
Networked backup