Veritas-bu

[Veritas-bu] Windows 2000 System State Backups on Solaris Mas ter

2001-05-17 16:40:04
Subject: [Veritas-bu] Windows 2000 System State Backups on Solaris Mas ter
From: limelite AT ti DOT com (Young, Ken)
Date: Thu, 17 May 2001 15:40:04 -0500
Oops, I may have mispoken on my previous message:

"Based on my limited testing you must also check "Cross mount points" in the
Win2K class on the backup server in order for it to backup the
System_State:\ and you can specify System_State:\ on the backup server's
file list."

Well, I did say "limited testing". Strangely, testing System_State backups
again, it appears that one does not to check "Cross mount points" in order
to back it up. However, if I specify system_state:\ rather than
System_State:\ in the backup server's file list, I get an error 71, none of
the files in the file list exist so case sensitivity is in play here. Test
it yourself and see if you get the same results.

As far as Windows 2000 goes, from
http://seer.support.veritas.com/docs/235143.htm, NetBackup 3.4.1 is
completely interoperable with NetBackup 3.4 with the latest Cumulative
patch. Patch J0850645 is a NetBackup 3.4 Patch, not for 3.4.1. If patch
J0850645 is applied to version 3.4, it is not Windows 2000 Logo certified.

I apologize for the misinformation ... Hopefully, there are no other errors.
:-)


Cheers,
Ken

-----Original Message-----
From: Young, Ken 
Sent: Thursday, May 17, 2001 1:12 PM
To: 'Fairchild, David'; 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: RE: [Veritas-bu] Windows 2000 System State Backups on Solaris
Mas ter


Though we haven't fully finished testing NB 3.4 yet nor are we running AD,
from Note 9 of NB 3.4.1 release notes which can be downloaded from
http://seer.support.veritas.com/docs/235054.htm:

- For Windows 2000 clients if you do not use the All_local_drives directive
in the files list, you must specify System_state:\ in the file list to
ensure that the Windows 2000 system state is backed up. 

Adding System_State:\ to the file list on the backup server should be the
preferable way to do it rather than include it on all the clients.

Based on my limited testing you must also check "Cross mount points" in the
Win2K class on the backup server in order for it to backup the
System_State:\ and you can specify System_State:\ on the backup server's
file list. 

On the client side, it looks like you can exclude System_State:\ and include
these three files that make up the System_State:\ (according to NB):

System_State:\Boot_Files
System_State:\COM+_Class_Registration_Database
System_State:\Registry

if you chose to do it that way. Haven't tested this yet or any restores of
System_State:\.

Bear in mind that you can only include a file or folder only if it is a
subset of the exclude list. For example:

If you exclude c:\, then you can include c:\temp but if you just include
c:\temp with an empty exclude list, then c:\temp would not be backed up, at
least it was that way with v3.2.

Also make sure you have the patch that fixes the 100% CPU spike per
http://seer.support.veritas.com/docs/232542.htm. Hope that helps ... a
little, perhaps?


Regards,
Ken Young
Texas Instruments Inc.
214-480-7686

-----Original Message-----
From: Fairchild, David [mailto:dfairchild AT firstam DOT com]
Sent: Thursday, May 17, 2001 10:47 AM
To: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: [Veritas-bu] Windows 2000 System State Backups on Solaris
Master


Ran into an issue that needs some verification and/or a solution. Our
corporate data center uses NB 3.4 with a Win2k master to backup other Win2k
machines. When setting up the class their is an option to collect disaster
recovery information to include the WIndows 2000 system state or one can do
an include to include the System_State:\ to get a backup of Active Directory
Information. This is all fine and well and working perfectly. 

Now comes the new issue. We have another project that is external to us
where all backups for now will be handled by an SSP that uses NB 4.3 on
solaris. Same issue as above we need the system state of Win2k boxes backed
up, but are uncertain if this will be. They want us to do client side
includes.

1. Can I do an include of the system state at the client "system_state:\" ? 

2. It didn't appear, after talking with the tech supp., that the solaris
master could specify either "Collect Disaster Recovery.." or
"System_State:\" 

3. Anyone out there done full disaster recoveries of Win2k Active Directory
when the Master is Solaris? Any luck?

::::::::::::::::::::::::::::::::::::::::::::::::::::::
David Fairchild
Enterprise Consulting Services
First American Corporation
(714)800-3027
(714)235-5330

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

<Prev in Thread] Current Thread [Next in Thread>