ntbackup log file hangs

[WildDoktor]

I've got a couple of servers still running ntbackup to local 4mm dat drives.

Using AT, I schedule this .cmd file to run each nite:

ntbackup backup c:\ d:\ /d "Full Backup" /v /b /hcn /t normal /l "d:\backups\backup.log"

Every morning I manually rename the log file and move it to a different folder.

Here's the problem:

Every once in a while - at random - I will rename the log file and get a an error that says: "Cannot rename backup: There has been a sharing violation. The source or destination file may be in use." Backups will not run after this; I've left one of the servers in this state for days, swapping the tape and hoping to see that it has run the next morning...in vain.

The only way I have found to fix this is to reboot the server! Not a pretty fix, to say the least. I have used KILL to kill the ntbackup process, but every time I have tried this it has locked up the server and I've had to reboot anyway.

So, any suggestions?

Thanks!
Bill

 

[SteelDragon]

Have you tried using a variable to set a max log file size? If that doesn't work, then try placing the backup log in a different location... Check your free space and make sure there is enough to create the log (obvious, but need to say it anyhow). I would also suggest getting a 3rd part backup software as NT backup DOES NOT backup your complete Win NT installation, there are several things that are left out, and if you need to ever perform a restore, you will lose them, and most of your registry. Just a thought, but there are some really good shareware/freeware utilities out there that do a much better job than NT backup. You might check:

http://www.tucows.com

for a few.

Good Luck,
SteelDragon

 

[WildDoktor]

Thanks for the reply!

Yep; I've got plenty of space (22Gb free).

Yep; I know I need to get some real backup software...it's still going through approval.

Sometimes when the log file is locked, I edit the .cmd file and change the name of the log file to something different. Sometimes this will let backups run the next time; sometimes it won't.

Any other suggestions, anybody?
Thanks!
Bill