Discussion Locked
0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have: Dell 2300, NT 4.0, SQL 7.0 sp 1, SEAGATE STD224000N(Reported as a Archive Python by NT) drive, SCSI setup all terminated correctly, brand new SONY DAT DDS3 tapes using the SQL Agent Scheduler to Dump as a back up. Backing up over 30 DB job runs for 5 hours. My jobs will intermintly succeed but moslty fail, like 4 nights in a row, then a good one, then a string of bad ones. Any ideas? Thanks
5 replies
by andy_p
Have a look here
http://www.swynk.com/faq/sql/sqlfaq_backup.asp#Backup
by kahlich
Poster rated this answer
by tony hogan
Short term solution: To work around this problem, dump databases, transaction logs and tables to disk devices, and then use the Windows NT Server Backup utility (located in Administrative Tools group) to back up the disk devices to tape [you can also schedule this backup]. Doesn't resolve the actual SQL issue but it at least gets the data backed up.
What type of error are you getting in the error log re: the failed backup?
-tony
by kahlich
Poster rated this answer
by kahlich
This question was closed by the author
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending
0 helpful
11 replies
0 helpful
10 replies
Question Locked
Do You Save Useful Windows Tutorial Videos for Later
0 helpful
7 replies
0 helpful
1 reply
Question Unanswered
Is WSL still relevant in 2026?
0 helpful
0 replies