Link to home
Start Free TrialLog in
Avatar of mthomas4
mthomas4

asked on

NTBackUp Scheduled Task

Hi Experts,

As part of the backup plan, there is a scheduled task to run NTBackUp on our Exchange Server.  It runs fine if started manually from the scheduled tasks interface and returns a nice 0x0 result.

However, every time the scheduler tries to run the job, it fails and returns a 0x1f.  This was configured before my time, and I don't want to go poking around blindly.  The command line that runs is included below (seems awfully big to me).

Do you see any reason why this would fail on the scheduler but work manually?

Thanks.
C:\WINNT\system32\ntbackup.exe backup "@C:\Documents and Settings\eei_admin_user.EEI\Local Settings\Application Data\Microsoft\Windows NT\NTBackup\data\Dail Exchange Backup.bks" /n "ExchangeDaily.bkf created 3/31/2008 at 3:37 PM" /d "Set created 3/31/2008 at 3:37 PM" /v:no /r:no /rs:no /hc:off /m normal /j "Dail Exchange Backup" /l:s /f "B:\Server Backups\Exchserver\ExchangeDaily.bkf"

Open in new window

Avatar of mthomas4
mthomas4

ASKER

The error reported in the event log is:

Event Type:      Error
Event Source:      NTBackup
Event Category:      None
Event ID:      8017
Date:            11/13/2008
Time:            12:01:43 AM
User:            N/A
Computer:      EXCHSERVER
Description:
NTBackup error: 'The operation failed. Consult the Backup Report for more details.'

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Where is this mysterious "Backup Report" and would it be of help?
ASKER CERTIFIED SOLUTION
Avatar of MightySW
MightySW
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I found the logs, but they're all from Feb 2007.  They're all "successful" logs as this problem seems fairly recent.  I changed the registry key to keep 20 logs, but as of right now I don't seem to have a recent one.

I guess in the meantime all I can do is try to parse the command line and try to figure out what it's doing.
I have a good log file now.  The following is the log file from ntbackup when I run the command line while logged in as the system administrator:

Backup Status
Operation: Backup
Active backup destination: File
Media name: "ExchangeDaily.bkf created 11/28/2008 at 11:19 AM"

Volume shadow copy creation: Attempt 1.
Backup of "EXCHSERVER\Microsoft Information Store\First Storage Group"
Backup set #1 on media #1
Backup description: "Set created 3/31/2008 at 3:37 PM"
Media name: "ExchangeDaily.bkf created 11/28/2008 at 11:19 AM"

Backup Type: Normal

Backup started on 11/28/2008 at 11:19 AM.
Backup completed on 11/28/2008 at 11:44 AM.
Directories: 4
Files: 5
Bytes: 7,534,650,158
Time:  25 minutes and  10 seconds

----------------------

This is what I get on jobs that run at the scheduled time (i.e. when there is no logged on user):

Backup Status
  The operation was not performed because the specified media cannot be found.

----------------------

It would seem that some path is not accessible while not logged in.  I'll keep poking around and see if I can get to the bottom of this.

In the mean time, any suggestions?
I would recreate the backup job using the backup wiz and then do the schedule.  Be sure to save it and during the wizard you will be prompted for a username and pass to run the job.  It will show up under c:\windows\tasks

Seems like the login credentials that were used before are not good anymore to connect to that device (network share I presume).  Be sure to supply some that can access the share during the setup.

HTH
Take a look at the job, where is it backing up to?  

Does that location still exist, is there enought free space on that drive?
I made a change yesterday and it seems to have resolved the problem.  Here's what was going on:

Original resource location:  B:\<path>
Changed resource location: \\<server name>\<share name>\<path>

Now these should be the exact same thing.  However it seems that mapped drives don't apply when logged out, or are flaky at best.  The UNC path looks like the best way to specify resources.  This job works like a charm now.
Getting my hands on some log files clued me into the resource availability problem.

Cheers!