Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-02-14 : 08:24:29
|
| Jason writes "We recently installed SP4 on SQL Server 2000 and now our transaction log backup jobs fail. We are backing up to a mapped network drive and have been successful prior to our latest install. I have tried an xp_cmdshell command from Query Analyzer and am able to do a directory listing and copy command to the mapped drive just fine. xcopy on the other hand does not work.When I try to preform any backup to the network drive:Backup Database master to Disk='t:\Backup\MasterDB.BAK' WITH INITNote: I have also tried using the UNC path as well with the same results:Cannot open backup device 't:\Backup\MasterDB.BAK'. Device error or device off-line. See SQL Server error log for more details.I look in the error log and see the following:Operating System error = 5 (Access Denied)Do you have any suggestion on how I can get my backups working again??? Please keep in mind I am able to copy/create files fine through Query Analyzer and I am using a domain account not the local account.Thanks in advance." |
|
|
mallier
Starting Member
24 Posts |
Posted - 2006-02-14 : 11:07:36
|
| check this link,http://groups.google.com.au/group/microsoft.public.sqlserver.tools/browse_thread/thread/ba5b7b0d5d9189f4/f892bbcf7866ad92%23f892bbcf7866ad92?sa=X&oi=groupsr&start=1&num=3cheers,http://mallier.blogspot.com |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2006-02-14 : 11:20:34
|
| Hi Jason, Welcome to SQL Team!"We are backing up to a mapped network drive"Do you REALLY need to do this? It adds heaps of fragility to the process, and you may not get notification if it starts to fail.Much better to backup to a local drive and then trigger a BATCH file, or some such, that copies the backup file to the network share (and then deletes it if successful if desired). This process can tolerate network outage (e.g. by making the Batch file transfer whatever files it finds locally that do not exist on the remote).Kristen |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2006-02-14 : 14:18:05
|
quote:
Originally posted by Kristen
Hi Jason, Welcome to SQL Team!"We are backing up to a mapped network drive"Do you REALLY need to do this? It adds heaps of fragility to the process, and you may not get notification if it starts to fail.Much better to backup to a local drive and then trigger a BATCH file, or some such, that copies the backup file to the network share (and then deletes it if successful if desired). This process can tolerate network outage (e.g. by making the Batch file transfer whatever files it finds locally that do not exist on the remote).Kristen
I disagree that backing up to a network drive is a problem. The only problem I have encountered with the network backups is the speed. My experience has been that the backups take about 25% more time to run across the LAN. Keep in mind that we run clustered Netapps and all servers are gigabit connected.I do not buy the argument that backing up across the LAN increases the possibility of problems. If that were the case, we would be seeing problems with standard data transfers from our DB servers to our Web and App servers. The only problem, IMHO, is the speed - and if you can live with the slight slowdown then do it.-ec |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2006-02-15 : 02:20:28
|
| I agree the network should be close to 100% reliable. But even though the LAN may not fail I would still be concerned about other factors: the permissions might get mucked up such that the share becomes not available, or the hardware rearranged and no one remember that SQL needs reconfig etc., plus the slower backup speed may contribute to stress on other queries running on the SQL box.An approach of "backup local and copy/move to LAN share" avoids all those issues and if cfor any reason the LAN is not reachable at least you still have local backups.Kristen |
|
|
|
|
|
|
|
|
Transaction Log Backup to Network Drive