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
Currently the TSM Client Deployment package is coded to check for 2GB of free space on the c:\ drive of a Windows client node. If it is not available the TSM client code will fail to install. The current auto-deployment package for 64bit Windows is 295MB, and 256MB for 32bit Windows. Please change the automated Client deployment package to check for the actual amount of free space that is need to do the install.
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 enhancement request, here are some numbers that we use internally when downloading and installing the package (manually)
32 bit base package: 175MB
Extraction space: 360MB
Temporary space: 360MB
Footprint: 360MB
TOTAL: 1255MB
64 bit base package: 220MB
Extraction space: 520MB
Temporary space: 520MB
Footprint: 520MB
TOTAL: 1780MB
obviously, these are just "rules" of thumb and the necessary space will be different and dependent on what type of package you install, what language packages, which components etc. as far as the client footprint (after installation), it will range between ~300MB - ~500MB.
as noted above, there are other things to consider such as logs space, disk cache (for the local dedupe cache) etc. etc. so the automatic deployment assumes the "worse case" scenario, this can definitely be circumvented by installing the client on that machine manually and not by the "auto deployment" feature.
as noted above, TSM
Paul,
The Automated TSM Client Deployement is, right now, only for upgrading the TSM client code on a Windows platform, it is not for new installs so pretty much the only thing it should be doing is stopping the TSM services, overlaying the old client code, and re-starting the services. It also has an option that allows you to re-boot the Windows machine, or not.
We can individually install the TSM client code upgrades on pretty much any Windows machine no matter how much free space is on the C:\ drive, I would just like the auto-deploy package to do the same.
In addition to the client code, TSM may need space for disk cache, logs, etc. While I see your point, I would be concerned that just installing the TSM software may not be sufficient to get TSM running in some environments. Perhaps this was the reason that IBM used 2GB instead of something less? It would be nice to have some tailorability to specify how much extra space (if any) should be available before continuing with the install.