![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||
Solution Type Technical Instruction Sure Solution 1009306.1 : TAPE - Persistant Binding (with Leadville) for Shared FC Tape Drives Under NetBackup 5.1 Control
PreviouslyPublishedAs 212884 Applies to:Sun StorageTek 9840B Tape Drive - Version Not Applicable and laterSun StorageTek L180 Tape Library - Version Not Applicable and later Sun StorageTek L700 Tape Library - Version Not Applicable and later Sun Storage SAN Foundation Software - Version 4.0 and later All Platforms Checked for relevance on 25-July-2012. GoalThe StorEdge[TM] Network Foundation HBA requires special configuration steps to bind device World Wide Port Names (WWPN) for use by the Veritas NetBackup sg driver. In a shared storage environment (where the same tape drive X can be used by both Windows and Unix servers for backups and restores) it is critical that tape drives do not change device paths. The mapping from say "/dev/rmt/0" to a physical tape drive 2 can change after reconfiguration boots, after SAN reconfigurations and after NetBackup configuration changes. However, if the Solaris[TM] rmt device is bound to the World-wide Port Number (WWPN) of the Tape drive, then it is no longer possible for such reconfiguration events to impact the mapping of tape drive to physical Solaris devices. This document is intended as a guide for Customers who wish to configure FC Tape drives under Netbackup control with the following conditions: This document assumes that the correct steps have been taken with regard to SAN zoning, patching and general installation and configuration of NetBackup. FixSteps to Follow 1. Create a backup copy of the current st.conf file: 2. Move the existing sg.conf to a backup (this must be a move, otherwise a later step will fail): 3. Create a backup copy of the current devlink.tab file: 4. Delete SCSI targets/LUNs from the /kernel/drv/st.conf file: All of these entries should be removed, otherwise duplicates will be added later. 5. Delete SCSI targets/LUNs from /etc/devlink.tab. This is typically the section near the end of the file and the entries are typically of the form: # begin SCSA Generic devlinks file - creates nodes in /dev/sg type=ddi_pseudo;name=sg;addr=0,0; sg/c\N0t0l0 type=ddi_pseudo;name=sg;addr=1,0; sg/c\N0t1l0 type=ddi_pseudo;name=sg;addr=2,0; sg/c\N0t2l0 type=ddi_pseudo;name=sg;addr=3,0; sg/c\N0t3l0 type=ddi_pseudo;name=sg;addr=4,0; sg/c\N0t4l0 type=ddi_pseudo;name=sg;addr=5,0; sg/c\N0t5l0 type=ddi_pseudo;name=sg;addr=6,0; sg/c\N0t6l0 type=ddi_pseudo;name=sg;addr=0,1; sg/c\N0t0l1 type=ddi_pseudo;name=sg;addr=1,1; sg/c\N0t1l1 type=ddi_pseudo;name=sg;addr=2,1; sg/c\N0t2l1 type=ddi_pseudo;name=sg;addr=3,1; sg/c\N0t3l1 type=ddi_pseudo;name=sg;addr=4,1; sg/c\N0t4l1 type=ddi_pseudo;name=sg;addr=5,1; sg/c\N0t5l1 type=ddi_pseudo;name=sg;addr=6,1; sg/c\N0t6l1 # end SCSA devlinks Everything in this section should be removed, inclusive of the beginning and ending lines. 6. Now add the WWPN of each tape drive to the sg.links as shown in the example following: 7. Edit the sg.conf file adding the same WWPN's as follows: 8. Edit the st.conf file adding the same WWPN's, this time specifying which qlc instance the drive WWPN should bind to. In the example below two drives are bound to qlc instance 2 and two drives are bound to qlc instance 3: 9. Don't forget to add the forceload statements to the /etc/system file: 10. Edit the devlink.tab file CAREFULLY. Matching the Netbackup sg devices from the sg.conf to the appropriate WWPN. (Use only tabs between entries and not spaces). 11. Unload the sg driver: 12. Generate the configuration files (st.conf, sg.conf and sg.links): sg.build adds the proper entries to the sg.links and sg.conf files. Before running the script, make sure that all devices are powered on and connected to the HBA. 13. Use the provided script to re-create the /kernel/drv/sg.conf file with the appended SCSA entries in /etc/devlink.tab and reload the sg driver: 14. Now sgscan should see the appropriate devices: Please Note: each time a new device is added or an old device removed, re-create and re-install the new sg configuration 15. Run sgscan. The script /usr/openv/volmgr/bin/sgscan checks for devices that are not configured, and produces output similar to the following example: # /usr/openv/volmgr/bin/sgscan #WARNING: detected StorEdge Network Foundation connected devices not in sg configuration file: # # Device World Wide Port Name 21000090a50001c8 # # See /usr/openv/volmgr/MediaMgr_DeviceConfig_Guide.txt topic # "Configuring the Sun StorEdge Network Foundation HBA/Driver" # for information on how to use sg.build and sg.install # to configure these devices 16. Run the following Solaris command and note any output: Check in the /etc/path_to_inst that Solaris has configured devices for both the st and sg drivers: Common Issues: Reference: "Veritas NetBackup 5.1, Media Manager Device Configuration Guide", page 13 Chapter 2.
Attachments This solution has no attachment |
||||||||||||
|