ntbackup problem, exit code 0x1f

L

Lisij

Good day eveyone.
Here is the situation. I will try to explain it as detailed as i can,
to cover most of the questions that i saw people asked in similar
situations...

Have AD with all clients WinXP Pro SP2.

i have configured 14 backups to run at 9-00 am in one of the
departmens i am responsible for.

Users dont have local admin rights on their machines.
I configured ntbackup task as follows:
Created separate account in AD, added it to the Domain Admin group.
On user's machines i initiate ntbackup with "Run as..." command, using
that AD account with admin rights.
Configure files to backup.
Backup info: Normal, no verification, overwrite files, destination -
share on the server, configured as an UNC name, not the mapped
drive...
Backup when: Later.
Scheduler - daily backup at 9-00am. Scheduled task runs from under AD
account with domain admin rights.
Option "Run only when logged in" is not selected.
Option "Wake computer to run the task" is selected.
All computers are on at the time the task runs.

PROBLEM:
randomly (means user A today, user B tomorrow, user C day after
tomorrow) backups fail with exit code 0x1F.
For example, today, 7 out of 14 failed.
Yestarday 6 out of 14 failes, few people are different then today.
When i run the task manually out of the scheduler (right click - Run)
it works OK.

Account that's used to run the tasks has full access to the share on
the server, just as NTFS permissions.
Antivirus isnt an issue (dont have it on the server atm)
(before any bashing begins about not having AV on the server, want to
say that the "Server" is just a workstation with lots of disk space,
XP Pro SP2 based as well, fresh build, and that department is just
testing the possibility of the backup onto it)

I saw a couple of times that 0x1F means that destination isnt
accessible (either rights or simply unavailible).
BUT! Randomness and the fact the one office failed today, but the
neighbour next door ran fine - all that kind of show that there are no
problems with access or permissions.
Tried deleting task, and re-creating it - no luck.

I searched groups here - only 3 threads so far, none followed up to
the resolution. And it seems to be more or less common problem.
 
P

Pegasus \(MVP\)

Lisij said:
Good day eveyone.
Here is the situation. I will try to explain it as detailed as i can,
to cover most of the questions that i saw people asked in similar
situations...

Have AD with all clients WinXP Pro SP2.

i have configured 14 backups to run at 9-00 am in one of the
departmens i am responsible for.

Users dont have local admin rights on their machines.
I configured ntbackup task as follows:
Created separate account in AD, added it to the Domain Admin group.
On user's machines i initiate ntbackup with "Run as..." command, using
that AD account with admin rights.
Configure files to backup.
Backup info: Normal, no verification, overwrite files, destination -
share on the server, configured as an UNC name, not the mapped
drive...
Backup when: Later.
Scheduler - daily backup at 9-00am. Scheduled task runs from under AD
account with domain admin rights.
Option "Run only when logged in" is not selected.
Option "Wake computer to run the task" is selected.
All computers are on at the time the task runs.

PROBLEM:
randomly (means user A today, user B tomorrow, user C day after
tomorrow) backups fail with exit code 0x1F.
For example, today, 7 out of 14 failed.
Yestarday 6 out of 14 failes, few people are different then today.
When i run the task manually out of the scheduler (right click - Run)
it works OK.

Account that's used to run the tasks has full access to the share on
the server, just as NTFS permissions.
Antivirus isnt an issue (dont have it on the server atm)
(before any bashing begins about not having AV on the server, want to
say that the "Server" is just a workstation with lots of disk space,
XP Pro SP2 based as well, fresh build, and that department is just
testing the possibility of the backup onto it)

I saw a couple of times that 0x1F means that destination isnt
accessible (either rights or simply unavailible).
BUT! Randomness and the fact the one office failed today, but the
neighbour next door ran fine - all that kind of show that there are no
problems with access or permissions.
Tried deleting task, and re-creating it - no luck.

I searched groups here - only 3 threads so far, none followed up to
the resolution. And it seems to be more or less common problem.

Your first job should be to examine the backup logs on
the days in question.
 
L

Lisij

