TSM FOR VE ( for vmware) option to exclude drives when performing Virtual Machine backups

apologies: somehow I entered my comment on the wrong RFE.

With SP you reach a limit fairly quickly on scaling up.
I name instances with digits as when either the internal database grows to a point where its backup begins to exceed an hour I lay down another instance and split the load by perhaps moving moving some backups but all new requests go to the new instance. The new caveat to this is the directory container storage pool. As that grows it slows down. More than 1 PB may be prohibitive, especially if you mix different types of data into the same DCP. I inherited a ~600 TB DCP (and growing) that was the target of nearly all backups. This means that all blocks become comparisons during ingest. There is no point in comparing dissimilar data! Thus I am splitting this single instance (with a 6.5 TB internal database -- allocated and 66% used -- is way to big, and can take ~15 hours to backup, yet as little as 1.5 hours when lightly loaded) into 4, one for Operations Center & Library Manager (no client support), one for database backups with separate DCPs for full backups by platform (Cache, Oracle, and SQL Server) and separate DCPs for transaction log backups (and incremental/differential database backups) by platform, one for filesystem backups, and another for block/VM backups. The 1st internal DB will only be 10GB. The database internal DB will be 0.5 TB (probably overkill). The filesystem and VM internal DBs will be 1TB to start (all using 16 separate LUNs). Each DCP will use 100 separate LUNs and be sized at significantly less than 1 PB to start.
A single large 880-class server can support many such SP instances so long as you use either multiple 10G interfaces ether-channelled into a larger pipe or 40G interfaces. Also there needs to be a large number of CPUs and amount of RAM, and high-speed fiber interfaces. Multiple high-speed Ethernet to clients (and WAN for replication) and Fiber interfaces to SAN disk storage is the limiting factor. I don't break-up SP servers into LPARs, just one full system partition so all the resources are shared. As spinning disk I/O becomes 70% for longer periods of time it is time to buy another physical server.

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

This solution was delivered in v6.4.

Thank you for submitting the request. This is a recognized requirement and a solution will be delivered in 4Q 2012.

Thank you for submitting the request. This is a recognized requirement and a solution will be delivered in 4Q 2012.

Thank you for submitting the request. This is a recognized requirement and a solution will be delivered in 4Q 2012.