Veritas NetBackup (NBU) Software
 
Solstice Backup (SBU) Software
 
Sun Storage L100 Tape Library
 
Sun Storage L25 Tape Library
 

GCS>Sun Microsystems>Storage - Tape>Libraries - L-Series
 

Applies to:

Goal

Solution

Prior to starting the confirguration of your EBS or NBU environment:

1. Ensure that the Sun StorEdge L25/L100 library is connected, powered up, passed its internal diagnostics and available for use (all the above are visible from the from panel on the library).
2. Confirm the Sun StorEdge L25/L100 libraries changer and tape drives are visible in the Solaris Operating Environment see < Solution: 216527 >  
3. Check that serialization is enabled from the front panel of the library. If disabled, then enable it by performing the following steps:
   • On the main screen, press Menu. The GUI displays the Menu screen.
   • Press Config. The GUI displays the Configuration screen.
   • Press the Up or Down buttons until Serialization is highlighted.
   • Press Select.
   • Use the Up or Down buttons to select Enabled.
   • Press Select.
   • Press Main to return to the main screen.

In the examples presented below, the Sun StorEdge L25/100 libraries have been configured with two tape drives (from the library front panel, target IDs are set as follows):

  Robot   = ID-0
Drive-1 = ID-1
Drive-2 = ID-2

Configuring Sun StorEdge Enterprise Backup Software (EBS)

If you are using EBS 7.x, you will need to follow the procedure outlined below. In a bridge environment, lus_add_fp_devs will not detect all the devices attached through a FC420 bridge. Some manual configuration of lus driver will be needed.

Run "/usr/sbin/nsr/lus_add_fp_devs" to detect devices as needed.

this will create the lus.conf, but will only add lun 0 to the file.

Run /usr/sbin/nsr/inquire to confirm that only the device on lun 0 is displayed:

   [email protected]:M4 DATA MagFile         3.07|Autochanger (Jukebox)
S/N: RBD12A0140

NOTE: The lus.conf file will need to be edited (see below) to include entries for each of the tape drives.

Run "cfgadm -la -o show_FCP_dev" to determine which devices are seen through Solaris and their luns.

sample output:

   Ap_Id                      Type         Receptacle   Occupant     Condition
c7                         fc-fabric    connected    configured   unknown
c7::2100001086107794,0     med-changer  connected    configured   unknown
c7::2100001086107794,1     tape         connected    configured   unknown
c7::2100001086107794,2     tape         connected    configured   unknown
c7::2100001086107794,3     ESI          connected    configured   unknown

From the above output:

• 2100001086107794 is the needed wwn.
• The media-changer/robotics arm is located at lun 0.
• The two drives are located at luns 1 and 2.

Edit the "/usr/kernel/drv/lus.conf" file

sample output:

   name="lus" parent="fp" target=100 lun=0 fc-port-wwn="2100001086107794";

NOTE: Only the entry for lun 0 device exists.

This file needs to be edited to add entries for the other luns for the tape devices. All media-changer and tape devices need a single entry per device. In our example, the final entries related to this device will be:

   name="lus" parent="fp" target=100 lun=0 fc-port-wwn="2100001086107794";
name="lus" parent="fp" target=100 lun=1 fc-port-wwn="2100001086107794";
name="lus" parent="fp" target=100 lun=2 fc-port-wwn="2100001086107794";

Refer to the EBS Administration Guide for more details on lus.conf entries.

Unload the lus driver.

NOTE: Any EBS operation using or interacting with media devices will result in the lus driver being reloaded.

Determine the module ID:

   # modinfo | grep lus
268  13a9cb6   ed67 253   1  lus (Legato SCSI User Interface Tap)

Unload the driver:

   # modunload -i 268

Verify unload:

   # modinfo | grep lus

Reload the driver by running the EBS inquire command.

The media changer and the drives should appear now.

sample output:

   [email protected]:M4 DATA MagFile      3.07|Autochanger (Jukebox)
