Veritas-bu

Re: [Veritas-bu] Best Practice: Location of the NetBackup Catalog

2008-05-12 13:18:29
Subject: Re: [Veritas-bu] Best Practice: Location of the NetBackup Catalog
From: "Nardello, John" <john.nardello AT wamu DOT net>
To: "WEAVER, Simon (external)" <simon.weaver AT astrium.eads DOT net>
Date: Mon, 12 May 2008 09:52:54 -0700
Depends on how much money you want to throw at your setup I guess. =)
 
Most of our large catalogs are quite happy living on the SAN. Of course, our SAN is DMX3s, dual-pathed to separate fabrics and switches, and runs to two different physical HBAs on the servers themselves.
 
Even if you're looking at only a single path though, having your catalog on a SAN volume means you're probably getting automatic hardware RAID of some level. That's generally a little harder to pull off using local disks and still have any reasonable amount of usable space leftover.
 
Plus, leaving it on the SAN gives you the option to do frame-based replication, snapshots, BCVs, etc etc etc.
 
But only if you can afford it. =)
 
- John Nardello
 


From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of WEAVER, Simon (external)
Sent: Monday, May 12, 2008 8:13 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Best Practice: Location of the NetBackup Catalog

All,
Just a general query on the best practice for the location of the NetBackup catalog (Its DB, images, ect).

When you install NBU on a Server, the location can be accepted as the "default" or you can customise the installation and choose an alternative location (ie: Spare drive on local server, SAN attached drive, ect).

Presently, I have NetBackup and the catalog installed locally, on RAID5 set, hot swappable.

My question is this: Is there a best practice for the location of the Catalog? For example, SAN attached disk? I sort of feel uncomfortable with this for several reasons:

1) If you lose SAN connectivity (due to a major disaster or failure) the catalog has gone
2) NetBackup and the OS relies on that disk being available constantly

Being stored locally, means the Server and its application (including the catalog) goes with it, and does not rely on an extra layer of hardware for the catalog to be available.

I think my concerns come from a previous environment where the catalog was stored on a SAN,  and was totally destroyed and unrecoverable, which meant a complete import of hundreds of tapes.

If anyone has any feedback on this, would like to hear the pro's and con's to storage off the physical server itself. I have always had the catalog locally stored.

Thanks, Simon

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
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu