IBM System Storage Ideas Portal
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).
Shape the future of IBM!
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:
Search existing ideas
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 your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
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
Please review the following information and let us know if any questions.
====
The size of the database backup was removed from the volume history information in 6.3 as this is no longer needed. It was originally added in 6.1 in order to track attributes of the database backup that were needed at the time the database needed to be restored. This information, along with a few other things that were also recorded, caused the ability to restore a server to be tightly coupled to having the volume history file available.
With TSM 6.3, the dependency on the volume history file was eliminated by a set of changes and enhancements to the database backup processing to no longer rely on recording this information to the volume history file.
For monitoring the database space, it's growth over time, and such, the recommended approach is the Q DB command which reports the used and free space for the database. If this data were being viewed or collected over time, then the database growth patterns, consumption rate, and such would be available for use and could be considered for decisions like when to purchase/provision more space.
Also consider that with 6.3 and the Tivoli Common Reporting, there is a report showing "Server Database Growth Trends" which is likely another way to view the data in question over time.
Please review the following information and let us know if any questions.
====
The size of the database backup was removed from the volume history information in 6.3 as this is no longer needed. It was originally added in 6.1 in order to track attributes of the database backup that were needed at the time the database needed to be restored. This information, along with a few other things that were also recorded, caused the ability to restore a server to be tightly coupled to having the volume history file available.
With TSM 6.3, the dependency on the volume history file was eliminated by a set of changes and enhancements to the database backup processing to no longer rely on recording this information to the volume history file.
For monitoring the database space, it's growth over time, and such, the recommended approach is the Q DB command which reports the used and free space for the database. If this data were being viewed or collected over time, then the database growth patterns, consumption rate, and such would be available for use and could be considered for decisions like when to purchase/provision more space.
Also consider that with 6.3 and the Tivoli Common Reporting, there is a report showing "Server Database Growth Trends" which is likely another way to view the data in question over time.
Please review the following information and let us know if any questions.
====
The size of the database backup was removed from the volume history information in 6.3 as this is no longer needed. It was originally added in 6.1 in order to track attributes of the database backup that were needed at the time the database needed to be restored. This information, along with a few other things that were also recorded, caused the ability to restore a server to be tightly coupled to having the volume history file available.
With TSM 6.3, the dependency on the volume history file was eliminated by a set of changes and enhancements to the database backup processing to no longer rely on recording this information to the volume history file.
For monitoring the database space, it's growth over time, and such, the recommended approach is the Q DB command which reports the used and free space for the database. If this data were being viewed or collected over time, then the database growth patterns, consumption rate, and such would be available for use and could be considered for decisions like when to purchase/provision more space.
Also consider that with 6.3 and the Tivoli Common Reporting, there is a report showing "Server Database Growth Trends" which is likely another way to view the data in question over time.