[Veritas-bu] NBU 7.0 media server upgrade problem

[NBU]

Hi,

Can u share the procedure for upgrading netbackup from 6.5 to 7.0


Thanks in Advance

+--
|This was sent by qureshiu...@rediffmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


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

[Veritas-bu] Upgradation Steps - 6.5.5 to 7.0

[NBU]

Hi Forum,

Need to upgrade my setup which is on NBU 6.5.5 (Solaris) to NBU 7.0

Pls. inform/suggest the steps involved to do so.


Thanks in Advance

+--
|This was sent by qureshiu...@rediffmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


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

Re: [Veritas-bu] isilon backup accelerator

[David Magda]

On Jun 9, 2010, at 19:27, A Darren Dunham wrote:

> NFS cannot carry the NTFS ACLS though.  So conceivably you can do all
> CIFS backups and get all security structures.  (I do NDMP and have
> mainly UNIX servers, so it's not something I've tried to test).

Well, NFSv4 does NTFS-style ACLs. See Section 5.11 of the NFSv4 spec  
(RFC 3530). There's also a draft on mapping NFSv4 and draft-POSIX ACLs  
("draft-ietf-nfsv4-acl-mapping-05").

Don't know of many systems that can show both though. I believe  
OpenSolaris can do UID-SID mapping and such with ACLs if you're  
exporting a ZFS file system to both NFS and CIFS/SMB.

NetApp should be able to handle it if you use "mixed" QTrees:

http://www.netapp.com/us/communities/tech-ontap/nfsv4-0408.html

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

Re: [Veritas-bu] isilon backup accelerator

[A Darren Dunham]

On Mon, Jun 07, 2010 at 09:03:12AM -0500, Ed Wilts wrote:
> If you have a NetApp filer (and there may be other NAS heads that have the
> same functionality) that have multiple security models on the same data,
> this approach simply will not work.  We have some file systems that use both
> Unix and NTFS security so backing the data up using either CIFS or NFS will
> miss the rest of the security information.

Just a note on this point.  Don't know about other systems, but Netapp
says that CIFS backups do properly save UNIX security info.  It's saved
in a SMB structure.

NFS cannot carry the NTFS ACLS though.  So conceivably you can do all
CIFS backups and get all security structures.  (I do NDMP and have
mainly UNIX servers, so it's not something I've tried to test).

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

Re: [Veritas-bu] Large Full schedule, DSSU and Shoe Shinning

[Ed Wilts]

On Wed, Jun 9, 2010 at 11:08 AM, Dean  wrote:

> Shoe shining is less of a problem with modern tape drives, as they have
> this "speed matching" which will slow the tape drive's throughput down to
> match, as closely as possibe, the speed that data is coming in from the
> host...
>
> "The IBM LTO-4 drive has the new technology that matches dynamic speed at
> any of the 6 speeds of 30MB/sec, 48MB/sec, 66MB/sec, 84MB/sec, 103MB/sec, or
> 120MB/sec. This speed matching is done for the adjustment of native data
> speed of the tape drive as close as possible with the net data rate of the
> host. The host's net data speed is that which is achieved after the
> factoring out of data compressibility."
>

In other words, you should be seeing about 60MB/sec from NetBackup (assuming
2:1 compression) to meet the minimum LTO-4 drive speed of 30MB/sec.

   .../Ed

Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE
ewi...@ewilts.org
Linkedin 
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Large Full schedule, DSSU and Shoe Shinning

[Dean]

Shoe shining is less of a problem with modern tape drives, as they have this
"speed matching" which will slow the tape drive's throughput down to match,
as closely as possibe, the speed that data is coming in from the host...

"The IBM LTO-4 drive has the new technology that matches dynamic speed at
any of the 6 speeds of 30MB/sec, 48MB/sec, 66MB/sec, 84MB/sec, 103MB/sec, or
120MB/sec. This speed matching is done for the adjustment of native data
speed of the tape drive as close as possible with the net data rate of the
host. The host's net data speed is that which is achieved after the
factoring out of data compressibility."

The details vary by drive vendor.


