B
Bartosz Wegrzyn
Hi,
I am using ntbackup to backup all data on the C,D drives to mapped
folder.
First, I created the backup job using the backup wizard.
As a backup location I selected mapped "Z" drive on which I backup
data from all servers. Then I copied the command from the run window
of the backup job to a file located on the Z: drive in the scripts
folder.
This is a bat file which contains this:
C:\WINNT\system32\NTBACKUP.EXE backup "@C:\Documents and
Settings\Administrator\Local Settings\Application
Data\Microsoft\Windows NT\NTBackup\data\C_systemstate_data.bks" /n
"C_systemstate_data" /d "C_systemstate_data" /v:yes /r:no /rs:no
/hcff /m normal /j "C_systemstate_data" /l:f /f
"Z:\DNS1\C_systemstate_data.bkf"
Then I created another scheduled job which runs the bat file.
Unfortunately, for some reason it does not work.
The log of the scheduled tasks logs:
4.71.2195.6920"dns1full.job" (Script-dns1full.bat) 11/30/2004 12:46:22
AM ** WARNING **
Invalid working directory..
The specific error is:
0x00000003: The system cannot find the path specified.
Verify that the directory exists and try again.
"dns1full.job" (Script-dns1full.bat)
Started 11/30/2004 12:46:22 AM
"dns1full.job" (Script-dns1full.bat)
Finished 11/30/2004 12:46:22 AM
Result: The task completed with an exit code of (1).
[ ***** Most recent entry is above this line ***** ]
I dont know what the invalid directory is.
Also if I try to run the configured job itself the backup log
logs:Backup Status
The operation was not performed because the specified media cannot
be found.
----------------------
But what is funny is that when I run manually the bat file with this
command:
"
C:\WINNT\system32\NTBACKUP.EXE backup "@C:\Documents and
Settings\Administrator\Local Settings\Application
Data\Microsoft\Windows NT\NTBackup\data\C_systemstate_data.bks" /n
"C_systemstate_data" /d "C_systemstate_data" /v:yes /r:no /rs:no
/hcff /m normal /j "C_systemstate_data" /l:f /f
"Z:\DNS1\C_systemstate_data.bkf"
"
it works without any problems.
Looks like thereis something that backup does not like, but what is
it?
Any ideas?
Bartosz Wegrzyn
I am using ntbackup to backup all data on the C,D drives to mapped
folder.
First, I created the backup job using the backup wizard.
As a backup location I selected mapped "Z" drive on which I backup
data from all servers. Then I copied the command from the run window
of the backup job to a file located on the Z: drive in the scripts
folder.
This is a bat file which contains this:
C:\WINNT\system32\NTBACKUP.EXE backup "@C:\Documents and
Settings\Administrator\Local Settings\Application
Data\Microsoft\Windows NT\NTBackup\data\C_systemstate_data.bks" /n
"C_systemstate_data" /d "C_systemstate_data" /v:yes /r:no /rs:no
/hcff /m normal /j "C_systemstate_data" /l:f /f
"Z:\DNS1\C_systemstate_data.bkf"
Then I created another scheduled job which runs the bat file.
Unfortunately, for some reason it does not work.
The log of the scheduled tasks logs:
4.71.2195.6920"dns1full.job" (Script-dns1full.bat) 11/30/2004 12:46:22
AM ** WARNING **
Invalid working directory..
The specific error is:
0x00000003: The system cannot find the path specified.
Verify that the directory exists and try again.
"dns1full.job" (Script-dns1full.bat)
Started 11/30/2004 12:46:22 AM
"dns1full.job" (Script-dns1full.bat)
Finished 11/30/2004 12:46:22 AM
Result: The task completed with an exit code of (1).
[ ***** Most recent entry is above this line ***** ]
I dont know what the invalid directory is.
Also if I try to run the configured job itself the backup log
logs:Backup Status
The operation was not performed because the specified media cannot
be found.
----------------------
But what is funny is that when I run manually the bat file with this
command:
"
C:\WINNT\system32\NTBACKUP.EXE backup "@C:\Documents and
Settings\Administrator\Local Settings\Application
Data\Microsoft\Windows NT\NTBackup\data\C_systemstate_data.bks" /n
"C_systemstate_data" /d "C_systemstate_data" /v:yes /r:no /rs:no
/hcff /m normal /j "C_systemstate_data" /l:f /f
"Z:\DNS1\C_systemstate_data.bkf"
"
it works without any problems.
Looks like thereis something that backup does not like, but what is
it?
Any ideas?
Bartosz Wegrzyn