ILCattivo
ADSM.ORG Senior Member
Morning chaps,
I have 1 File device class with 2 deduplication storage pools attached to a TSM 7.1.5 Server.
Directory: S:\STG,P:\STG,X:\STG
Currently these 2 storage pools have a max scratch setting of '0' whereby volumes of 5GB in size have been created manually as and when additional capacity has been required. Personally I don't like storage pools setup in this way as you can be prone to running out of storage pool space, and scratch volumes can also run out which can affect reclamation if any unforeseen large ingestion were to come about.
NB:\\ 1 storage pool has had volumes manually created for it using P:\ & X:\ while the other is only using S:\
i.e 'DEFine Volume DEDUP1 S:\STG\VOL1001 ACCess=READW Formatsize=5120'
Today, a lot more disk capacity is being added to the file class directories (see above) for these two storage pools.
I now want to change the max scratch setting to my preferred setting of '9999' & the max cap (MB) setting to '5120' for these 2 storage pools so that TSM now has the capability of using the entire underlying disk capacity available to it and start creating and deleting scratch volumes on its own as and when it needs them for both backups and reclamation.
Anything I should be aware of before doing this..? Firstly, I am assuming that making this change will result in both storage pools placing their scratch volumes in any one of the 3 available file class directories as appose to previously being restricted to just those directories where they were manually created?
edit.. btw, these storage pools backup to Tape daily via the 'backup stgpool' cmd.
Anything else?
Thanks
I have 1 File device class with 2 deduplication storage pools attached to a TSM 7.1.5 Server.
Directory: S:\STG,P:\STG,X:\STG
Currently these 2 storage pools have a max scratch setting of '0' whereby volumes of 5GB in size have been created manually as and when additional capacity has been required. Personally I don't like storage pools setup in this way as you can be prone to running out of storage pool space, and scratch volumes can also run out which can affect reclamation if any unforeseen large ingestion were to come about.
NB:\\ 1 storage pool has had volumes manually created for it using P:\ & X:\ while the other is only using S:\
i.e 'DEFine Volume DEDUP1 S:\STG\VOL1001 ACCess=READW Formatsize=5120'
Today, a lot more disk capacity is being added to the file class directories (see above) for these two storage pools.
I now want to change the max scratch setting to my preferred setting of '9999' & the max cap (MB) setting to '5120' for these 2 storage pools so that TSM now has the capability of using the entire underlying disk capacity available to it and start creating and deleting scratch volumes on its own as and when it needs them for both backups and reclamation.
Anything I should be aware of before doing this..? Firstly, I am assuming that making this change will result in both storage pools placing their scratch volumes in any one of the 3 available file class directories as appose to previously being restricted to just those directories where they were manually created?
edit.. btw, these storage pools backup to Tape daily via the 'backup stgpool' cmd.
Anything else?
Thanks