Hi Nick, I did have a look for my old notes earlier today but I'm afraid I'm drawing a blank (they'd be from over 5 years ago...).
In summary (from what I remember) the customer had a TSM Server library manager instance for a Quantum P7000 running 16 or so LTO2 drives. The Celerra was defined as a datamover on this and there were paths defined for these drives mapped to the special device files on the datamover. The TSM Server acted as a library manager in pretty much the same way as it would for any library client. In fact, it's pretty much the config described in 'Configuration 1' in the TSM docs on the subject >>> http://bit.ly/9KVVXS There is the option, as your Celerra admins seem to suggest, to have the Celerra connect to its own dedicated library (as per 'Configuration 2' in the above document) and it's perhaps this that they have been referring to. As far as I remember, the basic configuration was pretty much as per the TSM NDMP docs, nothing much sticks in my mind as being Celerra-specific. Keep in mind that my info might be a little out of date now, but I'm sure any major game-changes would be clear in the IBM docs. Hope that helps, /David McClelland London, UK -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nick Laflamme Sent: 22 March 2010 12:09 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Celerra NDMP Sanity Check I appreciate whatever you might come up with, David. If nothing else, you've given me some ammunition for convincing colleagues we have to do this differently. Nick On Mar 19, 2010, at 5:11 PM, ADSM-L wrote: > Nick, > > Very quickly - yes, shared is how I've worked with them in the past > (about 4 or 5 years ago though). No promises, but I'll see if I can > dig something out from how we did it when I'm in front of my PC again. > > /David McClelland > (from my iPhone somewhere in) London, UK > > On 19 Mar 2010, at 21:55, Nick Laflamme <dplafla...@gmail.com> wrote: > >> I need a sanity check. We're trying to implement new virtual tape >> devices on new devices with our existing set-up, including some >> storage agents and a handful of NDMP clients. The storage agents, no >> problem. We know how to do storage agents. The NetApp filers? No >> problem; they're just like storage agents, except for the whole >> "dedicated device class" thing, but at least we can get tape drive >> serial numbers from our NetApp administrators so we can map out the >> paths like we would for a storage agent or another TSM server >> sharing a library on a SAN. >> >> We've got two Celerra clients that are testing me. Their >> administrators swear up and down that all they can find -- and all >> we need -- are the device names, that there's no need for device >> serial numbers. >> >> The instructions from EMC also include steps to define a path from >> the Celerra to the library changer, not just to the drives. That >> makes me think EMC expects us to dedicate drives and a library >> (partition) to each Celerra. I can't find any TSM documentation or >> Redpieces that are specific to Celerra, so I turn to the list: >> >> Do other EMC Celerra sites using TSM dedicate tape libraries to >> their Celerras for NDMP, or is there a way to make the Celerra play >> well with other LAN-free clients? >> >> TSM 5.5.3, AIX 5.3, if it matters. Not sure about Celerra code levels. >> >> Thanks, >> Nick No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.791 / Virus Database: 271.1.1/2762 - Release Date: 03/21/10 19:33:00
