Hi
We have a scheduled task which runs a script which runs ntbackup every night.
Why a script? It stops some Enterprise Vault services, sets part of the registry to read only (or from read only), restarts the services, runs ntbackup, once the job has finished, the services stop again to reverse the registry change then restarts the services. It's a script provided by the vendor.
But ntbackup fails almost as quickly as it begins. It used to work, but its reliability became worse and worse. For a while the scripted firing up of ntbackup would work if we ran the script manually, but now even that's failing.
The application and system event logs show nothing aside from the notifications about service stop and starts.
The command line for ntbackup is
The I: drive is mapped and the account running the command does have rights to write it.
How do I know the ntbackup command quits with error 0? I added a line to the script to echo the errorlevel to a log file.
Also, the ntbackup log file when the backup fails is 1Kb and is blank (compared to 4Kb when it completes).
The server is rebooting as I type, let's see how it behaves when it comes back online...and now it's working. Don't really want to reboot the darn box all the time though!
I have come across a Microsoft KB article which discusses this very issue but doesn't offer a solution ( Argh!
JJ
[small][purple]Variables won't. Constants aren't[/purple]
There is no apostrophe in the plural of PC (or PST, or CPU, or HDD, or FDD, or photo, or breakfast...and so on)[/small]
We have a scheduled task which runs a script which runs ntbackup every night.
Why a script? It stops some Enterprise Vault services, sets part of the registry to read only (or from read only), restarts the services, runs ntbackup, once the job has finished, the services stop again to reverse the registry change then restarts the services. It's a script provided by the vendor.
But ntbackup fails almost as quickly as it begins. It used to work, but its reliability became worse and worse. For a while the scripted firing up of ntbackup would work if we ran the script manually, but now even that's failing.
The application and system event logs show nothing aside from the notifications about service stop and starts.
The command line for ntbackup is
Code:
"C:\WINDOWS\system32\ntbackup.exe backup '@C:\Documents and Settings\ev\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data\EnterpriseVaultBackup.bks' /n 'EnterpriseVaultBackup.bkf created 30/10/2008 at 13:12' /d 'Set created 30/10/2008 at 13:12' /v:no /r:no /rs:no /hc:off /m normal /j 'EnterpriseVaultBackup' /l:s /f 'I:\Backups\EnterpriseVaultBackup.bkf'"The I: drive is mapped and the account running the command does have rights to write it.
How do I know the ntbackup command quits with error 0? I added a line to the script to echo the errorlevel to a log file.
Also, the ntbackup log file when the backup fails is 1Kb and is blank (compared to 4Kb when it completes).
The server is rebooting as I type, let's see how it behaves when it comes back online...and now it's working. Don't really want to reboot the darn box all the time though!
I have come across a Microsoft KB article which discusses this very issue but doesn't offer a solution ( Argh!
JJ
[small][purple]Variables won't. Constants aren't[/purple]
There is no apostrophe in the plural of PC (or PST, or CPU, or HDD, or FDD, or photo, or breakfast...and so on)[/small]