On Thu, Jun 10, 2010 at 12:38 AM, Nate Sanders wrote:

> Our production Oracle jobs are set to use two 700GB dssu shares in a
> Storage Unit. We have our Full schedule set to bypass this and go
> straight to tape due to the job being larger than Disk Staging can
> handle for Oracle. Is there a fear of shoe shinning here since our
> recent migration to LTO4? DSSU sits on some 700GB SATAs in a netapp and
> I want to make sure this is acceptable, or find a better way to handle
> this.
>
> --
> Nate SandersDigital Motorworks
> System Administrator  (512) 692 - 1038
>
>
>
>
> This message and any attachments are intended only for the use of the
> addressee and may contain information that is privileged and confidential.
> If the reader of the message is not the intended recipient or an authorized
> representative of the intended recipient, you are hereby notified that any
> dissemination of this communication is strictly prohibited. If you have
> received this communication in error, please notify us immediately by e-mail
> and delete the message and any attachments from your system.
> ___
> Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

[Veritas-bu] VMWare vStorage API newbie Q (and never used VCB...)

[Jonathan Dyck]

Hello all,
I've been trying to get vStorage API backups going with Netbackup 7 in
my test environment now,  and am running into what I presume are
"standard" issues for people who've done this with VCB in the past.
Pretty sure I'm getting through those OK.

Getting beyond myself now, as this is a test environment  which has Lab
Manager, I'm running into VMs I can't backup. This is presumably because
they've been deployed via Lab Manager, which doesn't support the VMWare
snapshot method required to get the vStorage backups working.  The VMs
deployed straight from vCenter are no problem (basically the ones I can
right-click in vSphere client and create manual snapshots for ;).

Does this make sense?  Anyone have any experience with Lab Manager
deployed VM guests and VCB/vStorage backups?  Is there another method I
can try?

Thanks,
Jon




La version française suit le texte anglais.



This email may contain privileged and/or confidential information, and the Bank 
of
Canada does not waive any related rights. Any distribution, use, or copying of 
this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately 
from
your system and notify the sender promptly by email that you have done so. 



Le présent courriel peut contenir de l'information privilégiée ou 
confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute 
diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires désignés est interdite. Si vous 
recevez
ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans 
délai à
l'expéditeur un message électronique pour l'aviser que vous avez éliminé de 
votre
ordinateur toute copie du courriel reçu.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Large Full schedule, DSSU and Shoe Shinning

[Nate Sanders]

We're still on 5.1mp6 at the time. Dedupe on the Netapp is happening I
believe. Not much we can do on that front right now.