Your first job should be to examine the backup logs on
the days in question.- Hide quoted text -

- Show quoted text -

are we talking about SchedLgU.Txt or are there other files?
 
P

Pegasus \(MVP\)

Lisij said:
are we talking about SchedLgU.Txt or are there other files?

We are taking about backup*.log, buried deep inside the
profile folder of the account used when running the backup.
You can access them from the Tools menu within ntbackup.exe
but only if you're logged on as that same user. Otherwise you
need to use Explorer to open them.
 
L

Lisij

We are taking about backup*.log, buried deep inside the
profile folder of the account used when running the backup.
You can access them from the Tools menu within ntbackup.exe
but only if you're logged on as that same user. Otherwise you
need to use Explorer to open them.- Hide quoted text -

- Show quoted text -
============================================================
Here is the log from the failed scheduled backup:
------------
Backup Status
The operation was not performed because the specified media cannot
be found.

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

============================================================
Here is the log of the task i initiated manually, without changing a
single thing:
------------
Backup Status
Operation: Backup
Active backup destination: File
Media name: "jblow.bkf created 11/29/2007 at 11:05 AM"

Backup (via shadow copy) of "C: "
Backup set #1 on media #1
Backup description: "Set created 11/27/2007 at 7:51 AM"
Media name: "jblow.bkf created 11/29/2007 at 11:05 AM"

Backup Type: Normal

Backup started on 11/29/2007 at 11:05 AM.
Backup completed on 11/29/2007 at 11:09 AM.
Directories: 7
Files: 1
Bytes: 1,661,879,704
Time: 4 minutes and 8 seconds
 
P

Pegasus \(MVP\)

Lisij said:
============================================================
Here is the log from the failed scheduled backup:
------------
Backup Status
The operation was not performed because the specified media cannot
be found.

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

============================================================
Here is the log of the task i initiated manually, without changing a
single thing:
------------
Backup Status
Operation: Backup
Active backup destination: File
Media name: "jblow.bkf created 11/29/2007 at 11:05 AM"

Backup (via shadow copy) of "C: "
Backup set #1 on media #1
Backup description: "Set created 11/27/2007 at 7:51 AM"
Media name: "jblow.bkf created 11/29/2007 at 11:05 AM"

Backup Type: Normal

Backup started on 11/29/2007 at 11:05 AM.
Backup completed on 11/29/2007 at 11:09 AM.
Directories: 7
Files: 1
Bytes: 1,661,879,704
Time: 4 minutes and 8 seconds

You need to show us the command line you use for backing up your files.
 
L

Lisij

C:\WINDOWS\system32\ntbackup.exe backup "@C:\Documents and Settings
\miniadmin\Local Settings\Application Data\Microsoft\Windows NT
\NTBackup\data\PST Backup.bks" /n "fschaber.bkf created 11/27/2007 at
7:51 AM" /d "Set created 11/27/2007 at 7:51 AM" /v:no /r:no /rs:no /
hc:blush:ff /m normal /j "PST Backup" /l:s /f "\\cad-backup\email$\BroadView
\fschaber.bkf"


Repeating again, backup works fine when started manually.
To make it even more confusing, in last 4 days, backup for that user
ran ok twice, failed twice too.
 
P

Pegasus \(MVP\)

Lisij said:
C:\WINDOWS\system32\ntbackup.exe backup "@C:\Documents and Settings
\miniadmin\Local Settings\Application Data\Microsoft\Windows NT
\NTBackup\data\PST Backup.bks" /n "fschaber.bkf created 11/27/2007 at
7:51 AM" /d "Set created 11/27/2007 at 7:51 AM" /v:no /r:no /rs:no /
hc:blush:ff /m normal /j "PST Backup" /l:s /f "\\cad-backup\email$\BroadView
\fschaber.bkf"


Repeating again, backup works fine when started manually.
To make it even more confusing, in last 4 days, backup for that user
ran ok twice, failed twice too.

Here is the cause of your problem: You store the .bkf backup file on
a server share to which the account used by the Task Scheduler has
no access.
 
L

Lisij

