• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Limit the amount of tapes for copypool in library

mosiac

ADSM.ORG Member
Joined
Sep 25, 2014
Messages
152
Reaction score
0
Points
0
Is there a way for me to tell a copy pool to only keep say 10 or 15 tapes in the library for read write access at a given time?

Should I adjust my command that sets "offsite" status for tapes from 7 days to 5 or lower? Or is there a better way?
 

moon-buddy

ADSM.ORG Moderator
Joined
Aug 24, 2005
Messages
7,033
Reaction score
405
Points
0
Location
Somewhere in the US
Why do you have to keep offsite (copy pool) tapes in the library?

The default procedure is to eject offsite tapes right away after completing the copy from the online tape pool. This is your DR path.

Imagine what will happen if you keep the tapes and the Data Center that houses the tapes suffered from an unrecoverable disaster? You then lost all of your data.

If you MUST do this, then just don't eject those tapes for the duration that you want (again, defeating the purpose of offsite copies).
 

mosiac

ADSM.ORG Member
Joined
Sep 25, 2014
Messages
152
Reaction score
0
Points
0
The way it was previously setup was that it would check out any copypool tapes that were today-7 and the same for expiring data that was on old copy pool tapes, they would go into expiration but take 7 days to completely be cleared of all their data ready for scratch again.

I'm not sure why this was done but I would be more than happy to pull out all my copypool tapes on a daily basis but I don't know if I'll accomplish getting much written to them per day that way.
 

moon-buddy

ADSM.ORG Moderator
Joined
Aug 24, 2005
Messages
7,033
Reaction score
405
Points
0
Location
Somewhere in the US
The way it was previously setup was that it would check out any copypool tapes that were today-7 and the same for expiring data that was on old copy pool tapes, they would go into expiration but take 7 days to completely be cleared of all their data ready for scratch again.

I'm not sure why this was done but I would be more than happy to pull out all my copypool tapes on a daily basis but I don't know if I'll accomplish getting much written to them per day that way.
You don't worry if the copy tapes are just 1% or 90% utilized. What you should worry about is protecting your data.

Eject the tapes daily and you would get them back as scratch via reclamation.
 

marclant

ADSM.ORG Moderator
Joined
Jun 16, 2006
Messages
3,743
Reaction score
620
Points
0
Location
Canada
Website
www.ibm.com
The way it was previously setup was that it would check out any copypool tapes that were today-7 and the same for expiring data that was on old copy pool tapes, they would go into expiration but take 7 days to completely be cleared of all their data ready for scratch again.
Ok, so you have a reuse delay. The purpose of a reuse delay is that tapes are not overwritten for X days, which means that if you were to restore the TSM DB to a previous date (up to 7 days in your case), the data would still be available on the tape.

That's not the default, but it does provide extra protection. So you have to do a cost VS risk analysis. Is getting these tape immediately more important to you than the risk of loosing data if you were to be forced to restore the DB to a few days ago? If the answer is yes, then you can get rid of the reuse delay.
 

marclant

ADSM.ORG Moderator
Joined
Jun 16, 2006
Messages
3,743
Reaction score
620
Points
0
Location
Canada
Website
www.ibm.com
BTW, the customers that do use a reuse delay typically do so on their primary pool only, not their copy pool. But nothing says you can't do both. Again, cost VS risk.
 

mosiac

ADSM.ORG Member
Joined
Sep 25, 2014
Messages
152
Reaction score
0
Points
0
Honestly at this point I'd like to be able to feel like I've actually got all the data I'm supposed to be backing up. Right now I'm trying to find a way to clear out space in my library to add new scratch tapes so that I can write more data. I'm still working through another issue thread where for some reason some of my backups are trying to go straight to a tape stgpool versus disk first and I don't understand why at all.
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

DigitalOcean $100 Credit

Support ADSM.ORG and get DigitalOcean FREE credit. DigitalOcean currently offer a $100, 60-day Free Credit for new accounts. Sign-up here:

DigitalOcean Referral Badge

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 20 18.7%
  • Keep using TSM for Spectrum Protect.

    Votes: 65 60.7%
  • Let's be formal and just say Spectrum Protect

    Votes: 13 12.1%
  • Other (please comement)

    Votes: 9 8.4%

Forum statistics

Threads
31,902
Messages
136,004
Members
21,783
Latest member
london
Top