S/N: RBD12A0140
[email protected]:QUANTUM SDLT320      2E2E|Tape
S/N: PMC28Y0187
ATNN:QUANTUM SDLT320 MC28Y0187
IENN:00E09E600009DFAF
WWNN:500E09E00009DFAF
[email protected]:QUANTUM SDLT320      2E2E|Tape
S/N: RBD20Y0456
ATNN:QUANTUM SDLT320 BD20Y0456
IENN:00E09E60001141F5
WWNN:500E09E0001141F5

NOTE: The above steps will need to be repeated if lus_add_fp_devs is run again and the devices are no longer seen.

Configuring Veritas NetBackup

If you are using Veritas NetBackup 4.5 and later, you will need to follow the procedure outlined below. In a bridge environment, sg.build will not detect all the devices attached through a FC420 bridge. Some manual configuration of the sg driver will be needed.

Run "/usr/openv/volmgr/bin/sg.build" to detect devices as needed.

• This will create sg.conf and sg.links files.
• The sg.conf and sg.links files will need to be edited.

Run "cfgadm -la -o show_FCP_dev" to determine which devices are seen through the OS and their luns.

Sample output:

   Ap_Id                      Type         Receptacle   Occupant     Condition
c7                         fc-fabric    connected    configured   unknown
c7::2100001086107794,0     med-changer  connected    configured   unknown
c7::2100001086107794,1     tape         connected    configured   unknown
c7::2100001086107794,2     tape         connected    configured   unknown
c7::2100001086107794,3     ESI          connected    configured   unknown

Note that in our example:

• 2100001086107794 is the needed wwn.
• The media-changer/robotics arm is located at lun 0.
• The two drives are located at luns 1 and 2.

Edit the sg.conf file just created.

  Sample output:

   name="sg" parent="fp" target=0 lun=0 fc-port-wwn="2100001086107794";
name="sg" parent="fp" target=0 lun=1 fc-port-wwn="2100001086107794";

NOTE: The entry for lun 0, and possibly lun 1, device already exists.

There needs to be added entries for the other luns as well. All media-changer and tape devices will need their own entry. In our example, the final entries related to this device will be:

   name="sg" parent="fp" target=0 lun=0 fc-port-wwn="2100001086107794";
name="sg" parent="fp" target=0 lun=1 fc-port-wwn="2100001086107794";
name="sg" parent="fp" target=0 lun=2 fc-port-wwn="2100001086107794";

Refer to the Veritas NetBackup Admininistration Guide for more details on sg.conf entries.

Edit the sg.links file just created.

Sample output:

   type=ddi_pseudo;name=sg;addr=w2100001086107794,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w2100001086107794,1;       sg/c\N0t\A1l1

NOTE: lun 0 will already exist, and possibly entries for lun 1.

There needs to be added entries for the other luns as well. All media-changer and tape devices will need their own entry. In our example, the final entries related to this device will be:

   type=ddi_pseudo;name=sg;addr=w2100001086107794,0;       sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w2100001086107794,1;       sg/c\N0t\A1l1
type=ddi_pseudo;name=sg;addr=w2100001086107794,2;       sg/c\N0t\A1l2

NOTE: The lun is specified in the addr as well as the sg path.

NOTE: Refer to the Veritas NetBackup Administration Guide for more details on sg.links entries.

Continue the configuration by using the sg.install link as specified in the Veritas NetBackup Admin Guide.

Verify that sg driver is attached to the devices by running sgscan

The media changer and the drives should appear now.

Sample output:

   /dev/sg/c0tw2100001086107794l0: Changer: "M4 DATA MagFile"
/dev/sg/c0tw2100001086107794l1: Tape (/dev/rmt/3): "QUANTUM SDLT320"
/dev/sg/c0tw2100001086107794l2: Tape (/dev/rmt/2): "QUANTUM SDLT320" 

NOTE: These steps will need to be repeated if sg.build is run again and
the devices are no longer seen.

This solution has no attachment