Veritas-bu

Re: [Veritas-bu] NetBackup 6.5 index size

2008-04-01 16:22:29
Subject: Re: [Veritas-bu] NetBackup 6.5 index size
From: "Nardello, John" <john.nardello AT wamu DOT net>
To: <veritas-bu AT mailman.eng.auburn DOT edu>
Date: Tue, 1 Apr 2008 12:54:51 -0700
Count yourself lucky you haven't used LVM on AIX. I keep dreaming of ways to get the SAs to install Storage Foundation onto our AIX boxes. =)

- 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 Jeff Lightner
Sent: Tuesday, April 01, 2008 7:40 AM
To: WEAVER, Simon (external); Ed Wilts
Cc: veritas-bu AT mailman.eng.auburn DOT edu; Paul Keating
Subject: Re: [Veritas-bu] NetBackup 6.5 index size

I second Ed’s recommendation of Veritas Volume Manager (VxVM).   Not just for NetBackup but for most filesystems (including those for >terabyte databases).   The options one has for controlling things such as buffering, block sizes etc… are important for databases.  Moreover since it allows you to grow/shrink filesystems on the fly it is a great tool for Production environments where downtime Is hard to get.   Finally since it allows one to do software RAID in environments where hardware RAID isn’t available it has that added benefit.

 

Most Sun Solaris shops of any size use VxVM.   Many HP HP-UX shops use VxVM even though HP has its own Logical Volume Manager (LVM) but many still use LVM.  On Linux most Enterprise folks use LVM which is very much like the one on HP-UX.  AIX has one called LVM that I haven’t used.

 

Using Windows for very large enterprise class environments simply isn’t an option for most folks due to scalability issues.

 


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: Tuesday, April 01, 2008 9:35 AM
To: Ed Wilts
Cc: veritas-bu AT mailman.eng.auburn DOT edu; Paul Keating
Subject: Re: [Veritas-bu] NetBackup 6.5 index size

 

Ed

I use Robocopy alot, but I feel that the product may have been ill-advised by someone who thought we needed the product, when clearly we have proven this is not the case.

 

Robocopy and Diskpart :-) works like a charm!

 


From: Ed Wilts [mailto:ewilts AT ewilts DOT org]
Sent: Tuesday, April 01, 2008 1:22 PM
To: WEAVER, Simon (external)
Cc: Paul Keating; Dariusz.Klar AT sun DOT com; veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] NetBackup 6.5 index size

On Tue, Apr 1, 2008 at 12:27 AM, WEAVER, Simon (external) <simon.weaver AT astrium.eads DOT net> wrote:


Personally, I am not a fan of Veritas Volume Manager, and I certainly cannot recommend it.


That's because you're a Windows guy and the product certainly doesn't function on Windows like it does on Unix.  If you're a Unix guy, you'll see the limitations of Windows and its lack of a volume manager very quickly.

My catalog is in a volume manager and yes, we've grown it.   We've bounced a lot of our storage around between SAN frames as well as expanded volumes.  On the other hand, my Windows admins do nothing but bitch and moan when they have to do the same thing.  Linux, HP-UX, Solaris, VMS - all move data nicely around.  Windows, well, just say no.

Robocopy is not an alternative to a volume manager :-)

   .../Ed

 

-----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 Paul Keating
Sent: Monday, March 31, 2008 5:19 PM
To: Dariusz.Klar AT Sun DOT COM; veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] NetBackup 6.5 index size

Build your catalog filesytem using a Logical Volume Manager, such as Veritas Volume Manager (Storage Foundations) on a SAN attached LUN. As your catalog grows you can grow both the LUN and the filesystem hot, without an outage.

Or, if you have availability of a recent Enterprise class array such as the HDS USP-V, you can build it on a DP (Dynamic provisioned) LUN (aka thin provisioning)

The array presents your server with a large fixed size LUN, even several terabytes, but only occupies as much disk space as needed, initially, then auto allocates disk as needed.

Personally, I'd just go the volume manager route.

Paul



--
Ed Wilts, Mounds View, MN, USA
mailto:ewilts AT ewilts DOT org

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