cancel
Showing results for 
Search instead for 
Did you mean: 

sg.build questions

Steve_Patregnan
Level 2
I am running netbackup 6.0 using and L700E library,  with 8 SDLT tape drives connected via scsi cards to the netbackup server.
I have a question or two  regarding the sg.build command.

Last Fall we particapted in DR (disaster recovery exercise) at our disater recovery site.
The setup at the DR site is suposed to be identical to our production setup as far as how the equipment is connected.
But when I arrived there I found the library was connected via a fiber channel and after doing my normal setup commands I was only able to see 5 drives.

At the DR site I use the same command to build my drivers as I do when I am in the office
usr/openv/volmgr/bin/sg.build all -mt 15 -ml 1
 
After doing that at the DR site I only see 4 tape drives.

Can anyone help me with my sg.build command so that I can see all 8 tape drives?  
Should it be something like this,
usr/openv/volmgr/bin/sg.build all -mt 15 -ml 2

thanks,
1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified
First of all ensure that the O/S can see the devices in /dev/rmt.
Use a long listing of /dev/rmt to dermine target and lun numbers.
Use this info with -mt and -ml.
See TechNote: http://seer.entsupport.symantec.com/docs/236104.htm


View solution in original post

2 REPLIES 2

Marianne
Level 6
Partner    VIP    Accredited Certified
First of all ensure that the O/S can see the devices in /dev/rmt.
Use a long listing of /dev/rmt to dermine target and lun numbers.
Use this info with -mt and -ml.
See TechNote: http://seer.entsupport.symantec.com/docs/236104.htm


rjrumfelt
Level 6
We have 40 virtual tape drives and several physical scsi drives.  We have our lpfc.conf file set up correctly.  When we run sg.build, the resulting sg.conf file only show's scsi entries.  Ex:

name="sg" class="scsi" target=60 lun=27

We need the sg.conf file entries to read like:

name="sg" parent="lpfc" target=60 lun=27

Any ideas?


***EDIT***

We were able to get it resolved - we were not setting the correct number of targets.