Here is the cause of your problem: You store the .bkf backup file on
a server share to which the account used by the Task Scheduler has
no access.

Huh?
Which account is that?

Just checked permissions on the share:
Share permissions - full access to "Everyone"
NTFS permissions - "Domain admins" - full access; "System" - full
access...

"Domain admins" are members of the "Local Admins" on the workstation...
 
P

Pegasus \(MVP\)

Lisij said:
Huh?
Which account is that?

Just checked permissions on the share:
Share permissions - full access to "Everyone"
NTFS permissions - "Domain admins" - full access; "System" - full
access...

"Domain admins" are members of the "Local Admins" on the workstation...

When you created your scheduled task in the Task Scheduler,
you used a certain account. This account appears to have no
access to the server share.

If you used at.exe to schedule your task then it runs under
the System account. This account has no access at all to any
network resources.
 
L

Lisij

When you created your scheduled task in the Task Scheduler,
you used a certain account. This account appears to have no
access to the server share.

If you used at.exe to schedule your task then it runs under
the System account. This account has no access at all to any
network resources.- Hide quoted text -

- Show quoted text -

Steps of creating backup:
1. start-programs-accessories-system tools - right click on Backup -
Run as... - "Domain\miniadmin" (miniadmin is a member of domain admin
group), password
1.5. if it's the first time i run Backup, uncheck "always run in
wizard mode", and go directly to "Advanced"
2. Backup wizard (advanced) - Next - Selected Files, drives, or
network data - $navigate to a file to be backed up$ - Next - Place to
save a backup: \\server\share\backup.bkf - Next - Advanced
3. Select Type: "normal" - Next - Verify (not checked)/Disable shadow
copy (not checked) - Next - Replace existing backup - Next - When to
backup (NOW/LATER) $here is when scheduled task is created$: LATER
4. Job name: BACKUP - Set schedule
5. Scheduled task: Weekly, Mon to Fri. at 9-00 am; Settings: Wake
computer to run the task - checked
6. When clicked OK, it asks for the username/password: username :
"DOMAIN\miniadmin" (miniadmin is a member of domain admin group),
password - typed in twice
7. Back to backup wizard - Next: Asks for username/password again.
Type in same "domain\miniadmin) (miniadmin is a member of domain admin
group), password - typed in twice
8. Finish

Server:
Share permissions:
Everyone - Full access

NTFS permissions:
domain administrator - FA
Server\administrators - FA
Creator/owner - none, only special permissions are greyed out, but
when go "Advanced", click on CREATOR/OWNER, then EDIT, everything is
allowed
Domain Admin - FA
Domain Users - Read and Execute, Read, Write, List folder content
System - FA
Users (Server\Users) - Read&excute, List folder content, Write

Checked the permission on the backup file:
Same NTFS permissions as for a share, plus account I used to run the
task - FA to the file. Same account is an owner of the file
 
L

Lisij

Steps of creating backup:
1. start-programs-accessories-system tools - right click on Backup -
Run as... - "Domain\miniadmin" (miniadmin is a member of domain admin
group), password
1.5. if it's the first time i run Backup, uncheck "always run in
wizard mode", and go directly to "Advanced"
2. Backup wizard (advanced) - Next - Selected Files, drives, or
network data - $navigate to a file to be backed up$ - Next - Place to
save a backup: \\server\share\backup.bkf - Next - Advanced
3. Select Type: "normal" - Next - Verify (not checked)/Disable shadow
copy (not checked) - Next - Replace existing backup - Next - When to
backup (NOW/LATER) $here is when scheduled task is created$: LATER
4. Job name: BACKUP - Set schedule
5. Scheduled task: Weekly, Mon to Fri. at 9-00 am; Settings: Wake
computer to run the task - checked
6. When clicked OK, it asks for the username/password: username :
"DOMAIN\miniadmin" (miniadmin is a member of domain admin group),
password - typed in twice
7. Back to backup wizard - Next: Asks for username/password again.
Type in same "domain\miniadmin) (miniadmin is a member of domain admin
group), password - typed in twice
8. Finish

