ADSM-L

WindowsNT V3 Schedules failing on NTUSER.DAT

2015-10-04 18:03:48
Subject: WindowsNT V3 Schedules failing on NTUSER.DAT
From: INTERNET.OWNERAD at SNADGATE
To: Jerry Lawson at ASUPO
Date: 11/6/97 12:56PM
This is what REALLY happened.

The scheduled backup began.  I was too quick, and started to browse the
DSMSCHED.LOG before the backup had completed.  What I saw was the failure
messages, the incremental finished with 2 failure messages, and nothing else.
The assumption I (erroneously) jumped to was that the scheduled backup
failed.

This was NOT the case.

What did happen, was that the Scheduler now uses QUIET mode instead of
Verbose.  Therefore all I saw was the failure messages, which of course made
my assumption seem correct.  Later I looked into the log again, and found the
completion messages, and saw that I had been incorrect.

The bad news is that I went into the DSM.OPT log, and added the VERBOSE
statement.  Unfortunately It seems to be ignored.  Today's log was the same -
no detail, just completion and failure messages.

I find this unacceptable; a problem has been opened with the support center.
They have been able to recreate it, and II believe they will take an APAR,
although I don't have the number.  If you are interested, contact me
privately, and I will give you the PMR number.

Jerry Lawson
jlawson AT thehartford DOT com


______________________________ Forward Header __________________________________
Subject: WindowsNT V3 Schedules failing on NTUSER.DAT
Author:  INTERNET.OWNERAD at SNADGATE
Date:    11/6/97 12:56 PM


I read a statement that someone had a problem with their schedules
failing when trying to back
the locked file NTUSER.DAT.
The resolution was to exclude the file.
My problem is that every night, backups on several servers hit locked
files that return the
same ANS message we get from NTUSER.DAT  (Different filenames on
different nights)
Since we can't get all our users to close their applications before
leaving each night, does this
mean our schedules will fail each night instead of skipping locked
files?
If this is the case, we will be unable to upgrade to V3.

Is anyone out there getting the following messages without having the
backup terminate?
ANS4090E Access to the specified file or directory is denied
ANS4090E Access to the specified file or directory is denied
ANS4638E Incremental backup of 'Q:' finished with 1 failure
<Prev in Thread] Current Thread [Next in Thread>