hbw
ADSM.ORG Member
we upgrade our tsm clients from 5.1.6 to 5.2.2 on a Win 2003. the backup of oracle exportfiles goes directly on tape, not in a diskpool 'cause it's nearly 1 TB of data. With the 5.1.6 client the backup runs with three node sessions, two for drives and one for the "tsmdata". client definitions are maxmountpoints=4, ressourceutil=4.
after upgrading to 5.2.2 the client opens two sessions, one for the tsmdata, one backup-session. only one drive is allocated. so the backup takes o lot of time.
any idea why? no changes on client definitions or dsm.opt are made.
the tsm-server runs with 5.1.6. on w2k
:-o
after upgrading to 5.2.2 the client opens two sessions, one for the tsmdata, one backup-session. only one drive is allocated. so the backup takes o lot of time.
any idea why? no changes on client definitions or dsm.opt are made.
the tsm-server runs with 5.1.6. on w2k
:-o