Exchange NTBackup jobs fail from Task Scheduler (0x1f); OK when done manually
I have 3 jobs scheduled in the Task Scheduler on a Server 2003 Enterprise server. All 3 are set to do full backups of Exchange Info Store using Backup Utility for Windows (NTBackup). They are set to backup to a network drive (not tape).
If I run the job directly from NTBackup, it runs and succeeds, but the job in Task Scheduler fails with an exit code of 0x1f, both using the same login ID. I've placed the task that was created using NTBackup in the code section here.
This problem has been posted several times in several places including once that I found on EE, but I have found no solutions. Any help with this would be greatly appreciated.
If I run the job directly from NTBackup, it runs and succeeds, but the job in Task Scheduler fails with an exit code of 0x1f, both using the same login ID. I've placed the task that was created using NTBackup in the code section here.
This problem has been posted several times in several places including once that I found on EE, but I have found no solutions. Any help with this would be greatly appreciated.
C:\WINDOWS\system32\ntbackup.exe backup "@C:\Documents and Settings\Administrator.SEND\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data\ExBackup-Mon.bks" /n "ExBackup-Mon.bkf created 4/20/2009 at 9:32 AM" /d "Set created 4/20/2009 at 9:32 AM" /v:yes /r:no /rs:no /hc:off /m normal /j "ExBackup-Mon" /l:s /f "X:\ExBackup-Mon.bkf"
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes! It works now. I placed the command in a bach file and called that with the scheduler. I also created a shared folder on the destination server and changed the command to write to the UNC path of the shared folder.
Thanks to the both of you!
Jono
Thanks to the both of you!
Jono
This used to work for me but I stored the bks file somewhere outside the profile folder (C:\Backup in my case). I also did the above - create a batch file for it.