Skip to main content

This seemed simple enough when I started… ;)

 

I’ve got a number of policies reflecting differing retention times (1 month retention for 1 month, 1 month each for 12 months, quarterly and a yearly). 

Dealing with disks, this is great, for the most part as the Dedupe never seems to grow tired of how much I torture it.  However, I’m finding that when I got to tape, we’re seeing jobs go to varying tape media.  One thing I’d like to hammer home, however, is that yearly backups are separate from anything else.  I don’t need something with a retain until being 2030 and something else on the same tape being 2023.  We have three tapes drives in our robot, I’d like to just spin one off and let it deal with the yearlies.  We have over 700 servers, so it’ll have more than enough use from the beginning of the year until around tax time.

 

First - is there a better way to handle this?  I know there are methods with policy names, combining streams, and multiplexing, which, frankly, all seems like playing one-handed pinball.  I’ve tried getting help from support, but they’re a “fix-only” operation and of no help.  My thought, at least for the yearly, was:

Second - I’ve created another library.  I’d simply like to remove one of the devices from the first library and put it into the second library.  I’ve convinced the robot that it has a another library and it has some tape slots dedicated to that.  But I don’t see any way to remove the tape from library A and assign it to B.

 

Any thoughts? ;)

 

Best wishes!

Hello, The best way for you to go about doing this will be create seprate dedicated disk pools and assign a specific set of tapes to that disk pool. 

By Default commvault creates a Scratch pool with all the tapes in.Once that is created create an aux copy that is scheduled to run once a year and make it a selective copy and make sure that you choose the newly created tape pool within the tape library as the data path. 

This way you will have separation amongst tapes that are use for day to day aux copy function and yearly aux copies. 


After digging through a training guide from 2017.. what about simply having multiple Global Secondary copies?  This is what that’s used for, yes?  A Yearly tape copy on <any> policy could be sent to a secondary copy named “Yearlies” (for example).  Any yearly backup would go to media specifically selected for a yearly backup/last full backup of last year/etc., yes?  There’s no need, then to create an entire separate library?


Solved.. if you wish to remove drives/add them/etc:  Commcell→Storage Tab→ Expert configuration.  But, I’m most likely going to simply have more secondary copies instead.


Reply