Dwight, Why are you using several backup mgmtclasses? Different libraries? I can't explain this behaviour. But if you want approximately the same amount sent to each mgmtclass, you can try the following:
MAX_BACK_SESSIONS 15 ..... SERVER TSM_1 SESSIONS 4 BRBACKUPMGTCLASS A35_PR5_A SERVER TSM_2 SESSIONS 4 BRBACKUPMGTCLASS A35_PR5_B SERVER TSM_3 SESSIONS 4 BRBACKUPMGTCLASS A35_PR5_C SERVER TSM_4 SESSIONS 3 BRBACKUPMGTCLASS A35_PR5_C TSM_1 - TSM_4 are in this case aliases for the same TSM-server. In this scenario it can still happen that one mgmt-class gets more files (=data?) then the others if these classes are based on different tape-technology. Jeroen -----Original Message----- From: Dwight Cook [mailto:[EMAIL PROTECTED] Sent: woensdag 19 november 2003 13:42 To: [EMAIL PROTECTED] Subject: TDP/R3 & BRBACKUPMGTCLASS (odd behavior) tsm client is a sun solaris 8 running tsm 4.2.2.1 with tdp/r3 3.2.0.10 (yes, I'm behind on a few things... ) Initially running with MAX_BACK_SESSIONS 15 BRBACKUPMGTCLASS A35_PR5_A A35_PR5_B A35_PR5_C A35_PR5_D I saw session 1 use mgmtclass A35_PR5_A session 2 use mgmtclass A35_PR5_B session 3 use mgmtclass A35_PR5_C session 4 use mgmtclass A35_PR5_D session 5-15 use mgmtclass A35_PR5_A so I moved to MAX_BACK_SESSIONS 15 BRBACKUPMGTCLASS A35_PR5_A A35_PR5_B A35_PR5_C A35_PR5_D A35_PR5_A A35_PR5_B A35_PR5_C A35_PR5_D A35_PR5_A A35_PR5_B A35_PR5_C A35_PR5_D A35_PR5_A A35_PR5_B A35_PR5_C and I thought things were corrected... but today I'm looking at things and currently I have some 269 files in the "A" mgmtclass, 48 in "B", 54 in "C" and 56 in "D" anyone else ever see this oddity ??????????????????? Dwight
