ADIC Scalar i2K & Legato Networker - Config / modules required

ad 3) Yes - over the network.

Will you have this library partitioned (multiple application sharing it) or will it be dedicated to NetWorker for backup?

1. There has not been much documented about speccing a Networker server; however if you contact your EMC pre-sales contact they now have a sizing tool which is very useful. I have it on my laptop which I do not have a network connection for at present, but I am not too sure if it is something I am allowed to give out (plus there may be an updated version!) so contacting EMC may get it to you quicker.

2. You should need no additional software to backup your data to the I2K. You will need to install the ADIC Management Console if you want to manage the library from a workstation rather than the front panel of the library, but this is not essential and will have no impact on Networker.

3. If your workstations are not on the SAN then they will need to backup across the network via either the Networker server or a storage node. If you put the clients onto the SAN and wish to back up directly you will need to purchase Dedicated Storage Node and DDS licenses. If you have a large amount of data on a client this will probably be the preferable route unless you have a large backup window and/or gigabit ethernet.

Good - then you don't need any additional SW from Legato side).


If your backup server and potential storage nodes will be zoned correctly yes.


There 3 NetWorker components:
- client
- storage node
- server

In short:
- Client is backing up and restoring data.
- Storage nodes is managing drives/libraries.
- Backup server is controlling all that plus makes metadata management.

License you will need for storage node depends on your HW setup and general idea how you want this to setup. If yiu have basic setup where one box is server and controls all the drives than all licenses are already covered by the basic one.


All licenses get installed on server (or license manager if installed and if in use).

I appreciate the information.
Follow-up:

The Library will be dedicated to Legato.

