Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

NBU 7 Volume Pools

Created: 03 Jun 2011 • Updated: 14 Jun 2011 | 6 comments
This issue has been solved. See solution.

Just curious as to what msot people use with regards to managing retention periods. I've read a couple of posts from people who recommend using the Netbackup Volume pool then just defining the retention period for each policy. Is this a best practice? Currently we have multiple pools that are based on retention periods, but I am running into challenges with our DSSU as it writes to a pool with a 21 day retention but I would like to add data that has different retention periods.

I would be interested to hear your opinions. Thanks.

Dan

NBU7 on W2K3

Comments 6 CommentsJump to latest comment

Nicolai's picture

If there is no business need, I always go for a single volume pool and uses different retention's in that volume pool. No need to over complicate things. And in general fewer volume pool means more efficiency use of tape drives.

my 0.02$

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

SOLUTION
J.H Is gone's picture

Actually the Pools do not have retention periods, it is the backup schedule that chooses a retention period for the backup image.

Some people like to micro manage and set up pools based on day of the week, incr or fulls or in your case on retention period.  It just over complicates everything.  Use one volume pool if you can and let the policy do the retention and let NB expire items when it wants.

You can create a new pool (that does not have a name that reference a retention period and change your policies to start using it, and as tapes expire they go back to scratch or you move them out of the pool.  Once all are expired remove the old pool and stop the confusion.

I don't have to know how to spell....I work on Unix.
NetBackup 7.0.1 - AIX & Windows

rizwan84tx's picture

Single Volume Pool with multiple retention is good, as long as images with multiple retention never write on same volume. By Default, NBU will not allow images with different retention to be written on same media.

Best Regards,

Rizwan

Riaan.Badenhorst's picture

Hi Dan,

Please mark a solution or continue the line of questioning if not satisfied.

Regards,

Riaan Badenhorst

You need an OpenVision to see the truth about Backups. Restores are a plus. But that's just Semantics ;)

ITs easy :)

pkjohnston's picture

Pools are better used to define volume ownership and related charge-back (divisions, departments, workgroups, projects, ...) Perhaps easier for some to track and manage than billing against GBs backed up. Another approach for smaller shops would be to use pools to define what kind of backup data do you expect to find on the associated volumes (SQL_pool, Exchange_pool, FileShare_pool, UserPC_pool ...).

That was good advice given earlier in this thread to try to keep the number of pools down, unless you have a huge scratch pool, otherwise you're bound to run into more error code 96s during your backups.

Paul Johnston, C.E.T.

Virtual Academy Drill Sergeant (Canadian Regiment)

Symantec Education

Dan Giberson's picture

Thanks for all the input here guys. I really appreciate it.

NBU 7.01 on Windows 2003 with LTO2 Library