W2003 Server and ntbackup

[whocares23]

Having a little problem. When I run my scheduled backup batch file called backup.cmd - ntbackup backup e:\data /p "4mm DDS" /V:yes /D "daily" /hcn /m normal /l:f /um , it generates a dialog stating "place media created "yesterday's date" with 2 options complete or refuse. If I refuse the job stops. I then reschedule for 2 mins later and the job runs as it should.
This script runs fine on Server2000 and NT4 server. Any insight would be much appreciated.

 

[basst]

The ntbackup syntax is:

ntbackup backup [systemstate] "@FileName.bks" /J {"JobName"} [/P {"PoolName"}] [/G {"GUIDName"}] [/T { "TapeName"}] [/N {"MediaName"}] [/F {"FileName"}] [/D {"SetDescription"}] [/DS {"ServerName"}] [/IS {"ServerName"}] [/A] [/V:{yes | no}] [/R:{yes | no}] [/L:{f | s | n}] [/M {BackupType}] [/RS:{yes | no}] [/HC:{on | off}] [/SNAP:{on | off}]

Not sure what your /um switch is doing

 

[whocares23]

The /um switch allows the job to overwrite any tape - unmanaged backups.

 

[whocares23]

Some more info. The first instance that fails creates a log file, but it's empty. Also, no entry in the event logs. The rerun creates a proper log file/event log entry.

 

[crobin1]

NTBackup can be made to work (and I've used it extensively in the past) but it can be fickle. See if thread931-655160 helps any.

 

[whocares23]

The workaround I've been using was to run a two line batch file. The first line constructed to fail without creating a log, while the second line is the "real" backup. The problem seems to be rsm wasn't being refreshed properly. Running the dummy job forces a refresh, so the real job runs without problems. I would guess that adding:
rsm.exe refresh /LF"Backup Tape Device"
would do the same thing. Thanks for the response.