The Networker server will be SAN attached, (HBA's), therefore do I assume that Networker will see the Library?

You mention storage node, can you explain exactly what a storage node is? Is that a separate server SAN attached?

The DDS licenses and dedicated storage node. Do the DDS licenses get installed on the client or server?

I haven't got a lot more to add from my initial response and what Hrvoje added afterwards. I would suggest you engage your EMC partner to discuss what you are trying to achieve in more details as it sounds like you probably need to define what you are hoping to achieve a little more closely and also so that you are happy that the licensing costs will fall within your budget.

I am running the same setup and it works perfectly. Running over the network is just slower. Feel free to ask if you have any questions.

The library is now installed. We are using QLogic HBA attached to a HP (brocade) SAN Switch. The Server sees the Tape Drives (Since the Server sees the drives I assume I have the HBA/FC portion of the task complete)

However I am having problems with getting the Windows 2003E server to load the proper drivers for the following:

1. Tape Drives - IBM ULTRAMUM _TD3 SCSI Sequential Device

2. ADIC Scalar I2000 SCSI Array Device

I can not seem to locate the proper drivers (except for the library).

Am I overlooking the obvious / can someone direct me to the drivers for the Tape IBM LTO3 and (item 2.).

The drivers should be downloadable from IBM's website... Possibly this one:

http://www-1.ibm.com/support/docview.wss?rs=543&context=STCVQ6R&dc=D430&uid=ssg1S4000189&loc=en_US&cs=utf-8&lang=en

You don't actually need a driver for the Array Device, but I believe ADIC can provide you with one or at least a procedure so that it will stop prompting you to provide one.

The IBM drivers you can get from IBM's site.

A storage node would be a system connected to the SAN that would backup itself (dedicated) to SAN attached tape drives. There are other storage nodes which can backup LAN clients also, used to grow your environment when your networker server has a bottleneck (LAN, SAN, tape drives). DDS is used to share all or some of your tape drives in the I2k between the server and storage node, rather than having to split them up, 2 for the server, 2 for the node. Both systems can use any of the 4 drives, as long as they are not in use by the other. As mentioned, depending on your network, window, and client, I tend to make a dedicated storage node out of anything with over 100GB.

I would like to ask this question and update the thread.
I was successful at installing Networker and backing up the Legato Server itself as well as a test HP UX server. I feel comfortable that the foundation is in place.

My follow-up questions are more about the HBA/FC configuration.

I have 6 tape drives in the ADIC so a total of 4 FC cables are connected to my SAN Switch.

I have 2 Qlogic HBA installed in the Legato Server.

With this design it appears that all connections are active and my Windows server detects a total of 12 tape drives. What am I missing as far as failover / redundancy?
Obviously I should only be seeing 6 drives not 12.

If you run the inquire command and compare the drives you are seeing you should see that each drive is seen twice, once through each HBA (look at serial number and WWN)... Configuring zoning on the switch will allow you to present only specific drives to each HBA; if you fail to do this you will have issues when an attempt is made to access both names the drive is known as!

I appreciate all the information to date. I have another issue, I have successfuly got the library and my Networker server (win2003e) functioning without any problems. I am now tasked with getting my first storage node configured on an HP UX v 11.x server. I believe I have my zones proper because the UX box sees the library however it does not see the drives as tape drives it sees them as rscsi. I have (6) IBM LTO3 drives in the ADIC i2k and I am not able to get the devices created so that Legato Networker sees the drives as shared drives (using the inquire command on UX) Any info would be useful.

Do you see the drives with ioscan? Just do "ioscan -fnC tape" and see what you get (to speed up the things you can first query the kernel via ioscan -fnkC tape).

Here is what I see doing the ioscan -fnC tape

Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
tape 0 0/0/1/0.3.0 stape CLAIMED DEVICE HP C1537A
/dev/rmt/0m /dev/rmt/c0t3d0BESTn
/dev/rmt/0mb /dev/rmt/c0t3d0BESTnb
/dev/rmt/0mn /dev/rmt/c0t3d0DDS
/dev/rmt/0mnb /dev/rmt/c0t3d0DDSb
/dev/rmt/c0t3d0BEST /dev/rmt/c0t3d0DDSn
/dev/rmt/c0t3d0BESTb /dev/rmt/c0t3d0DDSnb


This the ADIC information: ioscan -fn

fcp 1 0/12/0/0.1 fcp CLAIMED INTERFACE FCP Domain

ext_bus 7 0/12/0/0.1.8.0.0 fcparray CLAIMED INTERFACE FCP A

rray Interface

target 13 0/12/0/0.1.8.0.0.0 tgt CLAIMED DEVICE

ctl 5 0/12/0/0.1.8.0.0.0.0 sctl CLAIMED DEVICE ADIC

Scalar i2000

/dev/rscsi/c7t0d0

target 15 0/12/0/0.1.8.0.0.1 tgt CLAIMED DEVICE

ctl 7 0/12/0/0.1.8.0.0.1.0 sctl CLAIMED DEVICE ADIC

Scalar i2000

/dev/rscsi/c7t1d0

target 17 0/12/0/0.1.8.0.0.2 tgt CLAIMED DEVICE

ctl 9 0/12/0/0.1.8.0.0.2.0 sctl CLAIMED DEVICE ADIC

Scalar i2000

/dev/rscsi/c7t2d0

target 19 0/12/0/0.1.8.0.0.3 tgt CLAIMED DEVICE

ctl 11 0/12/0/0.1.8.0.0.3.0 sctl CLAIMED DEVICE ADIC

Scalar i2000

/dev/rscsi/c7t3d0

target 21 0/12/0/0.1.8.0.0.4 tgt CLAIMED DEVICE

ctl 13 0/12/0/0.1.8.0.0.4.0 sctl CLAIMED DEVICE ADIC

Scalar i2000

/dev/rscsi/c7t4d0

target 23 0/12/0/0.1.8.0.0.5 tgt CLAIMED DEVICE

ctl 15 0/12/0/0.1.8.0.0.5.0 sctl CLAIMED DEVICE ADIC

Scalar i2000

/dev/rscsi/c7t5d0

target 25 0/12/0/0.1.8.0.0.6 tgt CLAIMED DEVICE

ctl 17 0/12/0/0.1.8.0.0.6.0 sctl CLAIMED DEVICE ADIC

Scalar i2000

/dev/rscsi/c7t6d0

target 27 0/12/0/0.1.8.0.0.7 tgt CLAIMED DEVICE

ctl 19 0/12/0/0.1.8.0.0.7.0 sctl CLAIMED DEVICE ADIC

Scalar i2000

/dev/rscsi/c7t7d0

target 29 0/12/0/0.1.8.0.0.8 tgt CLAIMED DEVICE

ctl 21 0/12/0/0.1.8.0.0.8.0 sctl CLAIMED DEVICE ADIC

Scalar i2000

/dev/rscsi/c7t8d0

target 31 0/12/0/0.1.8.0.0.9 tgt CLAIMED DEVICE

ctl 23 0/12/0/0.1.8.0.0.9.0 sctl CLAIMED DEVICE ADIC

Scalar i2000

/dev/rscsi/c7t9d0

target 33 0/12/0/0.1.8.0.0.10 tgt CLAIMED DEVICE

ctl 25 0/12/0/0.1.8.0.0.10.0 sctl CLAIMED DEVICE ADIC

Scalar i2000

/dev/rscsi/c7t10d0

target 35 0/12/0/0.1.8.0.0.11 tgt CLAIMED DEVICE

ctl 27 0/12/0/0.1.8.0.0.11.0 sctl CLAIMED DEVICE ADIC

Scalar i2000

/dev/rscsi/c7t11d0

target 37 0/12/0/0.1.8.0.0.12 tgt CLAIMED DEVICE

ctl 29 0/12/0/0.1.8.0.0.12.0 sctl CLAIMED DEVICE ADIC

Scalar i2000

/dev/rscsi/c7t12d0

target 39 0/12/0/0.1.8.0.0.13 tgt CLAIMED DEVICE

ctl 31 0/12/0/0.1.8.0.0.13.0 sctl CLAIMED DEVICE ADIC

Scalar i2000

/dev/rscsi/c7t13d0

target 41 0/12/0/0.1.8.0.0.14 tgt CLAIMED DEVICE

ctl 33 0/12/0/0.1.8.0.0.14.0 sctl CLAIMED DEVICE ADIC

Scalar i2000

/dev/rscsi/c7t14d0

target 43 0/12/0/0.1.8.0.0.15 tgt CLAIMED DEVICE

ctl 35 0/12/0/0.1.8.0.0.15.0 sctl CLAIMED DEVICE ADIC

Scalar i2000

/dev/rscsi/c7t15d0

ext_bus 9 0/12/0/0.1.8.255.0 fcpdev CLAIMED INTERFACE FCP D

evice Interface

target 45 0/12/0/0.1.8.255.0.0 tgt CLAIMED DEVICE

ctl 37 0/12/0/0.1.8.255.0.0.0 sctl CLAIMED DEVICE ADIC

Scalar i2000

/dev/rscsi/c9t0d0

*****************************************************end
Any Ideas?