ADSM-L

Re: Need Help - backup of registry NT, failures

1999-10-20 10:00:55
Subject: Re: Need Help - backup of registry NT, failures
From: "Prather, Wanda" <PrathW1 AT CENTRAL.SSD.JHUAPL DOT EDU>
Date: Wed, 20 Oct 1999 10:00:55 -0400
We are having exactly the same problem.
It does seem to be just a timing thing - does not hit all clients.
We are running 3.1.0.6j client.

I think it is true that if the particular file is not sent to the server, as
in your log below, then you don't have a good backup of the registry.

We found 2 easy ways around it (with thanks to Andy Raibeck!)

1) If we pull down the Utilities menu, and run a registry backup by itself,
for some reason we don't see the problem and have a good registry backup.
This would only be practical for people who are doing incremental backups
via the GUI, anyway.

2) We changed the serialization setting in the backup copy group from STATIC
to SHARED STATIC.  That just means that ADSM will try up to 4 times to get
control of the file and back it up before giving up and issuing the "user
file changed" message.  This doesn't really slow backups down much, because
the retries happen VERY fast.  So it's a harmless change, and we haven't had
the problem since.




> -----Original Message-----
> From: Michael Bartl [SMTP:michael.bartl AT ZENTRALE.ADAC DOT DE]
> Sent: Wednesday, October 20, 1999 8:42 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      AW: Need Help - backup of registry NT, failures
> 
> Hi Rene,
> we had the same problem quite a time ago. I'll try to explain what leads
> to
> the error:
> Before ADSM starts backing up files it uses an NT API function to write
> the
> contents of your systems registry into the adsm.sys directory structure.
> The
> files written do have the same layout as the native registry files in
> winnt\system32\config.
> Now probably out of a timing problem ADSM tried to backup adsm.sys\*.* at
> the SAME time as the results of the API call got written to this
> directory,
> what lead to the conflict situation and resulted in the file being
> skipped.
> I think the reason for the problem comming up on one machine and not on
> another one could be that the registry uses varying amounts of space from
> machine to machine, so the time overlap between the two functions occurs
> or
> not.
> 
> The problem did never again occur with the newer NT client versions, we've
> found 3.1.0.6q and .7f the most stable versions of V3.
> 
> When you don't have a possibility to install a new client right now but
> only
> in a few day, and you want to have a valid copy of your registry, just do
> one incremental session with the addistional option "-BACKUPREGISTRY=NO".
> That skips the creation of the adsm.sys contents (and leaves those from
> the
> last session active) and you can circumvent the conflict.
> 
> Good luck,
> Best regards,
> Michael
> --
> Michael H. Bartl
> ADAC e.V. (RZ/PPO, Storagemanagement, Datensicherung u. Notfallvorsorge)
> Tel.: (089) 7676-4063, Fax: (089) 7676-8161
> mailto:michael.bartl AT zentrale.adac DOT de
> http://www.adac.de
> 
> 
> -----Ursprüngliche Nachricht-----
> Von: Lambelet,Rene,VEVEY,FC-SIL/INF. [mailto:Rene.Lambelet AT nestle DOT com]
> Gesendet am: Mittwoch, 20. Oktober 1999 12:44
> An: 'ADSM-L AT VM.MARIST DOT EDU'
> Cc: 'jlawson AT THEHARTFORD DOT COM'; 'michael.bartl AT zentrale.adac DOT de'
> Betreff: Need Help - backup of registry NT, failures
> 
>                 Jerry,
>                 why do you explicitly backup the registry?
>                 Isn't it included in the incremental backup, by default?
>                 Please explain that to me.
> 
> 
> 
>                 We have a problem here and I have to give explanations to
> our NT guy. He's loosing confidence in adsm.
>                 Running NT client adsm 3.1.0.3, server OS/390 3.1.2.20.
> 
>                 On many NT clients, the backup of registry seems to be ok,
> we have following files in adsm.sys:
>                 in Adsm.sys/registry/vevpil01/machine/ : Sam, Security,
> Software, System files
>                 in Adsm.sys/registry/vevpil01/Users/ : Default file
>                 in Adsm.sys/registry/vevpil01/Users/System/ : Syste000 and
> Syste000.Key files
> 
>                 But the backup of adsm.sys does not work ( 2 failures ):
> please see below extract of dsmerror and schedlog.
> 
>                 Does this mean I cannot restore the adsm.sys?
>                 Is this a problem which is corrected in 3.1.0.7?
>                 Should I specifically backup the registry as you recommend
> below?
> 
>                 Thanks in advance for any clue and explanation (from
> anybody
> listening),
> 
> Rene Lambelet  
> Nestec SA - 55, Av. Nestle - CH-1800 Vevey
> Tel: ++41'21'924'35'43 / Fax: ++41'21'924'45'89
> E-Mail: rene.lambelet AT nestle DOT com
> 
>                 extract from dsmsched.log
>                 Executing scheduled command now.
>                 10/20/1999 03:13:58 Node Name: VEVPIL01
>                 10/20/1999 03:13:58 Session established with server ADSM:
> MVS
>                 10/20/1999 03:13:58   Server Version 3, Release 1, Level
> 2.20
>                 10/20/1999 03:13:58   Data compression forced off by the
> server
>                 10/20/1999 03:13:58   Server date/time: 10/20/1999
> 03:11:27
> Last access: 10/19/1999 21:04:28
>                 10/20/1999 03:13:58 --- SCHEDULEREC OBJECT BEGIN NT_INCR2
> 10/20/1999 02:45:00
>                 10/20/1999 03:14:00 
>                 Registry Backup Function Invoked.
>                 10/20/1999 03:14:00 
>                    Save Registry Key: RootKey 'HKEY_LOCAL_MACHINE', SubKey
> 'SOFTWARE'
>                 10/20/1999 03:14:03 
>                    Save Registry Key: RootKey 'HKEY_LOCAL_MACHINE', SubKey
> 'SYSTEM'
>                 10/20/1999 03:14:03 
>                    Save Registry Key: RootKey 'HKEY_LOCAL_MACHINE', SubKey
> 'SECURITY'
>                 10/20/1999 03:14:03 
>                    Save Registry Key: RootKey 'HKEY_LOCAL_MACHINE', SubKey
> 'SAM'
>                 10/20/1999 03:14:03 
>                    Save Registry Key: RootKey 'HKEY_USERS', SubKey
> '.DEFAULT'
> 
>                 10/20/1999 03:14:04 ANS1427I Registry Backup function
> completed successfully.
>                 10/20/1999 03:14:24 ANS1228E Sending of object
> 'C:\adsm.sys\Registry\VEVPIL01\Machine' failed
>                 10/20/1999 03:14:24 ANS1840E File
> 'C:\adsm.sys\Registry\VEVPIL01\Machine' changed during processing.  File
> skipped.
>                 10/20/1999 03:14:25 ANS1228E Sending of object
> 'C:\adsm.sys\Registry\VEVPIL01\Users' failed
>                 10/20/1999 03:14:25 ANS1840E File
> 'C:\adsm.sys\Registry\VEVPIL01\Users' changed during processing.  File
> skipped.
>                 10/20/1999 03:16:20 ANS1802E Incremental backup of 'C:'
> finished with 2 failure
> 
>                 extract from dsmerror.log
> 
>                 10/20/1999 03:14:21 AltStreamSize(): CreateFile: Win32
> RC=32
>                 10/20/1999 03:14:21 AltStreamSize(): CreateFile: Win32
> RC=32
>                 10/20/1999 03:14:21 AltStreamSize(): CreateFile: Win32
> RC=32
>                 10/20/1999 03:14:21 AltStreamSize(): CreateFile: Win32
> RC=32
>                 10/20/1999 03:14:21 AltStreamSize(): CreateFile: Win32
> RC=32
>                 10/20/1999 03:14:24 ANS1228E Sending of object
> 'C:\adsm.sys\Registry\VEVPIL01\Machine' failed
>                 10/20/1999 03:14:24 ANS1840E File
> 'C:\adsm.sys\Registry\VEVPIL01\Machine' changed during processing.  File
> skipped.
>                 10/20/1999 03:14:25 ANS1228E Sending of object
> 'C:\adsm.sys\Registry\VEVPIL01\Users' failed
>                 10/20/1999 03:14:25 ANS1840E File
> 'C:\adsm.sys\Registry\VEVPIL01\Users' changed during processing.  File
> skipped.
>                 10/20/1999 03:16:20 ANS1802E Incremental backup of 'C:'
> finished with 2 failure
>                   
<Prev in Thread] Current Thread [Next in Thread>