It looks like you have to backup the system object more than once???
Here is some data from only 1 backup of the system objects.
Following is the data from a second backup. Notice the size of the COMPDB,
EVENTLOG, and RSM all increase!
It is after the second backup that I was able to successfully restore the
system objects.
Total number of objects inspected: 7,527
Total number of objects backed up: 7,328
Total number of objects updated: 0
Total number of objects rebound: 0
Total number of objects deleted: 0
Total number of objects expired: 0
Total number of objects failed: 0
Total number of bytes transferred: 504.75 MB
Data transfer time: 69.29 sec
Network data transfer rate: 7,459.44 KB/sec
Aggregate data transfer rate: 652.23 KB/sec
Objects compressed by: 30%
Elapsed processing time: 00:00:12
tsm> q systemobject
Session established with server
Server Version 4, Release 2, Level 1.15
Server date/time: 08/15/2002 08:06:14 Last access: 08/14/2002 15:54:01
Size Backup Date Mgmt Class A/I File
---- ----------- ---------- --- ----
376 08/14/2002 16:03:01 DEFAULT A SYSTEM
OBJECT\TSMOSDRTST\COMPDB
376 08/14/2002 16:03:02 DEFAULT A SYSTEM
OBJECT\TSMOSDRTST\EVENTLOG
138,902,044 08/14/2002 16:04:57 DEFAULT A SYSTEM
OBJECT\TSMOSDRTST\SYSFILES
3,972,159 08/14/2002 16:07:09 DEFAULT A SYSTEM
OBJECT\TSMOSDRTST\REGISTRY
392 08/14/2002 16:07:11 DEFAULT A SYSTEM
OBJECT\TSMOSDRT\RSM
********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
Total number of objects inspected: 7,539
Total number of objects backed up: 1,838
Total number of objects updated: 0
Total number of objects rebound: 0
Total number of objects deleted: 0
Total number of objects expired: 0
Total number of objects failed: 0
Total number of bytes transferred: 141.17 MB
Data transfer time: 30.65 sec
Network data transfer rate: 4,715.24 KB/sec
Aggregate data transfer rate: 309.93 KB/sec
Objects compressed by: 41%
Elapsed processing time: 00:03:46
tsm> q systemobject
Size Backup Date Mgmt Class A/I File
---- ----------- ---------- --- ----
7,930 08/15/2002 08:09:24 DEFAULT A SYSTEM
OBJECT\TSMOSDRTST\COMPDB
5,593 08/15/2002 08:09:25 DEFAULT A SYSTEM
OBJECT\TSMOSDRTST\EVENTLOG
138,902,044 08/15/2002 08:11:19 DEFAULT A SYSTEM
OBJECT\TSMOSDRTST\SYSFILES
4,022,582 08/15/2002 08:14:15 DEFAULT A SYSTEM
OBJECT\TSMOSDRTST\REGISTRY
19,936 08/15/2002 08:14:17 DEFAULT A SYSTEM
OBJECT\TSMOSDRTST\RSM
"Cowperthwaite,
Eric" To: ADSM-L AT VM.MARIST DOT
EDU
<eric.cowperthwait cc:
e AT EDS DOT COM> Subject: Re: W2K - BMR
- using GHOST
Sent by: "ADSM:
Dist Stor Manager"
<[email protected].
EDU>
08/14/2002 07:39
PM
Please respond to
"ADSM: Dist Stor
Manager"
That method should work fine, based on my, admittedly, limited
understanding
of Win2K domains. I do know that our desktop support unit uses this sort of
method with Win2K desktops, ghost and system restores.
Eric
> -----Original Message-----
> From: Rob Schroeder [mailto:robs AT FAMOUSFOOTWEAR DOT COM]
> Sent: Wednesday, August 14, 2002 10:53 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: W2K - BMR - using GHOST
>
>
> After the install you can just change the server to be a member of a
> workgroup, then without rebooting, change it back to be a
> member of the
> domain. The SID will then be reconciled within AD. If this
> ghost image is
> a copy of a server already in production, then you may have
> to do this to
> both the clone and the cloned server.
>
> Rob
>
>
>
> Marc Levitan
> <marc.levitan@PFP To:
> ADSM-L AT VM.MARIST DOT EDU
> C.COM> cc:
> Sent by: "ADSM: Subject: Re:
> W2K - BMR - using GHOST
> Dist Stor
> Manager"
> <[email protected]
> .EDU>
>
>
> 08/14/2002 12:18
> PM
> Please respond to
> "ADSM: Dist Stor
> Manager"
>
>
>
>
>
>
> So, the SID in the ghost image has to be the same as the SID
> in the System
> Object that TSM has from the backup? (The one that will be restored)
>
> I ask because we used Ghost to remove the SID when we created
> the image.
>
> If this is the case, how do I know what the SID is so that I
> can use the
> free software to put it back?
>
> Thanks!
> Marc
>
>
>
>
> "Peter
> Pijpelink - To: ADSM-L AT VM.MARIST DOT EDU
> P.L.C.S. BV cc:
> Storage Subject: Re: W2K
> - BMR - using
> GHOST
> Consultants"
> <tsm AT PLCS DOT NL>
> Sent by:
> "ADSM: Dist
> Stor Manager"
> <ADSM-L AT VM DOT MA
> RIST.EDU>
>
>
> 08/14/2002
> 12:52 PM
> Please
> respond to
> "ADSM: Dist
> Stor Manager"
>
>
>
>
>
> You can use a free util which set the SID. We use this a lot,
> does it work
> in two second and you are done.
>
> email if you like to have, it is freeware
>
> greetings
> Peter
>
> At 11:40 14-8-2002 -0500, Cowperthwaite, Eric wrote:
> >Marc,
> >
> >The next problem you have, when using Ghost, is the Windows
> OS SID. Since
> >the System Object relies on the SID I would venture to guess
> that is the
> >issue. Try running SID Walker? I'm not sure. Or just put all
> your users on
> >Linux with Codeweaver :-).
> >
> >Eric
> >
> > > -----Original Message-----
> > > From: Marc Levitan [mailto:marc.levitan AT PFPC DOT COM]
> > > Sent: Wednesday, August 14, 2002 7:57 AM
> > > To: ADSM-L AT VM.MARIST DOT EDU
> > > Subject: Re: W2K - BMR - using GHOST
> > >
> > >
> > > What we have been doing is creating a container first
> using the DELL
> > > <CTRL-A> Utility.
> > > We then boot off a bootable CD ROM that has the ghost image on it.
> > >
> > > This image has W2K, TSM Client, and drivers, etc.. that
> allows us to
> > > connect to TSM Server and start the restore.
> > >
> > > I think this gets around the problem you are talking about???
> > > Do you know what could be causing the system object restore
> > > to quit before
> > > it completes successfully?
> > >
> > > Thanks,
> > > Marc
> > >
> > >
> > >
> > >
> > > "Cowperthwaite,
> > > Eric" To:
> > > ADSM-L AT VM.MARIST DOT EDU
> > > <eric.cowperthwait cc:
> > > e AT EDS DOT COM> Subject:
> > > Re: W2K - BMR - using GHOST
> > > Sent by: "ADSM:
> > > Dist Stor Manager"
> > > <[email protected].
> > > EDU>
> > >
> > >
> > > 08/14/2002 10:38
> > > AM
> > > Please respond to
> > > "ADSM: Dist Stor
> > > Manager"
> > >
> > >
> > >
> > >
> > >
> > > Ghost will work, if your drives are attached to a SCSI HBA.
> > > If they are
> > > attached to a RAID HBA you're out of luck. You can't load
> the RAID HBA
> > > drivers at DOS boot time and Ghost won't be able to find your
> > > RAID volumes.
> > >
> > > Eric W. Cowperthwaite
> > > Senior Consultant
> > > EDS
> > >
> > > -----Original Message-----
> > > From: Marc Levitan [mailto:marc.levitan AT PFPC DOT COM]
> > > Sent: Wednesday, August 14, 2002 5:16 AM
> > > To: ADSM-L AT VM.MARIST DOT EDU
> > > Subject: W2K - BMR - using GHOST
> > >
> > > Has anyone had success using Ghost (or other image software) to:
> > >
> > > 1) Put an image of W2K onto a server that includes the
> TSM client.
> > > 2) Connect to TSM Server and Restore System/boot partition
> > > (C:) and System
> > > Objects.
> > >
> > > I was able to successfully restore the System/boot
> partition (C:) and
> > > System Objects without using Ghost by manually installing
> W2K and TSM
> > > client.
> > > It is when I use Ghost to restore the W2k and TSM client that
> > > I run into
> > > the issue.
> > >
> > > What happens is that I can successfully restore the
> > > System/boot partition
> > > (C:) but when I try to restore the System Object, it stops
> > > before I get the
> > > RESTORE COMPLETE screen.
> > > Some of the items are restored, but it is not complete and
> > > becomes corrupt.
> > >
> > > Thanks,
> > > Marc Levitan
> > > Storage Manager
> > > PFPC Global Funds Services
> > >
>
|
