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.
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.