On 06/09/2010 09:46 AM, Lightner, Jeff wrote:
> Have you thought about using dedupe to reduce the size of the backup to
> disk?   We do that here with Data Domain then vault that off to tape.
>
> -Original Message-
> From: veritas-bu-boun...@mailman.eng.auburn.edu
> [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate
> Sanders
> Sent: Wednesday, June 09, 2010 10:38 AM
> To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
> Subject: [Veritas-bu] Large Full schedule, DSSU and Shoe Shinning
>
> Our production Oracle jobs are set to use two 700GB dssu shares in a
> Storage Unit. We have our Full schedule set to bypass this and go
> straight to tape due to the job being larger than Disk Staging can
> handle for Oracle. Is there a fear of shoe shinning here since our
> recent migration to LTO4? DSSU sits on some 700GB SATAs in a netapp and
> I want to make sure this is acceptable, or find a better way to handle
> this.
>
>   


-- 
Nate SandersDigital Motorworks
System Administrator  (512) 692 - 1038




This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Large Full schedule, DSSU and Shoe Shinning

[Lightner, Jeff]

Have you thought about using dedupe to reduce the size of the backup to
disk?   We do that here with Data Domain then vault that off to tape.

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate
Sanders
Sent: Wednesday, June 09, 2010 10:38 AM
To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
Subject: [Veritas-bu] Large Full schedule, DSSU and Shoe Shinning

Our production Oracle jobs are set to use two 700GB dssu shares in a
Storage Unit. We have our Full schedule set to bypass this and go
straight to tape due to the job being larger than Disk Staging can
handle for Oracle. Is there a fear of shoe shinning here since our
recent migration to LTO4? DSSU sits on some 700GB SATAs in a netapp and
I want to make sure this is acceptable, or find a better way to handle
this.

-- 
Nate SandersDigital Motorworks
System Administrator  (512) 692 - 1038




This message and any attachments are intended only for the use of the
addressee and may contain information that is privileged and
confidential. If the reader of the message is not the intended recipient
or an authorized representative of the intended recipient, you are
hereby notified that any dissemination of this communication is strictly
prohibited. If you have received this communication in error, please
notify us immediately by e-mail and delete the message and any
attachments from your system.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
 
Proud partner. Susan G. Komen for the Cure.
 
Please consider our environment before printing this e-mail or attachments.
--
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential 
information and is for the sole use of the intended recipient(s). If you are 
not the intended recipient, any disclosure, copying, distribution, or use of 
the contents of this information is prohibited and may be unlawful. If you have 
received this electronic transmission in error, please reply immediately to the 
sender that you have received the message in error, and delete it. Thank you.
--
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

[Veritas-bu] Large Full schedule, DSSU and Shoe Shinning

[Nate Sanders]

Our production Oracle jobs are set to use two 700GB dssu shares in a
Storage Unit. We have our Full schedule set to bypass this and go
straight to tape due to the job being larger than Disk Staging can
handle for Oracle. Is there a fear of shoe shinning here since our
recent migration to LTO4? DSSU sits on some 700GB SATAs in a netapp and
I want to make sure this is acceptable, or find a better way to handle this.

-- 
Nate SandersDigital Motorworks
System Administrator  (512) 692 - 1038




This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] FalconStor/NetApp w/OST

[Spencer O'Donnell]

What issues are you seeing with the Quantum in regards to restore?

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of mitch808
Sent: Monday, June 07, 2010 2:51 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] FalconStor/NetApp w/OST


There is no OST functionality with NetApp.  NetApp wants you to buy more
storage, and snap everything, to their storage.  There is no need for
backup to them.

As for Falconstor, I've yet to see any customer with it.  And I see a
lot of customers a week across many states.  

The customers that have Datadomain, love it.  Almost as fanatical as
NetApp users.  DataDomain's new DD Bost software is intriguing, but why?
were they suffering against other players, that they had to offload
processing?  

Quantum has one of the best implementations of OST, with their direct to
tape feature.  But I'm not sure if their restore issues have been solved
yet?

Exagrid as well has some positive remarks.  

I'm pretty sure, that you'll pay more by a lot for DataDomain, but will
it be worth it?

+--
|This was sent by mnab...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


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

Re: [Veritas-bu] NBU 7.0 media server upgrade problem

[Preston, Douglas]

Issue resolved.  Even with deleting all drives and robots on master sever and 
media servers, then recreating them I still had the issues.  Symantec support 
had test connectivity and it all seemed to be fine.  He then had me run 
tpautoconf -a on the failing media server and it started working.  All my 
backups performed well last night. Now I need to figure out how to get the same 
reports from bperror in 7.0 that I was getting in 6.x

bperror -U -backstat -hoursago 24 -by_statcode
this use to give me a list of servers that get backup broken down by result 
code.  Now all it gives me is the master server.  If I use -hoursago 72 I get a 
report for the backups performed pre 7.0 upgrade.

Same problem with this command bperror -U -backstat -hoursago 24

Doug Preston

-Original Message-
From: bob944 [mailto:bob...@attglobal.net] 
Sent: Tuesday, June 08, 2010 11:00 PM
To: veritas-bu@mailman.eng.auburn.edu
Cc: Preston, Douglas
Subject: RE: [Veritas-bu] NBU 7.0 media server upgrade problem

> I performed an upgrade from 6.5 to 7.0  on my master
> server all went well,  I performed an upgrade on 1
> media server all went well.  Before I could perform
> this on the next media server SCACIFS01.domain.com
> I started getting NetBackup TLD Control Daemon - "
> Invalid magic number from client SCACIFS01.domain.com
> " in the event log on the master server.  I performed
> the upgrade on this media server SCACIFS01.domain.com
> it still has the issue.

