ADSM-L

Re: drive not backed up on NT Server with v3.1.0.8

2000-03-10 15:48:50
Subject: Re: drive not backed up on NT Server with v3.1.0.8
From: Gary Ison <Gary.Ison AT MAIL.STATE.KY DOT US>
Date: Fri, 10 Mar 2000 15:48:50 -0500
Zeke,

        Make sure the account running the scheduler (normally "system") has
access to the drive in question.  I had a similar experience with a client
and someone had gone in to the Disk Admin tool and restricted access to the
drive.

I have just taken a call about this from one of my users with the same
problem and I noticed the Domain statement in the options file was the last
entry.  I told the user to move it before the include exclude list and
restart the scheduler.  I won't know if that fixed his problem until Monday.

You might also check the error log for a 933 error.  This terminates the
scheduler backup processing and occurs when a file is unable to back up.
The solution on that is to exclude the file from backup.  Files I found
causing this condition were "ntuser.data.log", "ntuser.log", registry files,
and some other application log files.

        I'm running 3.7.1.0 clients on an OS/390 MVS server at 3.1.2.40.

        Gary L. Ison
        Governor's Office for Technology
        101 Cold Harbor Drive
        Frankfort, Ky.   40601
        Phone:  (502) 564-8724
            Fax:  (502) 564-6856
E-mail: Gary.Ison AT mail.state.ky DOT us <mailto:Gary.Ison AT mail.state.ky 
DOT us>


<Prev in Thread] Current Thread [Next in Thread>