When you say "registry dump and backup", I assume you mean back up the
registry and the local drives. BACKUPREGISTRY can not be used from the
scheduler, but you can stick it in your client options file if you wish.
However, note that BACKUPREGISTRY YES is the default for NT 4.0.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Cahill, Ricky" <Ricky.Cahill AT EQUITAS.CO DOT UK>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
05/19/2003 02:15
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Backing Up NT Registry



Sorry for the late reply, been off having 4 teeth out :(

Is there anyway I can do the registry dump and backup in one??  The only
way
I can see to do it is to make a batch file up containing "backup registry"
and run this as a job from the scheduler before the main backup fires off?

Adding the -backupreg=yes to the commandline in the scheduler just comes
back with "invalid option" when the backup fires off as I'd assumed this
would do it all in one.

Thanks for the help.

        ..........Rikk

-----Original Message-----
From: Stapleton, Mark [mailto:stapleto AT BERBEE DOT COM]
Sent: 12 May 2003 19:26
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Backing Up NT Registry


From: Cahill, Ricky [mailto:Ricky.Cahill AT EQUITAS.CO DOT UK]
> This has to be simple but I really cant see what I need to do.
>
> Server ver 5.1.6.2
> NT Client ver 5.1.5.15
> OS ver NT4 +sp6a
>
> I have a SQL box that I backup d:\mssql\diskdumps on but am
> now required to
> also backup the registry on this box.
>
> I added -backupreg to the commandline in the schedule which
> did nothing, on
> going through the docs it appears I need to do :-
>
> backup registry - which drops it in an adsm.sys directory.
>
> Then backup this directory??

If you're seeing an adsm.sys directory, the registry is being backed up.
The Microsoft API for system object backups requires TSM to copy the
registry data to a flat file and back it up, much like what you're doing
when you create cold dumps of your SQL data.

If you're still not sure, open a GUI-based client session, go to
restores, and see if your registry data is available. If it is, you're
good to go.

--
Mark Stapleton (mark.stapleton AT berbee DOT com)
Berbee Information Networks
Office 262.521.5627


****************************************************************************************************
Equitas Limited, 33 St Mary Axe, London EC3A 8LL, UK
NOTICE: This message is intended only for use by the named addressee
and may contain privileged and/or confidential information.  If you are
not the named addressee you should not disseminate, copy or take any
action in reliance on it.  If you have received this message in error
please notify postmaster AT equitas.co DOT uk and delete the message and any
attachments accompanying it immediately.

Equitas reserve the right to monitor and/or record emails, (including the
contents thereof) sent and received via its network for any lawful
business
purpose to the extent permitted by applicable law

Registered in England: Registered no. 3173352 Registered address above
****************************************************************************************************