Celerra NDMP with TSM and EDL

Please ensure that the Target WWN of the EDL port is selected in the zone configuration while zoning the data mover AUX port to EDL. The same EDL port can be used as Initiator or Target - in this case, it will be target. While zoning EDL to Physical Tape library - it will be an initiator.

Also, verify with the EDL person whether the NAS Data mover has been configured as a SAN client properly and the Tape drives on EDL are assigned to the SAN Client.

In other words, please ensure that the data mover AUX port is visible to the EDL.

If you can't probe any tape device on the data mover, it may be either a EDL configuration issue or a Fiber connectivity issue.

My 2 cents - and sorry for jumping into this conversation late.

Thanks,
Sandip

yes, expecially if you have a gateway Celerra make sure they connect and zone the AUX ports of the data mover for the tape drives

Thats an easy mistake to make since the ports to connect to the SAN for Clariion/Symmetrix are already there - but we definitely do NOT support connecting tape drives to the BE ports

More info based on previous questions
Library I am emulatng?
TSM : Library Type: SCSI Drive: EDL-T9940B-200004 ECARTRIDGE
EDL: Vendor ID: STK Product ID: L700 Slots: 678 Drives: 20
Is everything Zoned Correctly? Yes - Celerra HBA AUX0 (HBA 2) zoned to EDL port

Did I see the Celerra HBA Login to the EDL console? I Yes - you can see the datamover HBA

Was it configured as a client? San Client YES - and drives assigned to the client

Was it assigned to a virtual library? DM3 YES
Am I sharing virtual library within TSM and Celerra DataMovers? Yes - that is the plan

do a server_devconfig server_3 -p -s -n
No devices on any chain

I'l attempt the shot-in-the-dark reboot the dm method later this week

Is the robotics shared between TSM and datamover? No

What we plan to do is option 1 Share drives between TSM and datamovers, while robotics is controlled by TSM


We reviewed the EDL config again... looks fine.. the dm's have been added as SAN clients and assigned drives... but Celerra is not detecting them

the virtual library you have defined in EDL ..is robotics and drives are shared between TSM server and datamover ? Robotics can not be shared between TSM and datamover, you have two choices:

1) you can share drives between TSM and datamover, while robotics is controlled by TSM
2) you can present drives and robotics strictly to datamover and let datamover control robotics, so basically you create a dedicated virtual library strictly for NDMP backups.

you can go with option one as it's the easiest but keep in mind that even then virtual tapes can not be shared for datamover backups and regular open systems backups because in TSM you will need to define a storage pool specifically for datamover and its type is celerradump ...hence you will not be able to put any open systems data on it.

i am sorry if i missed it ..what type of drives are you emulating ?

It has been a while since I did my last CDL (now EDL) configuration - but I remember there was a checkbox to be selected while configuring SAN Client in case the client is a Celerra. Is it still there and checked?

I hope you are working with EMC guys on the configuration issue at the same time while we are discussing here in the forum.

Regards,
Sandip

yeah ..those are supported. Weird stuff ...let's see if reboot helps.

emulating 9940b drives


and yes the Celerra checkbox is still there and yes it has been checked


Thank you all for your guidance, by the way ! your continued guidance is very helpful !
I've opened a case w/ EMC and I still plan on rebooting a datamover.

anybody else using that port on EDL ?

I have some progress to report..

one of my three datamovers.. ( just got this one zoned in last night) has now discovered a tape unit, I've added it in

jbox1 c96t0l0 jbox STK L700 3.05
tape2 c96t0l1 tape STK T9940B 1.32.427

there is only one difference between it and the other two datamovers that I've been unable to discover tape devices from.. it's that those two dm's are zoned to a different EDL SP port... as stated before they are seen by the EDL and SAN clients have bee added

yes, just as other things are using the same EDL port for the successfully discovered DM

No issues my friend - I can understand your situation and the pain to get the issues resolved.
However, truly appreciate your effort to keep us updated.
Hopefully someone will be able to help you on the TSM question you have.
Cheers
Sandip

Thanks for the update - this is exactly what I suspected and mentioned in my very first reply to this post (page 2) that ensure that the EDL ports are configured as Target as the same port can be an initiator also - trick is while selecting the WWN.

However, I am not having any TSM experience so will keep my mouth shut (sorry keyboard ) .

Thanks,
Sandip