Re: Back-Up
- From: "Lanwench [MVP - Exchange]" <lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 30 May 2009 09:13:16 -0400
DaveMills <DaveMills@xxxxxxxxxxxxxxxx> wrote:
I agree with Lanwench but one possible cause of this sort of problem
is that the mapped drive does not exist. When you login your profile
includes setting up the mapped drive. This does not happen for a
scheduled job unless you have the NET USE X: \\Server\Share command
as part of the job.
Ah, yes, of course - it would really need to be a UNC path.
On Fri, 29 May 2009 08:15:01 -0700, Generis
<Generis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi, everyone,
I am trying to run a back-up job, backing up data from one server,
running on Windows 2003 Standard Edition SP2, to a mapped network
drive (a computer running Win XP). If I do a "back-up now", it
works. But if I schedule the task to run daily at a specific time,
then the application starts but stops after a minute or two... The
back-up's view log says: "Result: The task completed with an exit
code of (1f)." but the server's Event Viewer shows an error with
ntbackup as source, event:8017, user: N/A.
Please note that:
1. The job is ran as administrator and the security tab shows (2)
groups with full rights: Administrators and SYSTEM.
2. I am able to access the mapped network drive, create, rename and
save files in it.
3. The server is up-to-date in terms of updates.
Thank you for looking. Your help is greatly appreciated.
.
- Follow-Ups:
- Back-Up
- From: Generis
- Back-Up
- References:
- Back-Up
- From: Generis
- Re: Back-Up
- From: DaveMills
- Back-Up
- Prev by Date: Re: File Server Resource Manager Quota Migration
- Next by Date: Re: Clients do not inherit all configured settings on print server
- Previous by thread: Re: Back-Up
- Next by thread: Back-Up
- Index(es):
Relevant Pages
|
