Weird problem with ntbackup

[jfunk]

I have a NAS running Windows Storage Server. It has mapped drives to several old Netware servers that it backs up using ntbackup every night.

For some reason, I can't get scheduled backups to work against one particular server. The backup starts and exits with no error after about .03 seconds, no files are backed up...the log is just empty and the backup file is not created.

If I just manually run a backup, it works perfectly fine. Select the exact same options, but set it to be scheduled (even for 5 seconds in the future), and it does this. Same thing if I manually start it from the scheduled tasks list.

All the other scheduled backups work fine with the exact same command line (with the exception of file name and path obviously).

All backups are have been created with the same userid (the only one) and the user is always logged in.


Any ideas?


TIA,

jfunk

 

[Smilin]

Check system and app logs. Obviously for ntbackup events but also see if there are any VSS, RSM or scheduler errors.

Be sure removable storage services are running.

If none of the above, stop the RSM service and rename any files in this folder:
%SystemRoot%\System32\NtmsData

Then restart the services.

(per: http://support.microsoft.com/kb/235032)

 

[jfunk]

Forgot to mention, I'm backing up to files on the local drive, not to tape or elsewhere.

Still tried your suggestion, but no change.

There are no ntbackup entries in the application log for the jobs that don't work properly. (nor any entries of any kind in either the application or system logs)

All the other jobs show an entry at the beginning and end of the job.

These jobs that don't work have no entries though. The Scheduled Tasks log shows it starting and stopping 1 second later, and the ntbackup report for the job gets created (but it is blank).

Thanks for the help.

j

 

[Smilin]

any event id 26s anywhere? If you are hitting the server via terminal services any popups like "out of space" won't make it to your screen. 26s would indicate what these were. Also make sure you don't have an ntbackup process already sitting in there somewhere. A hung backup job from long ago can cause new backup jobs to fail.

I wish I could help more, it's been a couple years now since I supported that app.