I was working on our 7.1 upgrade project and was looking for a fision-io card 
or other SSD solution for my catalog. The flat file aspect of the catalog is an 
I/O hog, and I'd prefer an SSD solution to 8 or 10 spindles in my master. I 
tend to agree with those that say it's a bad idea to put your catalog on an 
array you backup etc...

As far as upgrading in place versus new master is concerned, we are doing the 
latter. We have many clients that cannot upgrade to 7.1 at this point due to 
compatibility concerns. We'll keep our 6.5.6 master around a year or so until 
all those client have been migrated. At that point I will likely re-import the 
few backup images that have not yet expired. 99% of our backups' retentions are 
1 year or less, so this shouldn't be much work.

-Jonathan

-----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 Bluejay 
Adametz
Sent: Thursday, September 08, 2011 1:35 PM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] What to do with our growing Catalog on the 
Masterserver??

>          1B: instead of keeping the catalog on a local disk - possibly we can 
> direct connect to one of our filers and dump the catalog there.

I always considered it a really bad idea to put my catalog, or even
catalog backup, on the same storage systems as the data that I'm
backing up (I'm not sure if that's the case you're describing). If
that array fails for any reason, you could lose both the data as well
as the catalog for that data, making a restore take considerably
longer.

My environment isn't nearly that size, but I keep my 23gb catalog on
local disks on my master and do catalog backups to an array at the
other end of the campus.

                                                         - Bluejay Adametz

Diplomacy is the art of letting others have your way.
NOTICE: This message, including any attachments, is only for the use of 
the intended recipient(s) and may contain confidential and privileged 
information, or information otherwise protected from disclosure by law.  
If the reader of this message is not the intended recipient, you are 
hereby notified that any use, disclosure, copying, dissemination or 
distribution of this message or any of its attachments is strictly 
prohibited.  If you received this message in error, please contact the 
sender immediately by reply email and destroy this message, including all 
attachments, and any copies thereof. 

_______________________________________________
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