Hi, No. Migration works be starting a process per node having the most data in a diskpool. Work arounds: - creating extra diskpools and plitting data by using multiple management classes and including dirs/file types across these management classes (complex). - creating multiple TSM nodes per server and do part of the server per TSM node (less complex); - using a tuned maxsize on the diskpool to have the larger/largest object of that node go directly to tape, bypassing the diskpool.
Regards, Karel -----Oorspronkelijk bericht----- Van: Abdulaziz Almuammar [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 6 januari 2004 17:05 Aan: [EMAIL PROTECTED] Onderwerp: Migration proccess issue Hi Guys, I have TSM 5.1.5 and 4 tape drives on 3494 tape library I configured the migration proccess to start with 4 migration proccesses and it is working fine. the problem is i noteced that there is only one migration proccess when the disk pool has data of one node. is there any way that i can make the migration proccess to start with 4 proccesses when it is triggered although the disk pool has only data of one node? ( the disk pool has alot of file spaces of one node ). Best Regards, Abdulaziz