Server:
Share permissions:
Everyone - Full access

NTFS permissions:
domain administrator - FA
Server\administrators - FA
Creator/owner - none, only special permissions are greyed out, but
when go "Advanced", click on CREATOR/OWNER, then EDIT, everything is
allowed
Domain Admin - FA
Domain Users - Read and Execute, Read, Write, List folder content
System - FA
Users (Server\Users) - Read&excute, List folder content, Write

Checked the permission on the backup file:
Same NTFS permissions as for a share, plus account I used to run the
task - FA to the file. Same account is an owner of the file

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

I dont know where else to look.
All backups - all 14 of them - are configured same way. Several
complete successfully all the time... others fail...- Hide quoted text -

- Show quoted text -

Just changed the run time in scheduler to run few minutes ago -
completed successfully...
I didnt even start it manually. just changed time from 9-00 am to
10-15, and it ran just fine...

Is it possible that WinXP has some kind of limitation that would
prevent 15 simultanious connections? That's the only thing that i can
think of right now...
 
P

Pegasus \(MVP\)

Lisij said:
Just changed the run time in scheduler to run few minutes ago -
completed successfully...
I didnt even start it manually. just changed time from 9-00 am to
10-15, and it ran just fine...

Is it possible that WinXP has some kind of limitation that would
prevent 15 simultanious connections? That's the only thing that i can
think of right now...

Windows 2000/XP Prof allows up to ten concurrent network
connections. If you need more then you must place your
shares on a Windows Server.
 
L

Lisij

Windows 2000/XP Prof allows up to ten concurrent network
connections. If you need more then you must place your
shares on a Windows Server.- Hide quoted text -

- Show quoted text -

that's exectly what i was suspecting, was i process of looking for the
confirmation on MS web site

Thanks, that explains it
 
L

Lisij

that's exectly what i was suspecting, was i process of looking for the
confirmation on MS web site

Thanks, that explains it- Hide quoted text -

- Show quoted text -

For the last hour was playing with it...
At any given time (run backup for all of them) 8 tasks would complete.
2 fail consistently, seems like misconfiguration, will check. The
remaining 4 people vary.
Looks like going to replace XP with Server

Thanks Pegasus, appreciate the input.
 
P

Pegasus \(MVP\)

For the last hour was playing with it...
At any given time (run backup for all of them) 8 tasks would complete.
2 fail consistently, seems like misconfiguration, will check. The
remaining 4 people vary.
Looks like going to replace XP with Server

Thanks Pegasus, appreciate the input.

I am a little confused. In your very first post you mentioned
"Active Directory", which implies that you run your show in
a server environment. Now you intend to replace some
WinXP machine with a Windows Server. I thought you
already have one! Did you perhaps install too few CALs?
Or are you parking your backup files on a workstation?

There are a couple of other things that don't sound right:
- It's not a good idea to start all backup runs at the same
time. You will saturate your network. You should stagger
them.
- If you have a server then your users should store their
files on it. This would solve lots of problems, e.g. backing
them up, security, sharing. Allowing users to store their
files on their workstations should be strictly verboten!
 
L

Lisij

I am a little confused. In your very first post you mentioned
"Active Directory", which implies that you run your show in
a server environment. Now you intend to replace some
WinXP machine with a Windows Server. I thought you
already have one! Did you perhaps install too few CALs?
Or are you parking your backup files on a workstation?

There are a couple of other things that don't sound right:
- It's not a good idea to start all backup runs at the same
time. You will saturate your network. You should stagger
them.
- If you have a server then your users should store their
files on it. This would solve lots of problems, e.g. backing
them up, security, sharing. Allowing users to store their
files on their workstations should be strictly verboten!