The only time I've seen "invalid magic number" messages is when two
mismatched components were trying to communicate.  Once was some
upgrade where I'd upgraded, say, ("say" == "I don't remember") the
client but not an agent.  

That's pretty vague, but if you're still fighting it, it might be
worth scripting a comparison of the size (or, better, the sum) of
each NetBackup binary between systems that works and the one that
doesn't.  Uninstall/reinstall might be faster.  

There's an FT mention, AVR, drives that appear configured ... I'd
first blow away the device configuration and rediscover.  And
whatever FT configuration there is--I've only done FT once and don't
remember it fondly.  


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

Re: [Veritas-bu] ALL_LOCAL_DRIVES question

[WEAVER, Simon (external)]

Wayne
This Technote may be worth a read. To get a better understanding :)
It refers to 5.1, but it gives you an idea on what is needed for
successful backups of Windows Machines.
 
NOTE: Ensure that your Windows boxes are using VSS to do the backups,
and not VSP! Check the settings using BPClient or from the GUI under
Master Server Properties / Client Attributes. Add a client in there and
check the TAB "Windows Open File Backup". Ensure VSP is not enabled and
Win2k3 or Win2k8 boxes are using VSS!
 
http://seer.entsupport.symantec.com/docs/272538.htm
 

 


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
 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 


**
** 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 em

Re: [Veritas-bu] ALL_LOCAL_DRIVES question

[WEAVER, Simon (external)]

An example of the System Config of a Win2k3 Server, that was used for
ALL LOCAL DRIVES (NOTE: Screenshot I am seinding may not be seen on the
list)

 

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu [
mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Barber,
Layne Mr CTR US DISA CDM242
Sent: Tuesday, June 08, 2010 8:45 PM
To: BeDour, Wayne; judy_hinchcli...@administaff.com;
steve.foga...@gmail.com
Cc: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] ALL_LOCAL_DRIVES question

No, it is broken into 2 parts, system state and shadow copy. The client
recognizes what version the OS is and backs it up accordingly.

Windows 2000 - is only system state
Windows 2003 - is shadow copy components (includes system state) Windows
2008 - Same as 2003

The contents of system state are:
Active Directory
Com+ Class Registration Database
Registry
System Files
SYSVOL


Shadow Copy components adds 2 items and INCLUDES the System State:

Shadow Copy Components
 |
 |- System State
 |  Active Directory
 |  Com+ Class Registration Database
 |  Registry
 |  System Files
 |  SYSVOL
 |
 |- System Service
Event logs
Windows Management
Instrumentation




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

Re: [Veritas-bu] ALL_LOCAL_DRIVES question

[WEAVER, Simon (external)]

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
 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 


**
** 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

Re: [Veritas-bu] ALL_LOCAL_DRIVES question

[WEAVER, Simon (external)]

ALD does indeed capture system state / shadow copy components, if the
clients are Windows 2000 and 2003 / 2008, ect. NT of course does not
need these directives.
I know, because I use it all the time. and has been since 5.1
 
System State is the Registry of Win2k and Shadow Copy is Win2k3+
 
I am now on 6.5, and again, can confirm that the System state is present
on my clients in a single policy for All Local Drives Directive.
 
HTH
Simon



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 8: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
 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 


**
** 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




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

Re: [Veritas-bu] ALL_LOCAL_DRIVES question

[WEAVER, Simon (external)]

Wayne
For simplicity, and knowing that you capture "everything" about a
Windows box, including the System State and Shadow Copy components (ie:
for Windows 2008/2008), it is ideal. It also means all drives on that
box are backed up.
 
You may have reasons for backing up Windows C: Drive and Shadow Copy
components, if you do not want to backup any other data, and you can do
that as well.
 
For some of our smaller servers, ALD means that all clients get put into
one policy and everything is backed up, unless we have excluded a file
or folder for that client.
Hope this helps.
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 6:40 PM
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  

**
** 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