Also, IBM did one of their Technical Exchange calls on NDMP setups, it might be worth looking at: http://bit.ly/bUBPgk
/David Mc London, UK -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nick Laflamme Sent: 23 March 2010 01:53 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Celerra NDMP Sanity Check On Mar 22, 2010, at 6:38 PM, David McClelland wrote: > 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. OK, thanks. I know my predecessors made it work with a shared library; I suspect it was a lot of trial-and-error, and if there's a "smarter" way, I'd love to find it. > Hope that helps, It doesn't hurt to have more experiences to draw upon, certainly. > /David McClelland > London, UK Nick
