Re: [ADSM-L] Load balancing when you have many virtual tapes?
2014-10-13 13:10:51
What kind of drive are they emulating? Are they emulating IBM drives with
Atape driver? My understanding (I've been trusting this for years) will auto
load balance across hba's.
Rick
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Erwann Simon
Sent: Monday, October 13, 2014 12:36 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Load balancing when you have many virtual tapes?
Hello Wanda,
As TSM allocates drives in order, you have to distribute drive between the HBAs
in a round robin way (with 4 hba : drive 1 on hba 1, drive 2 on hba... drive 5
on hba 1 and so on). I prefer doing this at VTL level using mapping policy (i.e
access groups on Data Domain).
Le 13 octobre 2014 18:28:36 CEST, "Prather, Wanda" <Wanda.Prather AT ICFI DOT
COM> a écrit :
>TSM 7.1.1 on AIX
>So I have a customer putting in a VTL, which will have 96 virtual
>drives.
>Those virtual drives will be spread across 4 HBA's.
>
>What sort of strategies to people use to keep TSM from starting a
>BACKUP stgpool process and picking 4 virtual drives all on the same
>HBA?
>Is it dependent on the order you do your DEFINE DRIVE commands? Better
>to set up multiple virtual libraries?
>
>Any suggestions appreciated.
>
>Wanda
>
>
>Wanda Prather | Senior Technical Specialist |
>Wanda.Prather AT icfi DOT com<mailto:Wanda.Prather AT icfi DOT com> |
>www.icfi.com<http://www.icfi.com/> | 410-868-4872 (m)
>ICF International | 7125 Thomas Edison Dr., Suite 100, Columbia, Md
>|443-718-4900 (o)
--
Erwann SIMON
Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.
-----------------------------------------
The information contained in this message is intended only for the personal and
confidential use of the recipient(s) named above. If the reader of this message
is not the intended recipient or an agent responsible for delivering it to the
intended recipient, you are hereby notified that you have received this
document in error and that any review, dissemination, distribution, or copying
of this message is strictly prohibited. If you have received this communication
in error, please notify us immediately, and delete the original message.
|
|
|