Re: back not backing up
- From: "alex" <alex@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 19 Nov 2005 14:45:03 -0800
here's the batch file
C:\WINDOWS\system32\ntbackup.exe backup "@C:\Documents and
Settings\Administrator\Local Settings\Application Data\Microsoft\Windows
NT\NTBackup\data\backup.bks" /n "Media created 11/18/2005 at 12:05 AM" /d
"Backup" /v:yes /r:no /rs:no /hc:off /m normal /j "backup" /l:f /p "4mm DDS"
here is the line from the task scheduler
C:\WINDOWS\system32\ntbackup.exe backup "@C:\Documents and
Settings\Administrator\Local Settings\Application Data\Microsoft\Windows
NT\NTBackup\data\backup.bks" /n "Media created 11/18/2005 at 12:05 AM" /d
"Backup" /v:yes /r:no /rs:no /hc:off /m normal /j "backup" /l:f /p "4mm DDS"
here's what was in the .log file
Cannot locate the specified media or backup device. This backup operation
will terminate.
and yes the test folder was made.
"Pegasus (MVP)" wrote:
> I see. The purpose of the batch file was to run your backup
> command in a closely controlled environment. It seems you
> did not really do this.
>
> Now open the task in the Task Scheduler that performs the
> backup. In the "Run" box it has a very, very long line. This
> is called the "Command Line": It is what gets executed at the
> scheduled time. Highlight it, press Ctrl+C, then open the
> batch file I suggested, go to the line that starts with "ntbackup",
> create an empty line, then press Ctrl+V. You have now
> pasted the command line into the batch file. Remove my
> own line starting with "ntbackup" - it is a sample only. And
> while you're at it, paste the command line into your reply
> in this thread.
>
> Now use use Task Scheduler to run the batch file, then
> report the things I suggested before:
> - Post the whole ntbackup command line
> - Post c:\test.err
> - Post the backup??.log pertaining to this run.
> - State if the folder ?:\Test was successfully created
>
> Make sure to report on everything, not just a subset of
> the above items. This thread is getting very long, largely
> because of a lack of feedback.
>
>
> "alex" <alex@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:F417BF14-9EEF-44C4-9CBB-AE0F6BB9534B@xxxxxxxxxxxxxxxx
> > ntbackup command line? I am a little confused, i don't have a batch file
> that
> > run's the ntbackup. I use use the Task Scheduler to run to ntbackup which
> was
> > setup from within ntbackup. I ran your batch file and it gave Command Line
> > Problem: A valid backup operation was not specified on the command line.
> So
> > now what?
> >
> > "Pegasus (MVP)" wrote:
> >
> > > This is like pulling a wisdom tooth . . . I wrote in my previous
> > > reply "Post the whole ntbackup command line". You responded
> > > by saying "A valid backup operation was not specified on the
> > > command line.". Very well - but where is this command line?
> > > Your treating it as if it was a dark secret!
> > >
> > >
> > >
> > > "alex" <alex@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > news:B58FF87D-042A-47D7-8FAE-1B9C3F082801@xxxxxxxxxxxxxxxx
> > > > the log had this in it
> > > > Command Line Problem: A valid backup operation was not specified on
> the
> > > > command line.
> > > >
> > > > and the test folder did get created
> > > >
> > > > "Pegasus (MVP)" wrote:
> > > >
> > > > > There is a time lapse of 2 minutes between the start and the end
> > > > > of your batch file. Presumably this is the time it took for ntbackup
> > > > > to figure out that it was unable to complete the task. The next
> > > > > steps are obvious:
> > > > > - Post the whole ntbackup command line
> > > > > - Post c:\test.err
> > > > > - Post the backup??.log pertaining to this run.
> > > > > - State if the folder ?:\Test was successfully created.
> > > > >
> > > > > "alex" <alex@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > > > news:A7D64FA5-52DC-45E6-868F-63B00C957990@xxxxxxxxxxxxxxxx
> > > > > > I just did it and the log put this out
> > > > > >
> > > > > > Fri 11/18/2005 20:32:00.46 Start of task
> > > > > > User=wink, Path=C:\Program Files\Windows Resource
> > > > > Kits\Tools\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem
> > > > > > ErrorLevel of c:\Tools\YourTask.exe=87
> > > > > > Fri 11/18/2005 20:32:02.50 End of task
> > > > > >
> > > > > >
> > > > > > "alex" wrote:
> > > > > >
> > > > > > > I forgot about that i am doing full back-ups of system state and
> all
> > > > > > > information on the server drives which are local not networked
> > > drives. I
> > > > > am
> > > > > > > using the main administrator account which has access to
> everything
> > > so
> > > > > that
> > > > > > > rules out your thinking of networked drives and the account
> without
> > > > > correct
> > > > > > > permissions. I will give your idea a try and report back...
> > > > > > >
> > > > > > > "Pegasus (MVP)" wrote:
> > > > > > >
> > > > > > > > I'm glad to read that the backup log files were there after
> > > > > > > > all. If you're serious about your backup operation then
> > > > > > > > you will have to examine them once a week.
> > > > > > > >
> > > > > > > > You're not telling us what you're backing up to. I suspect
> > > > > > > > it's a networked drive. I also suspect that you're using
> > > > > > > > an account for the scheduled task that has insufficient
> > > > > > > > access rights to that drive. Copy the command line from
> > > > > > > > the scheduled task into the following batch file:
> > > > > > > >
> > > > > > > > @echo off
> > > > > > > > echo %date% %time% Start of task > c:\test.log
> > > > > > > > echo User=%UserName%, Path=%path% >> c:\test.log
> > > > > > > > md x:\Test 1>>c:\test.log 2>c:\test.err
> > > > > > > > ntbackup @... / / / 1>>c:\test.log 2>c:\test.err
> > > > > > > > echo ErrorLevel of c:\Tools\YourTask.exe=%ErrorLevel% >>
> > > c:\test.log
> > > > > > > > echo %date% %time% End of task >> c:\test.log
> > > > > > > >
> > > > > > > > Where it says "md x:\Test", place your actual backup drive
> letter.
> > > > > > > >
> > > > > > > > Now run this batch file under the Task Scheduler, then examine
> > > > > > > > the two log files. I suspect it will make it very clear why
> your
> > > > > > > > jobs fail.
> > > > > > > >
> > > > > > > > "alex" <alex@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > > > > > > news:EC96587E-4A56-4B60-8F89-70F4B9E5F5B9@xxxxxxxxxxxxxxxx
> > > > > > > > > they say Cannot locate the specified media or backup device.
> > > This
> > > > > backup
> > > > > > > > > operation will terminate.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > When i do it myself it works but what can i do to make it
> work
> > > by
> > > > > Task
> > > > > > > > > Scheduler ?
> > > > > > > > >
> > > > > > > > > "Pegasus (MVP)" wrote:
> > > > > > > > >
> > > > > > > > > > Look in "c:\documents and settings" for files called
> > > > > > > > > > "backup*.log". They are located in the profile folder
> > > > > > > > > > of the account under which you ran the backup job.
> > > > > > > > > > The command
> > > > > > > > > > dir /s "%userprofile%\..\backup*.log"
> > > > > > > > > > will find them for you if you still think they are not
> there.
> > > > > > > > > > What do they contain?
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > "alex" <alex@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > > > > > > > > > news:177B17EA-FD7B-4650-B7A9-31CF1AC45447@xxxxxxxxxxxxxxxx
> > > > > > > > > > > I don't have log files and the event log doesn't say
> much
> > > > > besides RSM
> > > > > > > > was
> > > > > > > > > > > started and then the next event says RSM was stopped.
> Like
> > > it
> > > > > tried
> > > > > > > > but
> > > > > > > > > > did
> > > > > > > > > > > go....
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > "Pegasus (MVP)" wrote:
> > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > "alex" <alex@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> message
> > > > > > > > > > > >
> news:4A1A3314-45C4-4F8E-B6D3-38D535A5BA9A@xxxxxxxxxxxxxxxx
> > > > > > > > > > > > > All of our servers are running w2k3 and using the
> > > back-up
> > > > > software
> > > > > > > > > > that
> > > > > > > > > > > > comes
> > > > > > > > > > > > > with it, i have it the servers to be backed up with
> > > > > Scheduled
> > > > > > > > Tasks
> > > > > > > > > > and do
> > > > > > > > > > > > > full back-ups and overwrite whatever is on the tape
> but
> > > it's
> > > > > not
> > > > > > > > > > working.
> > > > > > > > > > > > If
> > > > > > > > > > > > > i do manually it works fine what can i do to make
> this
> > > work?
> > > > > > > > > > > >
> > > > > > > > > > > > There are three types of logs that relate to scheduled
> > > > > > > > > > > > backup jobs that use ntbackup.exe:
> > > > > > > > > > > > - The event logger
> > > > > > > > > > > > - backupxx.log in your profile folder
> > > > > > > > > > > > - The log maintained by the Task Scheduler under
> > > "Advanced".
> > > > > > > > > > > >
> > > > > > > > > > > > What do they report?
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>
>
.
- Follow-Ups:
- Re: back not backing up
- From: Pegasus \(MVP\)
- Re: back not backing up
- References:
- Re: back not backing up
- From: Pegasus \(MVP\)
- Re: back not backing up
- From: Pegasus \(MVP\)
- Re: back not backing up
- From: Pegasus \(MVP\)
- Re: back not backing up
- From: alex
- Re: back not backing up
- From: alex
- Re: back not backing up
- From: Pegasus \(MVP\)
- Re: back not backing up
- From: alex
- Re: back not backing up
- From: Pegasus \(MVP\)
- Re: back not backing up
- From: alex
- Re: back not backing up
- From: Pegasus \(MVP\)
- Re: back not backing up
- Prev by Date: Re: Which Server to pick
- Next by Date: Installing programs
- Previous by thread: Re: back not backing up
- Next by thread: Re: back not backing up
- Index(es):
Relevant Pages
|