Whenever you do a backup of an NT system using the GUI interface or the
background scheduler (installed as an NT service), the first thing ADSM does
is back up the NT registry.  If you look at the output of the scheduler, you
can see where each hive is backed up.  It does this by calling a Microsoft
API to create a logical copy of the registry, which is then saved in the
adsm.sys directory before being sent to the ADSM server.

You will still get errors in the scheduler log against NTUSER.DAT and
NTUSER.LOG.  But if you look carefully, this is the USER PROFILE of anyone
currently logged on, not the resistry itself.

For most people's NT systems, since the background scheduler runs under the
SYSTEM account, not having that profile backed up is not an issue.

If you have NT workstations where people are logged on while the backup is
running and their profiles  routinely fail backup, you can circumvent by
creating a .bat file with the command:
 dsmc regback user curuser
and putting it in the user's startup group.  This does a logical registry
backup of the currently logged on user whenever the user logs on, and
insures that the user's profile will always get backed up.

If the registry isn't backing up for you, check to see if you are at least
at the 3.1.0.6 level of the WIn32 client.  Registry backup works.


> -----Original Message-----
> From: McGraw, Ryan [SMTP:Ryan.McGraw AT HBOC DOT COM]
> Sent: Friday, July 23, 1999 11:12 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Backup questions?
>
> Can ADSM automatically backup an NT registry? How about Novell DB Schema
> (NDS)? O any open system files (.sys files)? If yes to any of these...how?
> I
> haven't been able to figure these out. Thanks for any help.
>
>
>
> Ryan McGraw
> Mckesson HBOC
> Technical Consultant
> 404-338-3087
> 1800-454-8349 pgr
> ryan.mcgraw AT hboc DOT com
> ------------------------------------