When I looked into this subject I found that lanfree supports: - vtl - physical tape - file devices on GPFS (a san filesystem) - file devices via Sanergy (nfs but with data being sent over fibre channel) - I found a specific comment that straight NFS for sharing File devices is not supported by IBM (doesn't mean it doesn't work)
>From what I could figure out, Sanergy works below the NFS protocol. Sanergy slips in below the NFS protocol and routs NFS data blocks across a fibre channel connection. Rick From: Rick Adamson <rickadam...@winn-dixie.com> To: ADSM-L@VM.MARIST.EDU Date: 09/27/2011 01:41 PM Subject: Re: Ang: Re: [ADSM-L] vtl versus file systems for pirmary pool Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> Sorry, By not supported I meant for lan-free. Every bit of documents I've read only refer to using a physical or virtual tape library. ~Rick -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Allen S. Rout Sent: Tuesday, September 27, 2011 12:55 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Ang: Re: [ADSM-L] vtl versus file systems for pirmary pool On 09/27/2011 12:02 PM, Rick Adamson wrote: > 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? Not supported by what? If you've got a DD, then the simplest way to connect it to TSM is via files. Some backup apps require something that looks like a library, in which case you'd be buying the VTL license. FWIW, if you're already in DD space, you're paying a pretty penny. The VTL license isn't chicken feed, I agree, but it's not a major component of the total cost. - Allen S. Rout ----------------------------------------- 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.