Ah Ha.  That explains it.  The hostname has to be the same.  The hardware
is almost a duplicate.  We'll see if it's similar enough with this test.
Nothing ventured, nothing gained.




                             "Prather, Wanda"
                             <Wanda.Prather@JHUAPL. To:     ADSM-L AT VM.MARIST 
DOT EDU
                             EDU>                   cc:
                      Sent by: "ADSM: Dist Stor     Subject:  Re: Restore of 
System Object
                      Manager"
                      <ADSM-L AT VM.MARIST DOT EDU>


                             03/28/2003 04:05 PM
                      Please respond to "ADSM: Dist
                      Stor Manager"









Brad,

TSm will not restore a SYSTEM OBJECT to a different machine.

Now it can be a physically different machine, but it must have the same
hostname, and it must have identical hardware, as you are restoring the
registry, which includes hardware information.




-----Original Message-----
From: Brad Wallace [mailto:Bradley_Wallace AT GLIC DOT COM]
Sent: Friday, March 28, 2003 2:55 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Restore of System Object


I'm trying to restore the System Object of one Win2K server to another
Win2K server.  Kind of a disaster recovery test.

TSM Client Version on source machine is 4.2.0, TSM Client Version on
destination machine is 4.2.2.  Copied the dsm.opt file from the source
machine to the destination machine.  When on the destination machine, I can
seen and restore normal files that were backed up on the source machine.
But, I can not restore the system object to the destination machine.

The system object appears available to restore on the source machine.  When
I do
      q systemobject
I get results.  But when I do the same thing on the destination machine, I
get a message stating that no system objects were backed up.

What am I missing?