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



>       -----Original Message-----
>       From:   JerryLawson [SMTP:jlawson AT THEHARTFORD DOT COM]
>       Sent:   Tuesday, October 19, 1999 8:21 PM
>       To:     ADSM-L AT VM.MARIST DOT EDU
>       Subject:        Re: Antwort: Need Help
>
>       Excellent, but also, don't forget to backup the registry on the
> machine
>       first; otherwise you can't get back all of the customization, etc.
> I usually
>       have a bat file in the ALLUSERS startup window that does the
> following:
>
>            DSMC REGBACK USER CURUSER
>
>       Then when you do all the restores, after the machine has been
> rebooted, run
>       the reverse process
>
>            DSMC REGREST USER CURUSER
>
>       When complete - power the machine off, then reboot, and you should
> be golden.
>
>       Jerry Lawson
>
>
>       ______________________________ Reply Separator
> _________________________________
>       Subject: Antwort: Need Help
>       Author:  owner-adsm-l AT VM.MARIST DOT EDU at SMTP
>       Date:    10/19/99 1:33 PM
>
>
>       Mike,
>       it is a good idea to install a second NT to a directory different
> from the
>       (lost) productive one. You start this NT, copy boot.ini asied (not
> needed,
>       but helpful in case of failure) install ADSM and restore all the
> stuff from
>       ADSM. This restore should bring back everything since you have no
> open
>       files in the NT directory that ADSM wants to overwrite. It may be
> required
>       to put back the registry files from the adsm.sys-directory to the
> new
>       NT-directory (where they belong: %WinNTRoot%\system32\config\).
>
>       Having done this, everything should work fine again. But you should
> be
>       aware of problems with WinNT domain structure. It is recommended not
> to put
>       the emergency-NT into a domain structure but to put it into a
> NT-workgroup.
>
>       Yours,
>       Matthias
>
>
>
>
>
>
>       Mike Dillon <Mike.dillon AT WCOM DOT COM> am 19.10.99 18:13:39
>
>       Bitte antworten an "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT 
> EDU>
>
>
>       An:   ADSM-L AT VM.MARIST DOT EDU
>       Kopie:     (Blindkopie: Matthias Hensel/BE/USR/SHG)
>
>
>       Thema:    Need Help
>
>
>
>
>
>       Does anyone have information about using NT Clients being backed-up
> by a
>       Unix ADSM server.  We have experienced successful restores of the NT
>       server OS's, however when we try to restore the applications they
> fail.
>       Errors are received and the applications are lost.  Scenario:  NT
> 4.0
>       with IIS 4.0, several virtual sites setup and when a backup is
> complete,
>       we format the server and install OS and ADSM backup client.  Once
> the
>       client is installed the  we begin the restore.  Aproximently 115
> files
>       are not restored, many in the winnt\system32 directory.  The IIS is
> not
>       restored.  Does anyone have any experience trying to restore
>       applications from a ADSM server to the NT clients?
>
>
>       Michael Dillon
>       Sr. NT System Administrator