On Windows 2003 Server, I am running ntbackup through a script file, scheduled to run each night using the AT command. The backups run fine, but no log file is created. When I run the batch file manually, a backup log is created. When I use the ntbackup wizard to create a backup job and run it from the console, the backup log is created. Has anyone run into this problem? Thank you in advance for your assistance! -Dan

Did you include this or maybe a slight typo? Switch: /L:{f | s | n} Description: Specifies the type of log file: f=full, s=summary, n=none (no log file is created). Scripts can be run with read permission. Guess it could not actually make a new log if it only has read permissions. Might have to include write permissions. Dunno, just ideas/guesses. From here. http://support.microsoft.com/default.aspx?scid=kb;en-us;814583

got the same problem - no .log file created in server 2003 using command line ntbackup.exe! Worked fine in server 2000. Even searched the C:\ drive for any files containing the job name specified with the j/ switch but still nothing .. Any ideas anyone?

Just got it working, not entirely certain how but it does! The logs are stored here: C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data\ For some reason they don't show up in the search results on the C:\ drive for any files containing 'backup' or *.log. Also strange is that in Win2K they're stored in the 'Default User' profile instead. I am using command-line at.exe to schedule the batch script though... If the above directory path doesn't exist you might try creating it manually & seeing if the .log files are created then. There was some non-capitalisation in my command-line. I also see that the /UM switch isn't mentioned in the Win2K3 Help, but without it my tapes don't mount from the command line backup, which now looks like this: NTBACKUP.EXE backup C:\ /V:no /R:no /RS:no /HC:on /M normal /J "Server1" /L:s /P "miniQIC" /UM It may well have been a capitalisation/syntax thing - that's the only change I've made...

Bit more feedback: when running my .bat file manually from the command line as administrator the backup logs are created here: C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data\ If I schedule the batch file to run using command line at.exe NO LOGS ARE GENERATED! Schedule the .bat file to run using 'Scheduled Tasks' in Windows as Administrator the batch file runs & logs are generated in expected location: C:\Documents and Settings\Administrator\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data\ Not sure why at.exe can't create the logs. Looking in 'Scheduled Tasks' in Windows my batch file runs as 'System' user if set using at.exe, and as Administrator if scheduled via Windows. Could well be a permission thing, although both users have full access to the log folder... Annoying when this has been a tried & tested method of backing up our servers over the years, using both NT4 & Win2K. Guess I'll have to stop using at.exe