ADSM-L

Re: [ADSM-L] Ang: Re: [ADSM-L] vtl versus file systems for pirmary pool

2011-09-27 12:16:30
Subject: Re: [ADSM-L] Ang: Re: [ADSM-L] vtl versus file systems for pirmary pool
From: Rick Adamson <RickAdamson AT WINN-DIXIE DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 27 Sep 2011 12:02:47 -0400
Interesting. Every VTL based solution, including data domain, that I looked at 
had limits on the amount of drives that could be emulated which were nowhere 
near a hundred let alone a thousand. Perhaps it's time to revisit this.

The license is a data domain fee, and a hefty one at that. 

The bigger question I have is since the file based storage is native to TSM why 
exactly is using a file based storage not supported?

~Rick


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Daniel Sparrman
Sent: Tuesday, September 27, 2011 10:30 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Ang: Re: [ADSM-L] vtl versus file systems for pirmary pool

Not really sure where the general idea that a VTL will limit the number of 
available mount points.

I'm not familiar with Data Domain, but generally speaking, the number of 
virtual tape drives configured within a VTL is usually thousands. Not sure why 
you'd want that many though, I always prefer having a small diskpool infront of 
whatever sequential pool I have, and let the bigger files pass the diskpoool 
and go straightly to the seq. pool.

As far as for LAN-free, the only available option I know of is SANergy. And 
going down that road (concerning both price & complexity) will probably make 
the VTL look cheap.

Not sure what kind of licensing you're talking about concerning VTL, but I 
assume it's a Data Domain license and not a TSM license? 

Best Regards

Daniel Sparrman



Daniel Sparrman
Exist i Stockholm AB
Växel: 08-754 98 00
Fax: 08-754 97 30
daniel.sparrman AT exist DOT se
http://www.existgruppen.se
Posthusgatan 1 761 30 NORRTÄLJE



-----"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> skrev: -----


Till: ADSM-L AT VM.MARIST DOT EDU
Från: Rick Adamson <RickAdamson AT WINN-DIXIE DOT COM>
Sänt av: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Datum: 09/27/2011 16:52
Ärende: Re: [ADSM-L] vtl versus file systems for pirmary pool

A couple of things that I did not see mentioned here which I experienced
was.... for Data Domain the VTL is an additional license and it does
limit the available mount points (or emulated drives), where a TSM file
based pool does not. Like Wanda stated earlier depends what you can
afford !

I myself have grown fond of using the file based approach, easy to
manage, easy to configure, and never worry about an available tape drive
(virtual or otherwise). The lan-free issue is something to consider but
from what I have heard lately is that it can still be accomplished using
the file based storage. If anyone has any info on it I would appreciate
it.

~Rick
Jax, Fl.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tim Brown
Sent: Monday, September 26, 2011 4:05 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] vtl versus file systems for pirmary pool

What advantage does VTL emulation on a disk primary storage pool have

as compared to disk storage pool that is non vtl ?



It appears to me that a non vtl system would not require the daily
reclamation process

and also allow for more client backups to occur simultaneously.



Thanks,



Tim Brown
Systems Specialist - Project Leader
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Email: tbrown AT cenhud DOT com <<mailto:tbrown AT cenhud DOT 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.

<Prev in Thread] Current Thread [Next in Thread>