This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
Customer Lyle Fast wants to request a change to the way TSM works regarding deduplicated data in an offsite copy storage pool.
TSM recommends that offsite storage pools have a fully hydrated copy local and any offsite copies are non-deduplicated. Lyle feels this defeats the purpose of using deduplication (saving storage space for backups).
Why is dedup copypool not a good idea?
Not recommended as a DR restore will fail because the copy stgpool would only have the deduplicated copies of the data and no non-deduplicated copies to rehydrate the data for restore (no way to access the extents)
I thought the purpose of TSM Client side deduplication or server deduplication in an all disk environment was to save storage space for backups. If TSM support recommends a local non-deduplicated copy storage pool and copy non-deduplicated storage pool offsite, where is the savings?
In Effective Planning and Use of IBM Tivoli Storage Manager V6 Deduplication it mentions the DEDUPREQUIRESBACKUP option, recommends yes that data is not processed by identify duplicates until it is backup to a non-deduplicated storage pool.
I think there needs to be another option to DEDUPFORCEDCOPY that would copy all the blocks in the primary storage pool offsite deduplicate=YES backup copy storage pool.
Idea priority | High |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Storage
Product - Tivoli Storage Manager (TSM) Family
For recording keeping, the previous attributes were:
Brand - Tivoli
Product family - Storage
Product - Tivoli Storage Manager (TSM) Family
Thank you for submitting the request. This is a recognized requirement and a solution appears to be desirable. This request is not in a committed release plan for next year,
but the theme is aligned with our multi-year strategy, and will be a candidate for our future release. IBM’s plans may change and no commitment is made that a solution will be provided.