Hey, thanks for the additional input.
I'll clear it now.
Yes, we have normal functional AD, with 2 DC - one 2K, other 2K3; with
XP as clients.
The problem is that we dont have exchange in-house (it is a project in
progress at the moment, still about 6 months away).
The reason i am looking for a backup solution is to temporarely ensure
the backup of PST files. Email provider has a limited storage space
for each mail-box (very limited) and some ppl have years worth of
correspondance that is irreplaceable. There is a utility that we used
that would backup PST to a share on the file server, but it was (is)
user-dependant; user has to click "backup" on Outlook's exit. I was
looking to automate the process. ntbackup seemed to be the least
effort solution. We pulled out one workstation, added 6 e-SATA drives
to it, shared one, then have batch file running on that station that
would copy from "Current" to "Monday"/"Tuesday"/etc drives. That box
has 2 GB NICs teamed in LB.
If you know or can think of easier/better solution to backup PST files
that wouldnt need user's input - i'm all ears. Has to be cheap/free
too, no point to invest serious money into something that will be gone
in 6 months or so...

About saturating the network - not a problem. Network is all gigabit,
the largest PST file is 1.7GB, takes about 4 mins. Others have it
under 500MB, takes up to 1-2 mins. Noone noticed any issues with
network at the time of backups. If it worked out the way i thought it
would, we would scatter different departments in time, not different
users. 10-15 backups arent noticable.

And we have GPO that mapps "My Documents" for each user off the
server, so all files they work with are on the server, and it has tape-
backup solution in place, that totally separate from this one.
Yes, we tried to put those files onto the file server we have, but for
some reason users did notice significant performance issues, to the
point when shares werent availible. Don't know if the hardware on the
server couldnt handle it, or what was the problem. We tried separate
workstation box, run same 10 (or so) backups - not a glitch... Except
for number of simultanious backups, as we see now.

I realize that what i am trying to do may not be MS best practice, but
that isnt my sand box, i cant tear it down, and re-build how it's
suppose to be. Have to deal and work around the setup that is already
here.
 
P

Pegasus \(MVP\)

Hey, thanks for the additional input.
I'll clear it now.
Yes, we have normal functional AD, with 2 DC - one 2K, other 2K3; with
XP as clients.
The problem is that we dont have exchange in-house (it is a project in
progress at the moment, still about 6 months away).
The reason i am looking for a backup solution is to temporarely ensure
the backup of PST files. Email provider has a limited storage space
for each mail-box (very limited) and some ppl have years worth of
correspondance that is irreplaceable. There is a utility that we used
that would backup PST to a share on the file server, but it was (is)
user-dependant; user has to click "backup" on Outlook's exit. I was
looking to automate the process. ntbackup seemed to be the least
effort solution. We pulled out one workstation, added 6 e-SATA drives
to it, shared one, then have batch file running on that station that
would copy from "Current" to "Monday"/"Tuesday"/etc drives. That box
has 2 GB NICs teamed in LB.
If you know or can think of easier/better solution to backup PST files
that wouldnt need user's input - i'm all ears. Has to be cheap/free
too, no point to invest serious money into something that will be gone
in 6 months or so...

About saturating the network - not a problem. Network is all gigabit,
the largest PST file is 1.7GB, takes about 4 mins. Others have it
under 500MB, takes up to 1-2 mins. Noone noticed any issues with
network at the time of backups. If it worked out the way i thought it
would, we would scatter different departments in time, not different
users. 10-15 backups arent noticable.

And we have GPO that mapps "My Documents" for each user off the
server, so all files they work with are on the server, and it has tape-
backup solution in place, that totally separate from this one.
Yes, we tried to put those files onto the file server we have, but for
some reason users did notice significant performance issues, to the
point when shares werent availible. Don't know if the hardware on the
server couldnt handle it, or what was the problem. We tried separate
workstation box, run same 10 (or so) backups - not a glitch... Except
for number of simultanious backups, as we see now.

I realize that what i am trying to do may not be MS best practice, but
that isnt my sand box, i cant tear it down, and re-build how it's
suppose to be. Have to deal and work around the setup that is already
here.

Under the circumstances your temporary solution is probably
the best compromise.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Problem restoring a backup - NTBACKUP 15
XP NTBackup with NT 3.50 5
Using NTbackup with RUNAS 1
NTbackup 2
Question about ntbackup 2
NTBackup Functionality 2
scheduling a backup 7
Network ntbackup 5

Top