Hi Dough!
We choose a VTL over a file device class because several reasons:
1) IBM couldn't provide us a reference site with a 100 TB. + file device
class.
2) We were not sure how AIX would handle a crash with several very large
filespaces. How long will a filesystem check last?
3) How long will it take for TSM to mount a few hundred file volumes during
startup?
If you decide to use a file device class, limit the size of your volumes and
pre-define them. The smaller the volumes are, the less volume contention you
will encounter during multiple (multi-session) restores. You should
pre-define them to prevent fragmentation on the disks.
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-----Original Message-----
From: Thorneycroft, Doug [mailto:dthorneycroft AT LACSD DOT ORG]
Sent: Friday, June 17, 2005 19:47
To: ADSM-L AT VM.MARIST DOT EDU
Subject: File dev. type vs. VTL


I'm getting ready to add more disk to my TSM server,
Are there any advatage/disadvatages to using a Virtual tape library
instead of TSM defined file device types.
(Do TSM file device types work with multi session restores?)

Doug Thorneycroft
> Systems Analyst
> County Sanitation Districts of Los Angeles County
> 1955 Workman Mill Road
> Whittier, CA 90601
> Tel: (562)699-7411, Ext. 1058
> Fax:(562)695-6756
> www.lacsd.org
>
>


**********************************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), 
its subsidiaries and/or its employees shall not be liable for the incorrect or 
incomplete transmission of this e-mail or any attachments, nor responsible for 
any delay in receipt.
**********************************************************************