Re: Backing up SYSTEMOBJECT on Win2K machines

2005-01-19 17:17:48
Subject: Re: Backing up SYSTEMOBJECT on Win2K machines
From: "Robertson, Louis" <louis.robertson AT BEARINGPOINT DOT COM>
Date: Wed, 19 Jan 2005 22:01:29 -0000

In the event of a disaster you will probably be restoring to dissimilar 
equipment.  If that is the case and you are running W2K with SP3 and you are 
using the ntbackup of the systemstate you definitely want to read Microsoft's 
knowledge base article 249694, ( 
)specifically the section on changing the registry key - KeysNotToRestore.  
Prior to installing SP4 our test restores to dissimilar equipment was not very 
successful until we made the "KeysNotToRestore" registry change referenced in 
this article.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Jones, Eric J
Sent: Tuesday, January 18, 2005 1:52 PM
Subject: Backing up SYSTEMOBJECT on Win2K machines

Good Afternoon.
I've seen a few post on the backup of the SYSTEMOBJECT for win2k and I'm 
looking for the best way to backup our win2K systems.
I have 4 systems that I currently backup with another 10+ to go.
Most of my machines are UNIX so I've never had a problem with this.
It seems like the DB is growing faster than it use to and I'd like to prevent 
rapid growth once the others are included.
It's my understanding that all of the SYSTEMOBJECT files are backed up with 
every backup(incremental).
We keep all data for 90 days and the systems are backed up Monday-Friday .
Is it more efficient/better to have ntbackup backup the SYSTEMOBJECT to a file 
before the TSM backup, then have TSM backup this file nightly with the regular 
TSM backup?
Is there any problem with recovery of the machine using this method(ntbackup 
then TSM)?
Is there any advantages/disadvantages to using this method?
Generally how many files does the SYSTEMOBJECT backup contain?
We are currently on AIX 5.2/TSM 5.2.2 server and win2K SP3 clients.

Have a Great Day,

The information in this email is confidential and may be legally privileged.  
Access to this email by anyone other than the intended addressee is 
unauthorized.  If you are not the intended recipient of this message, any 
review, disclosure, copying, distribution, retention, or any action taken or 
omitted to be taken in reliance on it is prohibited and may be unlawful.  If 
you are not the intended recipient, please reply to or forward a copy of this 
message to the sender and delete the message, any attachments, and any copies 
thereof from your system.