Ntbackup: Another Stupid Microsoft Tweak

  • Thread starter Thread starter Darrell
  • Start date Start date
D

Darrell

Why did M$ take out the ability to specify where the output log for the ntbackup
command goes? This formerly used the /l "X:\Backup.log" command-line switch. Is
there any way to either know which log file the output was dumped to, or specify
my own output log? Thanks for nothing Microsoft.
 
Darrell said:
Why did M$ take out the ability to specify where the output log for the
ntbackup command goes? This formerly used the /l "X:\Backup.log"
command-line switch. Is there any way to either know which log file the
output was dumped to, or specify my own output log? Thanks for nothing
Microsoft.
Click to expand...

My hunch is that it may have been removed for security reasons. The help
file's list of command switches doesn't allow you to specify anything
other than a Job Name for the log.

Using the NTBackup GUI you can trace the logs to C:\Documents and
Settings\<ProfileName>\Local Settings\Application Data\Microsoft\Windows
NT\NTBackup\data
 
Hmm... seems there would be more pressing security issues for them to work on.
But, whatever.

Thanks for the info. My problem is that I have scheduled the backup to run at
night. Then I want to email the log to myself after the backup has completed.
Since ntbackup does its own log file management internally, I can't know exactly
what the name of the file is. Grrr.

Mike Williams said the following on 02/01/2006 9:27 AM:
 
Of course you can know exactly what the file name is: It's the
most recent one! This two-line batch file will copy it to your
preferred location:

@echo off
set Loc=%UserProfile%\Local Settings\Application Data\Microsoft\Windows
NT\NTBackup\data
echo F | xcopy /d /y "%Loc%\*.log" c:\Logs\Backup.log
 
Many thanks. Not sure what the "echo F" does for me though.

Pegasus (MVP) said the following on 02/02/2006 12:21 AM:
 
Darrell said:
Many thanks. Not sure what the "echo F" does for me though.
Click to expand...

"Echo off" is a command that means that the batch file does not show all the
lines as it works......
 
Well, I don't see this documented anywhere. And can't seem to find it thru a web
search. But, whatever. It works.

David Candy said the following on 02/02/2006 8:31 AM:
 
Back
Top