02-06-2011 01:19 PM
Solved! Go to Solution.
02-09-2011 05:32 AM
Each site get it's own pool with prefix of the bar code series ( Barcode JP = volume pool jp_scheduled). We haven't modified any volume group settings, we relying on the barcodes and storage unit names. Storage unit's also use the barcode naming style.
02-07-2011 12:33 AM
Does the media from site to site use diffrent barcodes ?.
I think barcode rules should do the job - See page 329 in the Admin guide.
02-07-2011 04:28 AM
Hey Nicolai,
Thanks for replying.
This can only be set to move media into a specific volume pool instead of a volume group.
This is ok, but I thought the idea of volume pools are to separate media by usage and volume groups are used to indicate media location. This is why I preferred to use a volume group. What’s your take on this?
02-07-2011 04:16 PM
Any other suggestions on this one?
02-08-2011 01:23 AM
Volume pool is something Netbackup takes control of when you perform a inventory of the robot.
If you wan't to know if a media outside a robot, look for the volume group collum in a volume pool.If the collum say "---" it mean the media is outside a robot.
We got a simelar setup with branch offices and this is how we do it.
Hope I got it right :)
02-09-2011 12:02 AM
So instead of trying to create custom volume groups for media to go in when it's ejected\injected I should just rely on the default volume groups.
I guess I'd really need the vault option if I wanted to do this.
Just one more thing, are you using a separate volume pool for each of your sites?
Cheers
02-09-2011 12:31 AM
Each site has it's own barcode series and volume group. The barcode indicate location - JP for Japan, Fr for France, PH for Philippines and so on.
And storage units are "on demand only" - else backup is Japan end up in France
02-09-2011 02:24 AM
Ok, I see.
The barcodes that were ordered don’t really indicate the location (they weren’t ordered by me) :(
Did you customize the volume groups or are you using the defaults and completely relying on the barcodes labels to easily identify the location?
What I would have liked is that each robot located at each site has a custom named volume group i.e. site1, site2, and site3
Cheers
02-09-2011 05:32 AM
Each site get it's own pool with prefix of the bar code series ( Barcode JP = volume pool jp_scheduled). We haven't modified any volume group settings, we relying on the barcodes and storage unit names. Storage unit's also use the barcode naming style.
02-09-2011 08:39 AM
I get custom barcodes and I can tell by the first letter what they are for ( can you also get them different colors for quick id when you look at the physical tapes)
I have some that are in the same robot, so I have barcode rules to put them in their own volume pool.
I don't look at volume groups at all.
02-09-2011 08:40 AM
Ok, so you’re using a separate volume pool for each site.
Are there any real drawbacks using this method?
I was thinking of setting it up this way, it’s just I read that volume groups should be used to distinguish location of media and volume pools used to separate application usage, i.e. exchange backups, oracle backups etc. I guess I’m looking into it a little too much.
Again, thank you for all your help with this
Cheers
02-09-2011 08:53 AM
Thanks J.Hinchcliffe
Each site here has a three letter site code associated with it, so I've decided to use this as the start of bar codes. We haven’t started using the already ordered bar codes as yet, which is lucky.
From what I understand is it best to try and keep volume pools to minimum for each robot so as to reduce the number of partially full media?
Cheers
02-10-2011 01:12 AM
Not really.
I general try reducing the number of volume pool for each site. If you have 3 client, each in a different volume pool, but only one tape drive, the backup would serialized. If all 3 client was in same volume pool the backup would be parallel (assumption: Retention is the same).
02-10-2011 07:20 AM
the fewer pools you have the fewer tapes you may need, and transport offsite, and pay for storage offsite.