Rob,
Thanks. I think the plan may be to bring in the new master as the 6.0
system and EMM server. Then the existing 5.1 environment, when upgraded
to 6.0, will point to the existing EMM database. This would involve
networking plans, as one was to be on its own separate network. It also
brings up SPOF issues: if that EMM server goes down, then both
environments are hosed - to use the technical term. I hadn't planned on
clustering the new master (as Veritas says they don't support
active/active clusters), but this may be too critical to leave on its
own.
So at the very least we'll plow forward with the INVENTORY_FILTER stuff,
and consider the consolidated EMM database. In either case I'm looking
forward to consolidating the media manager databases and cutting down on
all the SAN media server/SSO chatter.
Thanks for the contributions.
Greg
-----Original Message-----
From: Rob Worman (home) [mailto:rob AT worman DOT org]
Sent: Tuesday, November 22, 2005 10:39 PM
To: Geyer, Gregory
Cc: veritas-bu AT mailman.eng.auburn DOT edu; Lee, Kenneth (SBS US)
Subject: Re: [Veritas-bu] One ACS robot, two NBU masters
Gregory-
Yes, I believe you could support both of your master servers (but they
would both have to be 6.0!) with a single EMM server.
This is roughly equivalent to Jim Peppas's response to your question,
suggesting that your two masters could share a single volume database
host. This is doable in some circumstances but NOT yours, because of
the fact that one of your masters is 6.0. (plus most of the Symantitas
support folks get the shakes when they hear about that kind of shared
volume database server configuration :-/)
I would second Kenneth's idea below; it is a very well-traveled path,
lots of people use the INVENTORY_FILTER stuff to share their ACS robots
among multiple master servers (and/or among multiple backup
applications...)
HTH
rob
On Nov 22, 2005, at 9:56 AM, Geyer, Gregory wrote:
> Here's another issue that recent 6.0 developments might make possible.
> In 6.0 there's the EMM database which controls resources like device
> info, active drive status, the volume database among many other
things.
> In the in-depth 6.0 diffs web-class yesterday it was stated that the
> EMM database can support multiple masters. So it would seem possible
> that with one EMM database we could have multiple masters also sharing
> tape drives, since they'd already be sharing robotics anyway. Anybody
> read this different?
>
> ________________________________
>
> From: Lee, Kenneth (SBS US) [mailto:kenneth.lee AT siemens DOT com]
> Sent: Monday, November 21, 2005 4:06 PM
> To: Geyer, Gregory; veritas-bu AT mailman.eng.auburn DOT edu
> Subject: RE: [Veritas-bu] One ACS robot, two NBU masters
>
>
>
> Yes, it works without a problem. I have 2 masters, one is 4.5 and the
> other is 5.1. We are using STK 9310 with the first master and added
> the second master when 5.1 came out. We designed a tape range of
> 100000 -
> 199999 to the 4.5 master and 500000 - 599999 to the 5.1 master. In
> order to stop one master from inventorying the tape range of the other
> master, we are using INVENTORY_FILTER. To use this, you need to put
> your tape range into a pool within your library. Since we started
> with
> 1 master and added the second, we did not define pools for the tapes
> in ACS, therefore all 100000 range tape took the default pool of 1.
> When the second master was added, after the tapes are loaded into the
> library (the 500000 range), I ran this command in ACS to put the
> 500000 range tapes into a pool called 50. set scratch 50
> 500000-500999. You will have to do this every time you add new tapes.
>
>
>
> In NetBackup, you need to add the following line to vm.conf:
>
>
>
> INVENTORY_FILTER = ACS 1 BY_ACS_POOL 50
>
>
>
> I have ACS 1 and the using pool 50 for the second master. You need to
> add this to both masters but change the pool number. Recycle your
> NetBackup and do an inventory check and you should be good to go.
>
>
>
> One other thing. A bug. If you are running NetBackup Administrator
> Console on your Windows desktop and you do an inventory, the output
> will show ALL of the tapes. The reason is because the NetBackup
> Administrator Console does not have the vm.conf on your desktop and
> therefore, does not know that you are filtering. You need to run
> either jnbSA from the master server or run the Java Console instead.
>
>
>
> Cheers,
>
> Ken
>
>
>
> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Geyer,
> Gregory
> Sent: Monday, November 21, 2005 2:02 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] One ACS robot, two NBU masters
>
>
>
> We have one large STK library and want to have two master NBU servers
> (one 5.x for now, the other 6.0) access it. The environments will NOT
> share drives or tapes, and we hear there should be no issue sharing
> the robotics (its shared now with 30+ SAN media servers), but wanted
> to hear if anyone has a similar environment without any issues.
>
> A concern would be having an inventory mix the tapes in the
> environment.
> I see the "Robotic Inventory Filtering" in the ACS appendix of the MM
> Sys Admin guide but no experience using it.
>
> So does anyone out there use two masters with one ACS robot?
>
> G.
>
|
