TSM marks tapes full at about 75% of real capacity

If you disable collocation, you use less tape, but spend more time restoring.
If you keep collocation, you will use more tape, but spend less time restoring.

Doesn't matter how you slice it, you can only pick 2 out of 3:
- low cost
- performance
- storage capacity
 
cool, do I need to a lot of tapes a scratch before deleting the collocations, or just delete , the process will not need a lot scratch tapes :what happens when I delete(don't have test only production, that's why I'm careful)
 
You don't delete anything, you just update the storage pool to disable collocation.

New data backed up won't be collocated.

When reclamation runs, data will no longer be collocated on the output volumes.

Just need 1 scratch for when you start reclamation.
 
My tapepool has reclamation threshold=60 and collocate =Group
But copypool does reclamation threshold=100 .
should I reduce the copypool=60 also
 
My tapepool has reclamation threshold=60 and collocate =Group
Unless every node belongs to a group, then that's equivalent to collocation=node. You can have multiple groups, but all nodes that are not in a group are collocated by themselves.
https://www-01.ibm.com/support/know...0/com.ibm.itsm.srv.doc/t_colloc_planning.html

But copypool does reclamation threshold=100 .
should I reduce the copypool=60 also
Should update all your stgpools to have a threshold of 100 because you said earlier that there is an admin script that does the reclamation for you here:
https://adsm.org/forum/index.php?th...-about-75-of-real-capacity.29868/#post-126801

I explained why here: https://adsm.org/forum/index.php?th...-about-75-of-real-capacity.29868/#post-126802
 
Marclant
please see this, I had about 6 scratch tapes in it and I received the error message by 6 this morning:
12/08/15 06:00:15 ANR1405W Scratch volume mount request denied - no scratch volume available. (SESSION: 132869, PROCESS: 1784)
12/08/15 06:00:15 ANR1221E BACKUP STGPOOL: Process 1784 terminated - insufficient space in target storage pool PACSCOPOOL. (SESSION: 132869, PROCESS: 1784)
12/08/15 06:00:15 ANR1893E Process 1784 for BACKUP STORAGE POOL completed with a completion state of FAILURE. (SESSION: 132869, PROCESS: 1784)
12/08/15 06:00:15 ANR1405W Scratch volume mount request denied - no scratch volume available. (SESSION: 132869, PROCESS: 1785)
12/08/15 06:00:15 ANR1221E BACKUP STGPOOL: Process 1785 terminated - insufficient space in target storage pool PCOPYPOOL. (SESSION: 132869, PROCESS: 1785)
12/08/15 06:00:15 ANR1893E Process 1785 for BACKUP STORAGE POOL completed with a completion state of FAILURE. (SESSION: 132869, PROCESS: 1785)
12/08/15 06:00:15 ANR1405W Scratch volume mount request denied - no scratch volume available. (SESSION: 132869, PROCESS: 1786)
12/08/15 06:00:15 ANR1221E BACKUP STGPOOL: Process 1786 terminated - insufficient space in target storage pool COPYPOOL. (SESSION: 132869, PROCESS: 1786)
12/08/15 06:00:15 ANR1893E Process 1786 for BACKUP STORAGE POOL completed with a completion state of FAILURE. (SESSION: 132869, PROCESS: 1786)
12/08/15 06:00:15 ANR1405W Scratch volume mount request denied - no scratch volume available. (SESSION: 132869, PROCESS: 1787)
12/08/15 06:00:15 ANR1221E BACKUP STGPOOL: Process 1787 terminated - insufficient space in target storage pool COPYPOOL. (SESSION: 132869, PROCESS: 1787)
12/08/15 06:00:15 ANR1893E Process 1787 for BACKUP STORAGE POOL completed with a completion state of FAILURE. (SESSION: 132869, PROCESS: 1787)
12/08/15 06:00:15 ANR1405W Scratch volume mount request denied - no scratch volume available. (SESSION: 132869, PROCESS: 1788)
12/08/15 06:00:15 ANR1221E BACKUP STGPOOL: Process 1788 terminated - insufficient space in target storage pool PCOPYPOOL. (SESSION: 132869, PROCESS: 1788)
12/08/15 06:00:15 ANR1893E Process 1788 for BACKUP STORAGE POOL completed with a completion state of FAILURE. (SESSION: 132869, PROCESS: 1788)
12/08/15 06:00:16 ANR1405W Scratch volume mount request denied - no scratch volume available. (SESSION: 132869, PROCESS: 1789)
12/08/15 06:00:16 ANR1221E BACKUP STGPOOL: Process 1789 terminated - insufficient space in target storage pool COPYPOOL. (SESSION: 132869, PROCESS: 1789)
12/08/15 06:00:16 ANR1893E Process 1789 for BACKUP STORAGE POOL completed with a completion state of FAILURE. (SESSION: 132869, PROCESS: 1789)
please, I do not understand it, though its still running backup but by now its should have finished
 
When using VTL, you depend on having a good FR (Factoring ratio) of physical capacity vs. Nominal, type data (example: jpg, MKV, mp3, rar, zip, etc), multiplexing and previous compress data. The dedup is not compatible with the above.

If you define a repository initially 10TB physical with FR approx 14: 1, you should expect Nominal 140TB space. if you define 1TB 140 tapes, example: the new backups can not be Deduplicate. FR lowers example 10: 1, this will cause the tapes no longer be filled up to 1TB, the maximum growth will be about 730GB. It may not be the case, but it happens frequently. and show full.

another important parameter is RELABELSCRatch=yes
check this doc: http://www.redbooks.ibm.com/abstracts/sg248025.html?Open
 
Back
Top