Networker

Re: [Networker] Multiple Media Pools Bad?

2009-09-02 08:37:04
Subject: Re: [Networker] Multiple Media Pools Bad?
From: MIchael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Wed, 2 Sep 2009 08:27:09 -0400
EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on 
08/31/2009 10:14:03 AM:

> Hello,
> I'm not trying to "hijack" this thread so I'm posting it under another
> subject.
> 
> Why do you think it's bad practice to have multiple pools?  Other than
> the pain of unchecking the drives if you have to delete and recreate
> devices (and it is a pain.. :), it seems to have worked well in our
> setup.  We have multiple sites, and I don't want my backup traffic going
> across the wan, so having multiple pools seems to have worked well. 
> 
> I have separate pools for each of the following at each site:
> - windows os
> - linux os
> - sql
> - exchange
> - ndmp
> - vcb

I have pools for:

PRODUCTION (i.e., non-clone)
CLONE
BOOTSTRAP

and that's it, really. These are all for the servers at one site - the 
other sites that have their own tape drives have their own unique pool 
names, based on their site name.

> I would think that having multiple pools would speed up cloning as it
> wouldn't have to wait for source tapes, currently I clone by group and
> we have to make multiple clone copies of all of our data.  Having
> multiple pools has worked pretty well for us. 

I clone by group, but each group has only the one clone client in it. So I 
have 6 groups marked as "clone", and a total of 6 clients in them.

> The usual reason is to speed up a DR situation, so that when you do an
> nsrck -L7 for all clients it does not need to read dozens of tapes.

That's the reason I have a "BOOTSTRAP" pool.

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

<Prev in Thread] Current Thread [Next in Thread>