• 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.

Does reclamation check volume availability first?

Niceman

Newcomer
Joined
Mar 29, 2020
Messages
4
Reaction score
0
Points
0
I'm about a week and a half into learning TSM and trying my best to save a dodgy looking situation...

What happens if a file volume hasn't been marked unavailable (or destroyed) yet and a reclamation takes place, will it potentially delete the only usable copy of whatever's on that volume?

Or is TSM smart enough to check its availability during the reclaim process? I'd imagine TSM must be able to tolerate the loss of the disk storage right? I've come across the suggestion to set reclaim thresholds to 100 but some maintenance scripts have already run...

I'm uh... asking for a friend.
 

RecoveryOne

ADSM.ORG Senior Member
Joined
Mar 15, 2017
Messages
297
Reaction score
61
Points
0
Space reclamation on sequential volumes comes into play when files are expired or deleted from the volume (say the client says delete all backups for example). When the percentage of reclaimable space on the volume hits the threshold defined for the storage pool, the volume then becomes eligible to be reclaimed. I think the server does a check every hour or so to see which volumes are ready to be processed. (This can have an adverse affect with performance or tie up resources needed for other tasks, so I find it best to control when reclamation runs via tsm scripts). When the reclamation runs, the server copies files that remain on the volumes being reclaimed to other volumes in the same storage pool. Once the volume being reclaimed is empty, it should be returned to scratch volume based on the reusedelay setting. Reclimation can run for both primary and copy volumes. There are various recommendations to be found for different types of storage devices, and even a workaround for if you only have one tape drive, and need to free up tapes.

Very simplistically: TSM is only able to tolerate the loss of the disk storage if you have a copy storage pool in which to repair the primary storage pool. You would then use that copy to restore the primary or fix any damaged extents. There's other options such as replication to another server as well.

A really simple layout of primary and copy would look something like this for the legacy storage pool (file for example):
  • Client backups to to STGP_A at 10pm
  • At 1am STGP_A runs a backup stgpool command to TAPE_COPY_A
Client now has data protected on disk (primary) and tape (copy).

I always recommend that you should have a copy, and not on the same device as the primary storage!. See this link here for types of storage pools: https://www.ibm.com/support/knowledgecenter/en/SSEQVQ_8.1.9/srv.solutions/c_stg_pools.html

Generally you do not want to destroy volumes unless absolutely needed. If a volume is unavailable, that is generally a bad thing as well. Both cases unless there's a copy (from primary storage or copy storage) you could suffer data loss and/or not meet retention requirements.

Something not addressed above is database backup volumes. Those are not processed via reclamation. I find it best to address those manually via internal tsm scripts that delete the oldest database backup to free up space/tapes for the next one.

Hope the above helps.
 

Niceman

Newcomer
Joined
Mar 29, 2020
Messages
4
Reaction score
0
Points
0
Space reclamation on sequential volumes comes into play when files are expired or deleted from the volume (say the client says delete all backups for example). When the percentage of reclaimable space on the volume hits the threshold defined for the storage pool, the volume then becomes eligible to be reclaimed. I think the server does a check every hour or so to see which volumes are ready to be processed. (This can have an adverse affect with performance or tie up resources needed for other tasks, so I find it best to control when reclamation runs via tsm scripts). When the reclamation runs, the server copies files that remain on the volumes being reclaimed to other volumes in the same storage pool. Once the volume being reclaimed is empty, it should be returned to scratch volume based on the reusedelay setting. Reclimation can run for both primary and copy volumes. There are various recommendations to be found for different types of storage devices, and even a workaround for if you only have one tape drive, and need to free up tapes.

Very simplistically: TSM is only able to tolerate the loss of the disk storage if you have a copy storage pool in which to repair the primary storage pool. You would then use that copy to restore the primary or fix any damaged extents. There's other options such as replication to another server as well.

A really simple layout of primary and copy would look something like this for the legacy storage pool (file for example):
  • Client backups to to STGP_A at 10pm
  • At 1am STGP_A runs a backup stgpool command to TAPE_COPY_A
Client now has data protected on disk (primary) and tape (copy).

I always recommend that you should have a copy, and not on the same device as the primary storage!. See this link here for types of storage pools: https://www.ibm.com/support/knowledgecenter/en/SSEQVQ_8.1.9/srv.solutions/c_stg_pools.html

Generally you do not want to destroy volumes unless absolutely needed. If a volume is unavailable, that is generally a bad thing as well. Both cases unless there's a copy (from primary storage or copy storage) you could suffer data loss and/or not meet retention requirements.

Something not addressed above is database backup volumes. Those are not processed via reclamation. I find it best to address those manually via internal tsm scripts that delete the oldest database backup to free up space/tapes for the next one.

Hope the above helps.
It does indeed, thank you very much. There's a fair amount to wrap your head around at the start.
 

RecoveryOne

ADSM.ORG Senior Member
Joined
Mar 15, 2017
Messages
297
Reaction score
61
Points
0
Yes, there is a lot to pick up and run with at the start. Thankfully this forum is an amazing resource. It has greatly benefited me with my learning of the product. And I still get things wrong from time to time! But the fine folks here are kind enough to point out the errors and help offer up ideas.

That said, best resource is the documentation. Often times you'll find posts that say 'look at this' as I've done above. Just because IBM has wrote the book so to speak, and once you read the doc's and you still have a question then members here can help clarify.
 

Advertise at ADSM.ORG

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

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

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: 18 18.2%
  • Keep using TSM for Spectrum Protect.

    Votes: 61 61.6%
  • Let's be formal and just say Spectrum Protect

    Votes: 12 12.1%
  • Other (please comement)

    Votes: 8 8.1%

Forum statistics

Threads
31,755
Messages
135,384
Members
21,748
Latest member
fabiont
Top