On Tue, Apr 1, 2008 at 12:27 AM, WEAVER, Simon (external) < [EMAIL PROTECTED]> 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: [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] On Behalf Of Paul Keating > Sent: Monday, March 31, 2008 5:19 PM > To: [EMAIL PROTECTED]; [email protected] > 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:[EMAIL PROTECTED]
_______________________________________________ Veritas-bu maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
