We use ours as VTL because it was a very simple replacement of the existing VTL. We only use 48 drives and use disk pools to catch the incoming backups. The other advantage of VTL for us is speed. We have very limited 10Gb Ethernet and loads of 4Gb FC. 1Gb would be far too slow. We did look and using NFS, but the network ruled that out.
Andy Huebner -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick Adamson Sent: Friday, June 17, 2011 8:35 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] tsm and data domain I have had DD implemented for about a year now, but I fail to understand why anyone would utilize the DD VTL license when using TSM? Mine are setup as a simple SAN device with defined directories that correspond to my TSM primary storage pools. I have the device calss in TSM set as the type "file" and let TSM manage the virtual volumes as it would any other disk storage. There is another DD system that is located at our DR facility, and all data including TSM DB backups are replicated to that location. This allows me to no longer have copy pools. I have "cold" stand-by TSM servers at my DR site that can be recovered and online within 1-2 hours and ready to recover systems. Plus I save the cost of VTL licenses and the storage requirements for the copy pools....and using the "file" device class means I really do not have to be concerned with mount point limits. Interested in feedback..... ~Rick Adamson Jacksonville, FL. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of PAC Brion Arnaud Sent: Friday, June 17, 2011 3:11 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] tsm and data domain Tim, We are right conducting a POC with a pair of DD860, and are relatively satisfied with them. The machines are mostly used as VTL except for a small NFS partition which is used or TSM DB backups. Deduplication rate is OK : around 10 so far, with a good mix of Exchange, Oracle, DB2 as well as Win and AIX data. Ingestion rate is corresponding to our needs, slightly more than 1 GB/s , and the possibility to define plenty drives. Negative or "no so impressive" points, so far : deduplication rate is a "global" factor, impossible to know what type of data dedupes better than another one, thus lowering the granularity of deduplication monitoring . We also experienced pretty long initialization times for the TSM server attached to a virtual library having 100 drives : at restart TSM server needs at least 15 minutes to recognize all the drives, thus generating numerous client errors, as they try to get a drive which is defined but not available. We still have to experiment if defining more smaller libraries would solve that issue ... At least replication : it is still unclear for me what would be happening if we do rely on replication to replace copy storage pools, and if our TSM server crashes on primary site while replication is not completed. To my mind the virtual volumes contents would not be matching TSM DB content : not sure so far on how to handle such a situation ... Hope this helped ! Cheers Arnaud ************************************************************************ ****** Corporate IT Systems & Datacenter Responsible Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: arnaud.br...@panalpina.com ************************************************************************ ****** -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tim Brown Sent: Thursday, 16 June, 2011 21:50 To: ADSM-L@VM.MARIST.EDU Subject: tsm and data domain Any one use emc's data domain devices for storage pools and replication Would like to here positive and negative issues. Thanks, Tim Brown Systems Specialist - Project Leader Central Hudson Gas & Electric 284 South Ave Poughkeepsie, NY 12601 Email: tbr...@cenhud.com <<mailto:tbr...@cenhud.com>> Phone: 845-486-5643 Fax: 845-486-5921 Cell: 845-235-4255 This message contains confidential information and is only for the intended recipient. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, please notify the sender immediately by replying to this note and deleting all copies and attachments. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
