Re: Dayly backup fails to run after first day

There is a need to distinguish clearly if the scheduled job
fails to launch, or if it launches but failes to complete as
it should. I urge you to embed it in a batch file like so:

@echo off
echo %date% %time% Start of task > c:\test.log
echo User=%UserName%, Path=%path% >> c:\test.log
nbackup.exe /.. /.. /.. 1>>c:\test.log 2>c:\test.err
echo ErrorLevel of NTBackup.exe=%ErrorLevel% >> c:\test.log
echo %date% %time% End of task >> c:\test.log

Copy the "ntbackup.exe" command line from the scheduled
task into your batch file.

Invoke this batch file repeatedly from a Command Prompt and
examine the two log files each time.
- Does the job start every time?
- Does ntbackup complete every time?
- Are there any issues with incremental backup etc?

Now invoke the batch file several times with the Task Scheduler,
and examine the log files again. Any difference?

You must also examine the following log files:
- Event logs
- Task Scheduler logs
- NTBackup logs

After examining these four log files you will have a pretty good
picture about what is really happening!


"Sergey Usov" <sergeyusov@xxxxxxxxx> wrote in message
news:uZgKL6PtFHA.1440@xxxxxxxxxxxxxxxxxxxxxxx
> The account is authorized, because the scheduled job runs once but fails
the
> second time.
> The job runs if it is issued through command prompt, it even runs through
> Backup/restore wizard if one chooses parameter "NOW".
> I repeat again. The scheduled backup job runs the first time, for example,
I
> schedule it for tomorrow September 10 at 2:00 AM and then every day. It
will
> run tomorrow OK but fails on September 11 and later.
> I have a deep suspicion that parameter "INCREMENTAL" somehow influences
it.
> I don't know NTBACKUP very well (never worked on NT). By the way, what's
the
> difference between "INCREMENTAL" and "DAYLY". The HELP about NTBACKUP
gives
> vague explanation, besides it is in Russian. Unfortunately we bought it
> legally and it's too late to switch to English version.
> "Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
> news:%23PytBfOtFHA.1252@xxxxxxxxxxxxxxxxxxxxxxx
> > You must ensure through System Policy that the account you use
> > for the scheduled task is authorised to log in as a batch job.
> >
> > I note that you never responded to my initial suggestion of
> > running the job manually in order to see what's going on.
> >
> >
> >
> > "Sergey Usov" <sergeyusov@xxxxxxxxx> wrote in message
> > news:u8mYWAJtFHA.3188@xxxxxxxxxxxxxxxxxxxxxxx
> >> I'll try to rephrase.
> >> "0x80070569 The system is not logged in. The chosen mode of logging
into
> >> system
> >> for this user at this computer is not valid. Check username and
password"
> >> The idea is: the backup job was created. The first time it starts and
> > works
> >> even when nobody is logged into server, for example, at 2:00 AM. The
next
> >> time, when Task Scheduler wakes it up, it issues this error message.
The
> >> server is working, nobody's logged in, it's night time again. Why it
> >> needs
> >> "logging into system"?
> >> "Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
> >> news:eiKrbzHtFHA.2756@xxxxxxxxxxxxxxxxxxxxxxx
> >> > I'm afraid your translated error messages don't mean much to me -
> >> > they are too far from the English equivalent. I recommend that you
> >> > repost your query in a Russian newsgroup.
> >> >
> >> >
> >> > "Sergey Usov" <sergeyusov@xxxxxxxxx> wrote in message
> >> > news:uikZ1lHtFHA.3236@xxxxxxxxxxxxxxxxxxxxxxx
> >> >> Unfortunately it's Russian version. I'll translate.
> >> >> The code is:
> >> >> 0x80070569 The system is not entered. The chosen mode of entering
> > system
> >> > for
> >> >> this user at this computer is not envisioned. Check validity of user
> > and
> >> >> password and repeat.
> >> >> ====
> >> >> The user is "Administrator" (in Russian letters, since it is a
default
> >> >> Administrator), the password is correct, it was checked by the
system
> >> >> when
> >> > I
> >> >> used wizard.
> >> >> The server is on domain. The "Adminstrator" is logged in locally on
> >> >> computer, not on domain. I have a "user name" in domain with limited
> >> >> administrator rights, for example, I can't add new computer to
> >> >> domain..
> >> > This
> >> >> server belongs to our department, the domain is quite big and
> >> >> complicated.
> >> >> Right now I'll create another job with domain user name and schedule
> >> >> it
> >> > for
> >> >> tonight and next days. frankly speaking I tried it several times
> >> >> before
> >> > with
> >> >> the same error.
> >> >> Thank you for prompt reply, I really didn't expect it.
> >> >> Sergey
> >> >> "Pegasus (MVP)" <I.can@xxxxxxx> wrote in message
> >> >> news:uvBpxpEtFHA.1472@xxxxxxxxxxxxxxxxxxxxxxx
> >> >> >
> >> >> > "Sergey Usov" <sergeyusov@xxxxxxxxx> wrote in message
> >> >> > news:OK%23wqSEtFHA.2948@xxxxxxxxxxxxxxxxxxxxxxx
> >> >> >> On Windows Server 2003 I create a job by Backup/restore wizard to
> > make
> >> >> >> incremental backups of a directory every day. The first day
Backup
> >> >> >> runs
> >> >> > OK.
> >> >> >> The next and subsiquent days it fails. No logs. In scheduler it
> >> > reports -
> >> >> >> run fails.
> >> >> >>
> >> >> >
> >> >> > - Please post the exact error message you see in
> >> >> > Task Scheduler log file, word for word.
> >> >> >
> >> >> > - What happens when you copy the backup command line from
> >> >> > the scheduled task into a batch file, then run the batch
> >> >> > file from the Command Prompt?
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>


.