Assign static slot in library to storage policy

Last post 10-24-2010, 2:19 PM by Liam. 3 replies.
Sort Posts: Previous Next
  • Assign static slot in library to storage policy
    Posted: 10-22-2010, 3:28 PM

    I think if this isn't possible i could get around this by adding a new scratch pool.

    However then I'd have to manually move the tape back into that pool

    I have a job that needs to be a seperate tape from any other backups. Its not very large and doesn't have a huge retention date to it.

    With previous software we would just assign that job to say slot 23 in the changer and it would always write to that tape. Then when it was full we'd replace it and it would continue writing to the new tape in that slot.

  • Re: Assign static slot in library to storage policy
    Posted: 10-24-2010, 9:31 AM
    • Aplynx is not online. Last active: 06-24-2019, 4:40 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,631

    create a new backup set with a subclient containing the content you are looking at and a new storage policy pointing to the library with that tape as the primary with 1 stream. you could call it "one time backup."

    once the retention is up just delete both the SP and backup set, but until then keep them in place. this is usually the best option.

  • Re: Assign static slot in library to storage policy
    Posted: 10-24-2010, 11:02 AM

    Sorry forgot to mention it runs regularly and not just a one off.

  • Re: Assign static slot in library to storage policy
    Posted: 10-24-2010, 2:19 PM
    • Aplynx is not online. Last active: 06-24-2019, 4:40 PM Liam
    • Top 10 Contributor
    • Joined on 05-04-2010
    • New Jersey
    • Master
    • Points 1,631

    regardless storage policies determine destination and retention so you wouldn't be able to assign specific media directly to an SP because you can only assign one scratch pool. a new scratch pool can hold the media you want to back up to and the new SP can be directed towards it.

    as for the data, you can't duplicate the same data in the same backupset, hence the need for the new backup set if the data is the same as in the default. if its additional data, say the D drive for instance, you could create a new subclient and point it to the D drive and let the default with the catch all (\) backup the rest to the original storage policy

The content of the forums, threads and posts reflects the thoughts and opinions of each author, and does not represent the thoughts, opinions, plans or strategies of Commvault Systems, Inc. ("Commvault") and Commvault undertakes no obligation to update, correct or modify any statements made in this forum. Any and all third party links, statements, comments, or feedback posted to, or otherwise provided by this forum, thread or post are not affiliated with, nor endorsed by, Commvault.
Commvault, Commvault and logo, the “CV” logo, Commvault Systems, Solving Forward, SIM, Singular Information Management, Simpana, Commvault Galaxy, Unified Data Management, QiNetix, Quick Recovery, QR, CommNet, GridStor, Vault Tracker, InnerVault, QuickSnap, QSnap, Recovery Director, CommServe, CommCell, SnapProtect, ROMS, and CommValue, are trademarks or registered trademarks of Commvault Systems, Inc. All other third party brands, products, service names, trademarks, or registered service marks are the property of and used to identify the products or services of their respective owners. All specifications are subject to change without notice.
Close
Copyright © 2019 Commvault | All Rights Reserved. | Legal | Privacy Policy