February 14, 2007 at 1:16 am
Hope there is anyone that can help me, I am backing up to a tape drive via SQL, now the first few times it was running fine and did backup, we had power problems in the buiding and ever since I keep on getting the error SQLmaint.exe (SQL STATE 42000) (Error 22029) errors, is there anyone that can help, please do, I have no idea what to do anymore. Please help....
February 14, 2007 at 4:26 am
your best bet is to recreate the job. I never use sysmaint.exe as it's not reliable to my mind - I always write my code in T SQL within job steps or use procs etc. If you had logging set then you should be able to see more of the error, but probably not. Check the event and error logs for more info
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
February 15, 2007 at 6:57 am
A couple of things:
#1 - Don't backup to tape, backup to disc, zip, then backup zipped file to tape after you have copied to another machine
#2 - Don't backup to tape - backing up to disc is faster
#3 - if you copy the zipped backup to tape, you will be able to fit more backups on a single tape
#4 - Use WinZip, not PkZip. PkZip doesn't handle files above a certain file size, I don't remember what the limit is, but it's lower than you would think.
February 15, 2007 at 7:52 am
It's not true that PKZip will not handle files above a ceratin size.
This restriction went away with version 5.0 that was released in 2002.
February 15, 2007 at 8:38 am
I was referring to the standard version of PkZip command line.
This is From an email from PkZip support on 1/20/06:
The DOS version of PKZIP has a 2GB file size limit. The current Command Line version 9.0 has no file size limit, so I would suggest upgrading your older DOS program to the current Windows Command Line program.
The command line version that he is speaking of that works in Win2000 Server cost $600 extra. In my opinion it's not worth it to spend $600 on a product when the $50 version of WinZip will do the same thing for my needs.
February 15, 2007 at 9:20 am
The 2gb file size limit is a limit on the size of a zip file that can be created, not the size of the file to be compressed.
February 15, 2007 at 9:23 am
We have had good luck with WinAce if you want to spend a little bit of money. It seems to compress much better than WinZip.
Otherwise PowerArchiver command line is not bad for a quick, free solution.
February 15, 2007 at 10:26 am
I use WinAce at home. I like the fact that it opens a wider variety of files. We got WinZip at work before I heard about WinAce. We zip up some pretty big backup files (80gb+) and have not had any problems with WinZip, so I am hesitant to switch. I also have not tried WinAce with large files, so I can't comment on how it handles them.
February 15, 2007 at 3:25 pm
you're really wasting time putting zip files to tape as any reasonable tape will compress anyway - been there, done it. If you want compression use Lite Speed, ( and as redgate have a product too I should mention that < grin > )
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
February 15, 2007 at 8:40 pm
Thanks, but the databases is over 120 GIG each and there is 3 of them, needs to be done on a daily basis as the db get updated daily with new information. Why do I get the error though? It did run last week Friday for the last time, and I never changed the job in any way.
February 16, 2007 at 5:49 am
Colin - good point about the compression on tape, forgot about that. I still wouldn't backup directly to tape, way too slow. We don't backup to tape, we zip, then copy to another machine and have 3 days worth of backups there. We then burn to DVD off that machine weekly, so that we will create a history. The most current backup is kept on the machine on another drive in zip and unzipped format.
This sounds like this backup job was created through Database Maintance in Enterprise Manager and is not a script. I would script the backup and see if that fails. The SQLmaint.exe errors don't give a lot of info to help you. There are multiple posts I have seen on this forum talking about sqlmaint.exe errors. If you get an error from the script it should tell you a little more. Have you tried to drop and recreate the backup job in Enterprise Manager?
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply