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 |
|
rkessler
Starting Member
2 Posts |
 Posted - 2004-05-05 : 14:02:35
|
| We have backups on SQL2000 going to a unc on another box. They fail intermittently and drive us nuts with ERROR 3013 and write failures. I have just heard from a SQL Server DBA that the rule with SQL Server is "Don't backup to a remote box!".Can anyone confirm this is true...Thanks in advance...- RichardRichard KesslerThe Mattei CompaniesSeattle, WA 98101 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-05-05 : 14:10:57
|
| Yes that is true. The recommendation is to backup to the local disk then copy the file to the remote server or tape. Backups are very important. You can not afford to have a database/server failure occur and find out that the backup wasn't successful since the network had a hiccup. Backing the database up to disk is less prone to problems. The only problem that you might encounter is lack of free disk space. But that you can certainly plan out.Tara |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-05-05 : 14:13:15
|
| Also, I noticed that in your other thread from last week that you are having problems with deleting of files through a maintenance plan. The recommendation is to not use maintenance plans. You wouldn't use a wizard to create your application, so why use a wizard here. You have much more control when you write your own code to do the maintenance routines.Tara |
|
|
|
|
|
|
Backing up to a remote server...bad idea?