Thanks for your response ,
Why 32 drives ?
Yes VTL can write 10 TB/ hr without DD Boost
I may not start with 32 but still need to calculate total number of servers ,
any time constraint and database size to decide the count
> On 16 Sep, 2014, at 1:57 am, Nick Laflamme <nick AT LAFLAMME DOT US> wrote:
> When I worked in a TSM/DD shop with Data Domain VTLs, we did something a
> little different: we defined for each TSM server both a "normal" VTL
> instance and a "LAN-free" library for any storage agents. The TSM master
> server needs access to the LAN-free library so it can mount tapes and
> validate tape labels, but our copypools for the standard policies were set
> to use storage pools in the "normal" libraries. Only clients assigned to
> specific domains ended up with access to the LAN-free libraries --or were
> relegated to the LAN-free ghetto, if you prefer. :-)
> We could have used shared libraries among our TSM servers, but we had had
> some bad experiences with a similar configuration using EMC Clariian VTLs.
> Spinning off dedicated VTLs is trivially cheap, so why not?
> On Mon, Sep 15, 2014 at 11:45 AM, Saravanan Palanisamy <
> evergreen.sarav AT gmail DOT com> wrote:
>> Dear TSM Folks,
>> Has anybody tried this approach to enhance tape drive availability ?
>> Create 64 tape drives in data domain and allocate 32 tape drives only for
>> TSM server backup ( Lan based backup) and remaining 32 tape drives dedicate
>> for storage agent
>> Is this possible to implement this setup ?
>> I really had concern because storage agent definitely need tape drive
>> should be defined and path must be online in TSM server before defining
>> path for storage agent.
>> Will it work if turn off tape drive path in TSM server and only turn on
>> corresponding path for storage agent ? I never tried this approach and has
>> anybody got real time experience on this setup?
>> Thanks & Regards,
>> Mobile: +65-86966188