Wayne
Yes. In essence, if you create a policy with say, the C: Drive for a
Windows 2003 Server, then the C: Drive will get backed up.
However, the critical "system / boot files / registry and configuration"
information of Shadow Copy Components will NOT be backed up.
 
Unless you either:
1) Create a Directive for System State (ie: Win2k) or Shadow Copy
(Win2k3)
2) Use All Local Drives Directive.
 
Simon

________________________________

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of BeDour,
Wayne
Sent: Tuesday, June 08, 2010 8:26 PM
To: judy_hinchcli...@administaff.com; steve.foga...@gmail.com;
layne.barber....@csd.disa.mil
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] ALL_LOCAL_DRIVES question



Is all the registry information for a Windows 2003 system included in
the Shadow Copy Components?

 

Wayne BeDour 
Unix System Administrator 
PH: 248-447-1739 
Internet: wbed...@lear.com 

________________________________

From: judy_hinchcli...@administaff.com
[mailto:judy_hinchcli...@administaff.com] 
Sent: Tuesday, June 08, 2010 3:19 PM
To: steve.foga...@gmail.com; layne.barber....@csd.disa.mil
Cc: veritas-bu@mailman.eng.auburn.edu; BeDour, Wayne
Subject: RE: [Veritas-bu] ALL_LOCAL_DRIVES question

 

Ok, slight correction

 

2003 servers it gets  Shadow Copy Components:\

 

2008 servers it gets System_State:\

 

(but that could be dependent on vsp or vss - not sure)

But my policies say All-Local_Drives and it has gotten theses.

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Steve
Fogarty
Sent: Tuesday, June 08, 2010 2:01 PM
To: Barber, Layne Mr CTR US DISA CDM242
Cc: veritas-bu@mailman.eng.auburn.edu; BeDour, Wayne
Subject: Re: [Veritas-bu] ALL_LOCAL_DRIVES question

 

ALL_LOCAL_DRIVES doesn't grab the SYSTEM_STATE/SHADOW_COPY_COMPONENTS
for my Windows clients.  At least it never used to?  I had to explicitly
put those in my file list.  Most of my policies were created under 5.x,
now running 6.5.6.  Maybe something has been ":fixed".

On Tue, Jun 8, 2010 at 2:56 PM, Barber, Layne Mr CTR US DISA CDM242
<layne.barber....@csd.disa.mil> wrote:

The ALL_LOCAL_DRIVES directive keeps you from having to know all the
drives local to a client. In windoze, it will also grab the system
state/shadow copy components. You use it to simply catch everything that
is local to the client instead of having to know ALL of the details of
the client.


-----Original Message-----
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of BeDour,
Wayne
Sent: Tuesday, June 08, 2010 12:40
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] ALL_LOCAL_DRIVES question

Our environment, HP-UX 11-31 currently running one master and media
server running NetBackup 6.5.2.  Running mostly unix / Linus backups and
a couple windows b/u's thrown in for good measure.  Let me start this
out by stating that I just know enough Windows to scrape by and get me
into trouble.  That said, I'm setting up a backup for a Windows box and
have been reading and trying to figure out exactly what the
ALL_LOCAL_DRIVES directive is used for.  Why not just create a policy
and point to C:\ for example?  Can someone give me a simple explanation
for ALL_LOCAL_DRIVES and when it should be used?

Thanks in advance...

Wayne BeDour

Unix System Administrator

PH: 248-447-1739

Internet: wbed...@lear.com <mailto:wbed...@lear.com>


**********************
** LEGAL DISCLAIMER **
**********************

This E-mail message and any attachments may contain legally privileged,
confidential or proprietary information. If you are not the intended
recipient(s), or the employee or agent responsible for delivery of this
message to the intended recipient(s), you are hereby notified that any
dissemination, distribution or copying of this E-mail message is
strictly prohibited. If you have received this message in error, please
immediately notify the sender and delete this E-mail message from your
computer.

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

 

**********************
** LEGAL DISCLAIMER **
**********************

This E-mail message and any attachments may contain 
legally privileged, confidential or proprietary 
information. If you are not the intended recipient(s),
or the employee or agent responsible for delivery of 
this message to the intended recipient(s), you are 
hereby notified that any dissemination, distribution 
or copying of this E-mail message is strictly 
prohibited. If you have received this message in 
error, please immediately notify the sender and 
delete this E-mail message from your computer.

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.
-o-
Astrium Limited, Registered in England and Wales No. 2449259
Registered Office:
Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
_______________________________________________
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Reply via email to