If the one you try to jump out of is
designed by the same folks that brought the others ones you’ll probably bounce
off the blue screen in front of it…
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Randy Samora
Sent: Friday, February 15, 2008
9:40 AM
To: Rosenkoetter, Gabriel
Cc:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Restoring
Shadow Copy Component/System State
I wish I
had the option of doing Windows infrequently. 800 clients, all Windows
here. I’m getting ready to jump out of one if this keeps up.
From: Rosenkoetter,
Gabriel [mailto:Gabriel.Rosenkoetter AT radian DOT biz]
Sent: Friday, February 15, 2008
8:36 AM
To: Randy Samora
Cc:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu]
Restoring Shadow Copy Component/System State
Though the client will show up under host properties with
its real OS type (probed from the master), it's my understanding that it'd be
Best Practice to change its OS type in the policy definition (ie, remove it and
readd it with the same name). I also don't know what effect that does or
doesn't have. (I do Windows as infrequently and rapidly as I possibly can.)
--
gabriel rosenkoetter
Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup & Recovery
gabriel.rosenkoetter AT radian DOT biz, 215 231 1556
From: Randy
Samora [mailto:Randy.Samora AT stewart DOT com]
Sent: Friday, February 15, 2008
9:11 AM
To: Rosenkoetter, Gabriel
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu]
Restoring Shadow Copy Component/System State
I’ve
always wondered about that. In the client list of the policy, if I say
the client is a 2000 Server and it is actually a 2003 Server. Does NBU
override my 2000 Server selection?
From: Rosenkoetter,
Gabriel [mailto:Gabriel.Rosenkoetter AT radian DOT biz]
Sent: Friday, February 15, 2008
8:01 AM
To: Randy Samora
Cc:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu]
Restoring Shadow Copy Component/System State
No, ALL_LOCAL_DRIVES includes the appropriate one of
System_State:\ or Shadow Copy Components:\ based on how you've listed the
client (Windows2000 v. WindowsNET, for example).
Or, I think it's based on that. It might be based on what
the client's bpcd says when the media server connects to it.
(The docs are hazy. Ahem, Veri... er, Symantec readers.)
--
gabriel rosenkoetter
Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup & Recovery
gabriel.rosenkoetter AT radian DOT biz, 215 231 1556
From: Randy Samora
[mailto:Randy.Samora AT stewart DOT com]
Sent: Thursday, February 14, 2008
4:22 PM
To: WEAVER, Simon (external)
Cc:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu]
Restoring Shadow Copy Component/System State
I’m
using the All Local Drives directive. Does it make a difference to list
Shadow Copy Components separately?
From: WEAVER, Simon
(external) [mailto:simon.weaver AT astrium.eads DOT net]
Sent: Thursday, February 14, 2008
12:56 AM
To: Randy Samora;
veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu]
Restoring Shadow Copy Component/System State
Randy
In the backup policy where this client
belongs, are you selecting the "Shadow Copy Components" directive?
S.
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Randy Samora
Sent: Wednesday, February 13, 2008
11:21 PM
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Restoring
Shadow Copy Component/System State
Part of
my requirements are test restores of critical boxes in a lab environment.
The lab is isolated and when I restore a client, there’s not really much
we can test because the client looks for the production network. Today I
had to restore a Windows 2003 Server in the production environment and most of
the registry wasn’t restored; services and other objects were
missing. With the test restores, I always had the option of doing an
ntbackup of the System State and then I would run a full backup of the
client. I’d take my tape to the lab, run a full restore, but before
I rebooted the restored client, I restored the ntbackup of the System State
(Shadow Copy Component.) That seemed to work just fine. But today
when the server blew up, there was no opportunity to do an ntbackup of the SS
first. I asked Symantec last year if the ntbackup was still needed and
they said no, a full backup and restore should recover the client. I just
never had the chance to test that theory.
Am I
missing a step? I installed the OS from a basic CD install, loaded the
NBU client, and then did a full restore. But it’s as if the system
state was never restored so I’m wondering if I’m even backing it
up. How can I tell? Do I need VSS or VSP activated in order to get
a good copy of the system state? We turned VSP off over a year ago
because we were having problems with the orphaned cache files. I’ve
never gone back and changed the setting on most of the clients and my plans
were to start using VSS but haven’t gotten to that task either. Is
there a trick or an added step to getting a good backup of the system state on
a Windows 2003 Server server or is there a trick to restoring it?
Thanks,
Randy
|
This email (including any attachments)
may contain confidential and/or
privileged information or information otherwise protected from disclosure.
If you are not the intended recipient, please notify the sender
immediately, do not copy this message or any attachments and do not use it
for any purpose or disclose its content to any person, but delete this
message and any attachments from your system. Astrium disclaims any and all
liability if this email transmission was virus corrupted, altered or
falsified.
---------------------------------------------------------------------
Astrium Limited, Registered in England and Wales No. 2449259
REGISTERED OFFICE:-
Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
|
