NTBackupScript is a simple batch file that will force the built-in backup program in Windows Server 2003 (NTBACKUP) to create tape backups when scheduled using ANY available tape in the drive, then eject that tape and send an emailed report about the backup.
NTBackupScript can also check to see if there is a tape in the drive sometime during your workday and send a reminder email to change the tapes if no tape is detected.
I've found NTBACKUP to be a little flaky for doing tape backups. It seems that the way it works with the Removable Storage subsystem is quite touchy in Windows Server 2003. NTBackupScript restarts and refreshes the Removable Storage and then renames the tape for every backup and then specifies that new name in each backup. It also uses the /um switch for NTBACKUP to force it to use any available tape in the drive!
NTBackupScript is mostly put together from code snippets from JSI INC. and uses "sleep.exe" from the Win2k3 Resource Kit for pausing the script, and "blat.exe" (lite version) for sending emails.
Why did I put NTBackupScript together and then give it away?
Because I'm a cheapskate! Windows Server 2003 has a free backup program that comes with it that mostly works. I don't want to have to buy another expensive backup program and then have to learn how that works. I want to force the free Windows backup to make backups to tape. I'm giving this away to all the other servers admins out there who just want a tape backup in Windows that works and is free. I don't want everyone else to have to waste their time trying to fight with ntbackup and rsm commands in scripts to get tape backups to work like I did. Hopefully the script just works for you with little effort.
NOTE: In Windows Server 2008 the NTBACKUP program was removed so this script will not allow you to backup to tape.
G'day Trubo, No - there's no easy way that I know of to have NTBackupScript understand every language variant available - I have made some good inroads to
The upgrade to 2.42 with the same settings mapped by hand to the settings file (not copied, in case there were changes in the new version) did fix the problem.
I haven't had a chance to try this until just now. I still get the same error message after making the changes to the ntbackupscript.cmd. I did use the correct