Shortly... blades boot from SAN with FC cards, FAS 2020, XenServer and IBM TS3100 library by FC.
My idea is to make full backup of filler by NDMP because there is a problem with pass-through for FC ports to VM's in XenServer.
I don't want dedicate separate server as backup server in my chassis.
My filler has two controllers, each with two FC ports. It's connected to SAN swithes with four paths. I use multipath in XenServer - four paths used.
The problem is that filler doesn't see the library connected to SAN switch. The zonning is made correctly, to one filler's FC port.
I red articles and want to ensure is it true that I CANNOT use tape drive which is connected to SAN switch and zonned to the filler's port (that port is also used by host connection through SAN switch).
If it's true what is solution for me? Should I change zoning and run the data flow on three paths and use the last one for tape drve only?
The onboard ports are either Target or Initiator. In your case they are targets for Xen. To work for tape, you need Initiator ports. These ports cannot do both simultaneously. Unfortunately there is no PCI slot on the 2020 to add more ports. If you type "fcadmin config" you will see 0a/0b are targets from the description below, and you don't have ports to connect tape.
A workaround you could use is ndmp over ethernet. Configure the tape library on a server, then do ndmp from the 2020 to that server. This has been a part of the ndmp protocol for many years...the backups will run over ethernet to the server then from the server to tape... not as efficient as direct attached tape, but since it isn't feasible teh 2020 would push more than a gig anyway, I don't see a bottleneck... unless the network ports are being used for other workloads.
We have two filers connected to a dual drive library and a Windows server via an FCP switch, so yes it will work.
The port you are connecting the tape to needs to be configured as an initiator. The CLI filer command fcadmin config we display the current config. If it needs changing, sorry filer reboot. This port can not be used to connect to disk shelve or host servers. There are also the same rules for quad port cards which share chips between ports. See now site
The switch should have link lights for the filer and tape, if not replace cables and confirm licenses on switch. The NetApp filer does not require an FCP lincense for to use FC tapes. Tape drives/media changes do not support multipath so only use a single switch can set your zoning as point to point.
Now that you have configure the switch confirm that the filer can "see" the tape
sysconfig Is it on the correct port
sysconfig -t Are the drive options correct (LTO / SDLT, etc)
sysconfig -m Is it the correct library
If it is not showing the tape. Try either removing the filers FC cable and wait for the filer to down the port (console message) or use the command storage disable adapter <name|0a...>. Wait for about a minute then enable the port. The file will then scan for new devices.
Still no joy confirm to storage router is configured correctly in the tape and terminators are in the correct place.
Once you can get the filer to 'see' the tape, you just need to enable NDMP, create an backup account with both a filer password and an NDMP password which the filer creates. Review the ndmpd command, yes there is an extra d on the end.
Your backup app should now be good to go.
If you are still having problems go make to basics. Show that the filer will work with the library by using a single FC cable in a point to point config. Once this is working, add in the switch, etc.
One improtant thing. You have written "This port can not be used to connect to disk shelve or host servers.". Did you mean exactly "host servers" or this port can be used to connect to host servers but using FCP switch? Is is difference?
If the port cannot be used to any other operation that tape backup, then I have to decrease HA down to three paths to my blades and make the preparing as you described.
Yes you can have your servers/hosts and tape on the same FCP switch, just need to create the zoning correctly.
"The best practice would be to have separate zones for each filer. The zones consist of one initiator from the filer and respective dedicated tape drives and a separate zone for the Robotic arm and NetBackup host only."
Fibre Channel Libraries Many libraries with fibre channel interfaces employ a combination of fibre tape devices and/or SCSI tape devices. If the library is supported by NetApp with a particular tape device , then devices listed as SCSI in the matrix above are also supported when accessed via the fibre channel interface of the library. If a fibre channel interface library is supported via switch attachment, it is also supported without a switch. If the devices in the library attach directly to the storage appliance (i.e. not through a bridge device in the library) then only the interfaces in the matrix are supported.
I feel that we don't understand each other 🙂 Sorry for it.
I still don't know is specific filler's fc port able to work with tape drive as well as hosts via fc switch.
You wrote that "The port you are connecting the tape to needs to be configured as an initiator. The CLI filer command fcadmin config we display the current config. If it needs changing, sorry filer reboot. This port can not be used to connect to disk shelve or host servers. There are also the same rules for quad port cards which share chips between ports."
If I change the filler's fc port type to initiator (to enable it to work with tape drive) will it work with the hosts via fc switch as well? This port is target type now.
I think from the original post that both 0a/0b are fc target adapters..so tape will not work since a port can't be changed to initiator because all ports are targets. With no additional ports available, this 2020 won't be abke to attach to tape... Unless you go with 1 target for fc luns and 1 initiator for tape but that doesn't sound like an option.
If you have no extra disk shelves it will it will be possible to configure one port for host/servers to access via the FC switch and the other port to access the tape drive. You can not mix tapes and hosts on the same port on the filer.
You could configure your systems (Two FAS2020 in a cluster) so that both filers, each via a single port, are connected to the tape via a single switch. ie 3 cables. You could then connect your hosts to the same switch using the remaining two ports on the FAS2020. This would allow both filers to create NDMP backups, you could also connect a server to the tape via the FCP switch so that you could backup the server's local data (lun contents, rather than NDMP dump of lun, which will only restore to a Netapp filer) using a media agent. It is possible to have the backup server running in a VM, mount flexclones and backup the contents of LUNs to the tape which the VM thinks is connected directly to itself. This is the configuration we run here.
"It is possible to have the backup server running in a VM...". The VM doesn't see any fc cards yet.
"Enterprise" grade backup software supports libraries and tapes connected directly to NDMP host. Backup server itself does not need any direct connection to library in this case; server is using NDMP protocol to control library through filer. Whether BE supportes it, I do not know - you need to check BE documentation.