Veritas-bu

Re: [Veritas-bu] ALL_LOCAL_DRIVES question

2010-06-08 16:23:11
Subject: Re: [Veritas-bu] ALL_LOCAL_DRIVES question
From: "Barber, Layne Mr CTR US DISA CDM242" <layne.barber.ctr AT csd.disa DOT mil>
To: "Steve Fogarty" <steve.fogarty AT gmail DOT com>
Date: Tue, 8 Jun 2010 14:28:14 -0500
Page 189 of the admin guide vol I (note that on win2k3 system state includes 
shadow copy components):


ALL_LOCAL_DRIVES example 1
Assume that Allow multiple data streams is enabled in the auto-discovery mode. 
Assume that the client is a Windows system with two drive volumes, C:\ and D:\. 
The backup selections list contains:
ALL_LOCAL_DRIVES
For this backup selections list, NetBackup generates:
■
One stream for C:\
■
One stream for D:\
For a UNIX client, NetBackup generates a stream for each file system.
Policies 189
Rules to indicate paths in the backup selections list
SYSTEM_STATEis also backed up because SYSTEM_STATE is included in the 
ALL_LOCAL_DRIVES directive.
ALL_LOCAL_DRIVES example 2
Assume that Allow multiple data streams is not enabled. Assume that the client 
is a Windows system with two drive volumes, C:\ and D:\. The backup selections 
list contains:
ALL_LOCAL_DRIVES
Here, NetBackup backs up the entire client in one data stream that contains the
data from both C:\ and D:\.
SYSTEM_STATEis also backed up because SYSTEM_STATE is included in the
ALL_LOCAL_DRIVES directive


-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu 
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Steve 
Fogarty
Sent: Tuesday, June 08, 2010 14:01
To: Barber, Layne Mr CTR US DISA CDM242
Cc: veritas-bu AT mailman.eng.auburn DOT 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.ctr AT csd.disa DOT 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-bounces AT mailman.eng.auburn DOT edu 
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of BeDour, 
Wayne
        Sent: Tuesday, June 08, 2010 12:40
        To: veritas-bu AT mailman.eng.auburn DOT 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: wbedour AT lear DOT com <mailto:wbedour AT lear DOT 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 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>