Backup log

  • Thread starter Thread starter Sameer
  • Start date Start date
S

Sameer

Hi,

We have scheduled NT backup with "At" command on windows
2000 server. Backup is working Ok at schedule time. But it
does not generate log file although we have used /L
option. The same batch file when I run instead of through
at command it generates log file under my NT profile
directory. Pl. Help

Thanks,

Mahendra
 
Sameer wrote in
Hi,

We have scheduled NT backup with "At" command on windows
2000 server. Backup is working Ok at schedule time. But it
does not generate log file although we have used /L
option. The same batch file when I run instead of through
at command it generates log file under my NT profile
directory. Pl. Help

"under my NT profile" is your clue. (I think).
What account is actually _running_ the sceduled task and is the log in
_that_ account's profile?
 
Sameer said:
option. The same batch file when I run instead of through
at command it generates log file under my NT profile
directory. Pl. Help

Sounds like a permissions problem. Jobs scheduled using the AT command
run under the "NT AUTHORITY\SYSTEM" account. This account will need
write access to:-

C:\Documents and Settings\Default User\Local Settings\
Application Data\Microsoft\Windows NT\NTBackup\data

To troubleshoot, open a console window and enter:-

at hh:mm /i cmd.exe /k

where hh:mm is about three minutes into the future. Run your script
from the new console window when it starts. Hopefully you'll be able
to see any errors.

You might find it simpler to schedule the job using the GUI scheduler
and specifying a username/password that have appropriate access.
 
Have you found a solution to this? I have been having the same exact
issue. Also, it appears that when I schedule the job through the AT
command, it doesn't register in the restore database. Any ideas?
 
GKurcon said:
Have you found a solution to this? I have been having the same exact
issue. Also, it appears that when I schedule the job through the AT
command, it doesn't register in the restore database. Any ideas?

"Sameer" <[email protected]> wrote in message


The most common problem with using AT is the commands run as the local
System account, meaning it will have different permissions than you. If you
run the same command from your account, does it work? If so, then
permissions are most likely your problem. The System account probably does
not have access to the location that /L specifies. If it's a local folder
then you just need to change the NTFS ACLs. If you are trying to write the
log to a network location then that is a problem. The system account has
local admin rights, but over the network it has anonymous or guest rights.
You would need to open a connection with a different user account, like "net
use \\server\share /u:user password" but then you have a plain text password
inside your batch file or AT command line.

Post more details about your ntbackup command.
 
Back
Top