Glad to see you at Pulse, but I got a similar problem here in Sweden where the
migration only use one process during migration.
I was thinking of to open a PMR to understand why it only use one drive.
Cell: +46-70-325 1577
E-mail: Christian.Svensson AT cristie DOT se
CPU2TSM Support: http://www.cristie.se/cpu2tsm-supported-platforms
Från: Prather, Wanda [wPrather AT ICFI DOT COM]
Skickat: den 13 mars 2012 21:36
Till: ADSM-L AT VM.MARIST DOT EDU
Ämne: Re: migration threads for random access pool and backups issue
Since your disk pool is much smaller than what you are backing up, plus you
have plenty of tape drives, it doesn't make much sense to send those 3 large
filespaces to the diskpool.
Create a new management class, send each of those 3 filespaces directly to the
tape drives, bypassing the disk pool.
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Sent: Sunday, March 11, 2012 12:09 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] migration threads for random access pool and backups issue
I have to backup large data ~ 300TB and have small DISK POOL SIZE 500GB. I have
3 filespaces, backing up on single node. I am triggering multiple dsmc,
dividing the filespace on directories. I have 15 E06 Tape drives and can
allocate 5 drives for this backup.
If I run multiple dsmc sessions the, server starts only one migration process
and one tape mount.
As per ADMIN GUIDE the Migration for Random Access is "Performed by node.
Migration from random-access pools can use multiple processes."
1. On Random Access pools multiple migration sessions can be generated, only if
we backup on multiple nodes ? Is my understanding correct or there is any way
to increase the number of tape mounts ?
2. The only way to speed up with current resources is to backup to File device
class, so that I can have multiple tape mounts?
3. Any inputs to speed up this backup?
Server and client both are on Linux, running TSM version 6.2.2
Any suggestions are welcome.