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.
update dev {devclassname} directory="/dir1,/dir2,/dir4"
You must replace the entire list of directories with the new one.
So if you have /dir1, /dir2, /dir3, /dir4 currently and want to remove /dir3, you would do:
Code:update dev {devclassname} directory="/dir1,/dir2,/dir4"
This will not delete any data from /dir3. If there is data still there, you can still read it and access it, new scratches will be created on the directories that remain defined to the devclass.
This means you can do the change now so that no new data is written to /dir3. Then can use MOVE VOLUME to move the data from the /dir3 volumes to existing or scratch volumes in that pool.
Correct, no dedup across pools.is my understanding that dedup only works at the individual storage pool level
One large container pool for better deduplication. If some of the data will be kept a really long time, you can look at 8.1.3 or higher for tiering to cloud: https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.3/srv.common/r_techchg_tier_813.htmlI ask because I am trying to find the most efficient way of backing up the same data via two different storage sources to one TSM Server. One source will remain dormant (until the retentions expire when eventually it will be blown away) and the other remain active from the initial re-ingestion.?
Correct, no dedup across pools.
One large container pool for better deduplication. If some of the data will be kept a really long time, you can look at 8.1.3 or higher for tiering to cloud: https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.3/srv.common/r_techchg_tier_813.html