Cannot comment on the drive "view" or schedule-mode problems -- sounds like
a TSM-cluster service definition discrepancy (else, a bug; need to check the
cluster services setups and client code level, then contact Support Line or
install latest client code -- there's been a bunch of client-code activity
in cluster support this year, both for Win2K and AIX).

Regarding your speed/performance of incremental {If the EMC disks appear as
"local" drives, you should consider the NTFS journaling-incremental
feature.} -- alternatively, you may want to consider -incrbydate for your
weekday backups;  the speed of progressive-incremental is largely due to the
client traversing the entire file system structure to identify which files
to process -- file systems with large numbers of files (anything over
half-million) seem to be cause for performance concerns.  I had a client
that decided to address this issue by limiting their file systems to 100 GB;
starting a new drive-letter when reaching that size greatly helped mitigate
the daily incrementals (AND full file system restores, their main concern).
We recently did 1.6 million file/object restore for a 320 GB file system,
achieved nearly 10 GB/Hr with parallel restore sessions, DIRMC (very
important), DIRSonly and FILESonly options, to minimize NTFS re-org
thrashing, and CLASSIC (vs. no-query) restore path, to ensure minimal tape
mounts.

Result was backups of 12-20 GB, restores 6-15 GB/Hr, depending on
collocation standards.  High priority (ie, mission critical or
high-visibility) servers get collocated.

Hope this helps.  See, also, a dozen other posts this past couple months,
search for "cluster" in the subject field.

Don France
Technical Architect - Tivoli Certified Consultant
Professional Association of Contract Employees (P.A.C.E.)
San Jose, CA
(408) 257-3037
don_france AT att DOT net