Understanding the SCSI Passthru Drivers
NetBackup Media Manager provides its own driver for communicating with SCSI-controlled robotic peripherals.
This driver is called the SCSA (Generic SCSI passthru driver), also referred to as the sg driver.
To manage the sg driver
Perform the following steps as the root user.
1. Determine if an sg driver is loaded by using the following command:
/usr/sbin/modinfo | grep sg
141 fc580000 2d8c 116 1 sg (SCSA Generic Revision: 3.4d)
153 fc7fa000 1684 49 1 msgsys (System V message facility)
2. Remove the existing driver:
/usr/sbin/rem_drv sg
/usr/bin/rm -f /kernel/drv/sg.conf
Install SG Driver
To install the driver run the following command:
/usr/openv/volmgr/bin/driver/sg.install
Once the driver has been installed, it is not necessary to reboot the system or run the sg.install command during or after each system boot.
Configuring SG and ST Drivers
This procedure contains instructions for configuring the sg driver for SCSI targets 0 thru 6 and 8 thru 15 for fast or wide adapter cards.
In this procedure, you execute sg.build to add these targets to the st.conf, sg.conf and sg.links files. Adjust the -mt and -ml parameters to create the range of targets and LUNs required by your configuration.
To configure drivers
Execute the sg.build script to add target IDs 0-6, 8-15, and LUNs 0-1 to the following files:
/usr/openv/volmgr/bin/driver/st.conf
/usr/openv/volmgr/bin/driver/sg.conf
/usr/openv/volmgr/bin/driver/sg.links
/usr/openv/volmgr/bin/sg.build all -mt 15 -ml 1
The -mt 15 parameter specifies themaximum target ID that is in use on any SCSI bus (or bound to a fibre channel device).The -ml 1 parameter specifies the maximum target LUN that is in use on any SCSI bus (or by a fibre channel device).
The file /usr/openv/volmgr/bin/driver/st.conf is used to replace the following seven entries in the /kernel/drv/st.conf file:
name=”st” class=”scsi” target=0 lun=0;
name=”st” class=”scsi” target=1 lun=0;
name=”st” class=”scsi” target=2 lun=0;
name=”st” class=”scsi” target=3 lun=0;
name=”st” class=”scsi” target=4 lun=0;
name=”st” class=”scsi” target=5 lun=0;
name=”st” class=”scsi” target=6 lun=0;
Edit the /kernel/drv/st.conf file.
Place a # in column one of each line of the seven default entries.
The temporary file ./st.conf contains the entries that you need to insert into /kernel/drv/st.conf.
Reboot the system with the reconfigure option (boot -r or reboot — -r).
Verify that the system created device nodes for all the tape devices using the following command: ls -l /dev/rmt/*cbn
Install the new sg driver configuration.
/usr/bin/rm -f /kernel/drv/sg.conf
/usr/openv/volmgr/bin/driver/sg.install
when run sg install command sg.conf will copy to /kernel/drv/sg.conf
and sg.links will copy to /etc/devlink.tab
Verify that the sg driver found all the robots, tape drives,
The script /usr/openv/volmgr/bin/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.An example of the additional entries in /usr/openv/volmgr/bin/driver/sg.conf
follows:
name=”sg” parent=”fp” target=0 lun=0 fc-port- wwn=”22000090a50001c8″;name=”sg” parent=”fp” target=0 lun=1 fc-port-wwn=”22000090a50001c8″;
An example of the additional entries in /usr/openv/volmgr/bin/driver/sg.links
follows:
type=ddi_pseudo;name=sg;addr=w22000090a50001c8,0; sg/c\N0t\A1l0type=ddi_pseudo;name=sg;addr=w22000090a50001c8,1; sg/c\N0t\A1l1
Preventing Possible System Problems
VERITAS recommends adding the following forceload statements to the /etc/system file. These statements prevent the st and sg drivers from being unloaded from memory
forceload: drv/st
forceload: drv/sg
Other statements may be necessary for various fibre channel drivers, such as the following example for JNI drivers. This statement prevents the named driver from being unloaded from memory.
forceload: drv/fcaw
SSO Configurations With More Than 16 Tape Drives
When the number of tape devices that are configured approaches 16, changes in tape device status may not be visible to all media servers in a Shared Storage Option (SSO) configuration. This is because the default maximum size of IPC message queues may not be large enough.
VERITAS recommends adding the following statements to the /etc/system file. These statements increase the maximum number of messages that can be created, and the number of bytes per queue. A reboot is necessary for the changes to take effect.
set msgsys:msginfo_msgtql=512
set msgsys:msginfo_msgmnb=65536
Hi,
I am getting this error messages in the server, can u sugest me what this problem, checked all the tape drive is working fine
unix: st46 at qus1: target 4 lun 0
unix: st46 is /pci@1e,600000/pci@3/scsi@5/st@4,0
unix: pseudo-device: devinfo0
unix: devinfo0 is /pseudo/devinfo@0
unix: VERITAS SCSA Generic Revision: 3.4d
Thanks and Regards,
Pratap
Hey Aziz,
Please assist
I created devices for 2 additional new VTL drives yesterday and they can now be seen at the OS level.
I reconfigured Storage Devices in Netbackup thereafter and got 2 Drive Paths
/dev/rmt/11cbn
/dev/rmt/2cbn
sharing the same Drive name – HP.Ultrium3-SCSI.009. This is wrong.
It was the 2cbn that had the Drive name before, so I wonder why 11cbn which is one of the 2 new devices should share the Drive name with 2cbn.
I would need to separate this to their Individual Drive Names and will be happy if you could assist.
Thanks
Dennis
Hi Dennis,
U can check drive & robot path from Veritas, goto “/usr/openv/volmgr/bin/” then run “tpconfig -l”.
Or from Veritas GUI, click “Media and Device Management”>>Device> click Drives tab. See the “drive path”, make sure the drive path is correct.
Please see also the output from “./scan” command, run it from “/usr/openv/volmgr/bin/”
thx
To Pratap,
I think that’s not an error, Just kernel informational messages when your server is building the devinfo pseudo device driver, look the the kern.info part of the message. Correct me if I wrong..
hi Aziz,
I already configure tape drive to one of the system.
SunOS S55KJA11 5.9 Generic_118558-24 sun4u sparc SUNW,Sun-Fire-V440. We can see the tape drive from #cfgadm -al but when we try to scan the tape from veritas command. The tape cannot see. I need your advice. Thanks
Hii Hilmi,
It seem that you need to reconfigure the ‘st.conf’. Try to run ‘sg.build’ command from ‘/usr/openv/volmgr/bin’:
Prefix: #sg.build all -mt max_target -ml max_lun
Exp:
#cd /usr/openv/volmgr/bin/
#./sg.build all -mt 3 -ml 4
‘sg.build’ will update st.conf,sg.conf, and sg.links, and generates SCSI Target IDs with multiple LUNs.
Then run ‘./scan’ again..
Hi
I have two solaris servers which are to be configured as SAN media servers as they are going to backp huge volume. I have one drive and want both the servers to use the same drive. SSO option cannot be used in our environment. Could you please suggest how this can be done
Govind,
You have to buy SSO License..
As the function of SSO is “to allow individual tape drives (stand-alone or in a robotic library) to be dynamically shared between multiple NetBackup media servers or SAN media servers. and then Each media server can access any of the shared drives as needed and each server ”owns” the drives it has active. The shared drives are automatically allocated and deallocated as backup and restore operations dictate”.
In fact I never try ur scenario, but based on my experience it’s impossible sharing drive without SSO License.
Hi i have solaris 9 netbackup 6 media server with two lp11000 emulex controllers and storagetek L1400 LT03 tape library. I can see all drives from master server with sgscan but i cant see it from media server. On media server i can see devices in /dev/rmt and mt command shows info when i load tape in library.
Do i need to do any special configuration since it is not creating link in /dev/sg ?
Shrikant,
Could you see your drives from ‘./scan’ command?
cd /usr/openv/volmgr/bin/
./scan
If you couldn’t, Try to run ’sg.build’ command from ‘/usr/openv/volmgr/bin’:
Prefix: #sg.build all -mt max_target -ml max_lun
Exp:
#cd /usr/openv/volmgr/bin/
#./sg.build all -mt 3 -ml 4
Then run ‘./scan’ again.
For further reference, Here the Netbackup Media Manager Device Configuration Guide:
ftp://docs-pdf.sun.com/875-3543-10/875-3543-10.pdf
1. Execute the sg.build script to add target IDs 0-6, 8-15, and LUNs 0-1 to the following files:
/usr/openv/volmgr/bin/driver/st.conf
/usr/openv/volmgr/bin/driver/sg.conf
/usr/openv/volmgr/bin/driver/sg.links
cd /usr/openv/volmgr/bin/driver
/usr/openv/volmgr/bin/sg.build all -mt 15 -ml 1
The -mt 15 parameter specifies the maximum target ID that is in use on any SCSI bus (or bound to a fibre channel device).
The -ml 1 parameter specifies the maximum target LUN that is in use on any SCSI bus (or by a fibre channel device).
2. The file /usr/openv/volmgr/bin/driver/st.conf is used to replace the following seven entries in the /kernel/drv/st.conf file:
name=”st” class=”scsi” target=0 lun=0;
name=”st” class=”scsi” target=1 lun=0;
name=”st” class=”scsi” target=2 lun=0;
name=”st” class=”scsi” target=3 lun=0;
name=”st” class=”scsi” target=4 lun=0;
name=”st” class=”scsi” target=5 lun=0;
name=”st” class=”scsi” target=6 lun=0;
a) Make a copy of the /kernel/drv/st.conf file.
b) Edit the /kernel/drv/st.conf file. Place a # in column one of each line of the seven default entries. The temporary file ./st.conf contains the entries that you need to insert into /kernel/drv/st.conf.
c) Reboot the system with the reconfigure option (boot -ror reboot — -r).
d) Verify that the system created device nodes for all the tape devices using the following command: ls -l /dev/rmt/*cbn
3. Install the new sg driver configuration.
/usr/bin/rm -f /kernel/drv/sg.conf
/usr/openv/volmgr/bin/driver/sg.install
Hi,
Recently I got new tape drives for to add in the tape library. The library already has 2 drives and taking backups very fine. SO how to configure these 2 new drives in solaris 9 and Veritas netbackup6. Can you please guide me on how to do this from scartch.
Thnak you,
Bhagavan
I’m greutfal you made the post. It’s cleared the air for me.
@Bhagavan
1. You have to make sure, it already detected by OS:
#cd /dev/rmt/
#ls
{here you will see “0cbn,1cbn.. ect”, each *cbn is the label information for each drive}
#cd /usr/openv/volmgr/bin/
#./scan
{the output look like this:
bash-2.05# ./scan
************************************************************
*********************** SDT_TAPE ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
————————————————————
Device Name : “/dev/rmt/0cbn”
Passthru Name: “/dev/sg/c1t0l0”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : “SEAGATE ULTRIUM06242-XXXx”
Vendor ID : “SEAGATE ”
Product ID : “ULTRIUM06242-XXX”
Product Rev: “1619”
Serial Number: “HL00BKN”
WWN : “SEAGATE ULTRIUM06242-XXX ”
WWN Id Type : 1
Device Identifier: “SEAGATE ULTRIUM06242-XXX”
Device Type : SDT_TAPE
NetBackup Drive Type: 3
Removable : Yes
Device Supports: SCSI-3
Flags : 0x4
Reason: 0x0
————————————————————
Device Name : “/dev/rmt/1cbn”
Passthru Name: “/dev/sg/c1t1l0”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : “QUANTUM SDLT320 5E5E”
Vendor ID : “QUANTUM ”
Product ID : “SDLT320 ”
Product Rev: “5E5E”
Serial Number: “RBE16Y1120”
WWN : “QUANTUM SDLT320 “xxxxxxxxxxx””
WWN Id Type : 1
Device Identifier: “QUANTUM SDLT320 “xxxxxxxxxxx””
Device Type : SDT_TAPE
NetBackup Drive Type: 11
Removable : Yes
Device Supports: SCSI-2
Flags : 0x4
Reason: 0x0
————————————————————
Device Name : “/dev/sg/c1t6l0”
Passthru Name: “/dev/sg/c1t6l0”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : “STK L40 0215”
Vendor ID : “STK ”
Product ID : “L40 ”
Product Rev: “0215”
Serial Number: “xxxxxxxxxxx”
WWN : “”
WWN Id Type : 0
Device Identifier: “”
Device Type : SDT_CHANGER
NetBackup Robot Type: 8
Removable : Yes
Device Supports: SCSI-3
Number of Drives : 2
Number of Slots : 20
Number of Media Access Ports: 2
Drive 1 Serial Number : “HL00BKN”
Drive 2 Serial Number : “xxxxxxxxxxx”
Flags : 0x0
Reason: 0x0
bash-2.05# pwd
/usr/openv/volmgr/bin
bash-2.05#
2. Then for easy step, just run Netbackup Configuration Wizard
-from Netbackup main display, click your master server hostname, >> on the right panel click “Configure Storage Device”.
-Follow the screen >>Next>>Next>>Finish.
-Restart Netbackup services.
Hi Aziz,
Thank you for your reply.
The following is the status when I done scan and when I try to configure from Configuration wizard it has detected 4 tape drives but it is shoing 2 drives are not usable which I added recently. And through scan command it is not showing the name of the drive for these 2 new drives.The following is the output of the command.
So do I need to build the kernel to recognize these new drives as you mentioned in your document.
Device Name : “/dev/rmt/1cbn”
Passthru Name: “/dev/sg/c1t2l0”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : “IBM ULTRIUM-TD3 64D0”
Vendor ID : “IBM ”
Product ID : “ULTRIUM-TD3 ”
Product Rev: “64D0”
Serial Number: “1210047825”
WWN : “”
WWN Id Type : 0
Device Identifier: “IBM ULTRIUM-TD3 1210047825”
Device Type : SDT_TAPE
NetBackup Drive Type: 16
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
————————————————————
Device Name : “-”
Passthru Name: “/dev/sg/c1t3l0”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : “IBM ULTRIUM-TD3 64D0”
Vendor ID : “IBM ”
Product ID : “ULTRIUM-TD3 ”
Product Rev: “64D0”
Serial Number: “1210047802”
WWN : “”
WWN Id Type : 0
Device Identifier: “IBM ULTRIUM-TD3 1210047802”
Device Type : SDT_TAPE
NetBackup Drive Type: 16
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x10000
————————————————————
Device Name : “-”
Passthru Name: “/dev/sg/c1t4l0”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : “IBM ULTRIUM-TD3 64D0”
Vendor ID : “IBM ”
Product ID : “ULTRIUM-TD3 ”
Product Rev: “64D0”
Serial Number: “1210048564”
WWN : “”
WWN Id Type : 0
Device Identifier: “IBM ULTRIUM-TD3 1210048564”
Device Type : SDT_TAPE
NetBackup Drive Type: 16
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x10000
From your ‘./scan’ output, it seem that you only have = 1cbn on your “/dev/rmt” directory.
try to remove all file on “/dev/rmt”:
#cd /dev/rmt
#rm *
run “devfsadm” command
#devfsadm
run ./scan again, show me the output.
and also list file on your “/dev/rmt” directory.
If your ‘/dev/rmt’ directory is empty after running ‘devfsadm’, I think you hv to reconfigure all device from the beginning.
For further reference, read the VERITAS NetBackup 6.0 Media Manager Device Configuration Guide, for UNIX, Windows, and Linux.
Salam Aziz,
Terima kasih di atas bimbingan bapak.. it’s work..
One question,
Prefix: #sg.build all -mt max_target -ml max_lun
what is the max target and max lun.. what happen if value of max_target and max_lun is 50.. saya kurang mengerti tentang ini.. anyway I’m from malaysia.. 😉
@hilmi
/usr/openv/volmgr/bin/sg.build all -mt 15 -ml 1
so,
maximum target ID : 15
maximum target LUN : 1
target IDs 0-6, 8-15, and LUNs 0-1
just follow the instruction, range LUNs only between 0 -1
Oya, Salam balik jg..
hi aziz
this is samir here
i have configure netbackup 6.0 mp4
from the os level drives and robot got detected but in veritas robot is active and drives are unconfigured
pls help
Gevonden: het heet ‘the big bang theory’. het zijn geen aspergers, maar ze zijn sociaal niet zo handig en ze zijn ongelooflijk slim.het is dus niet dat ze aspergers spelen, maar blijkbaar zijn er aspergers die zich herkennen en het geweldig vinden. (de jongen over wie ik het had is uitzonderlijk goed in begrijpen van humor,wat uniek is voor as8&sgerr)e#p230; oja, da’s weer zo’n stigma.
Aziz, I need ur thoughts.
I’m upgrading site with 4tape(9840B) drives,L700 and LTD robot currently in production.
This will be decommissiend and I will replace it with Iscalar IBM ATL and 6 LTO tape drives.
Im trying to come up with safe procedure.
1- backup the catalog
2- Install Netbackup 6.5 into new master and media servers
3- Restore /netbackup/db, volmgr/db , and catalog to the new master server.
4- Configure the robot
5- Configure LTO tape drive
6- Map aone cleint to test.
Do you have clear steps to configure the tape drives that I can follow?
Thx
Ashco
@samir,
you need only 1 step again; run the Veritas Device Configuration Wizard. from Veritas GUI, click ‘Media and Device Management’, then select ‘Configure Storage Devices’, follow the screen wizard.You will see your robot & drives there, select/check ur robot & drives >>press next>>finish, then restart NBU services.
@Ashco,
for decommission NBU, you can see my other post:
https://saifulaziz.wordpress.com/2007/07/02/decommision-media-server/
other step to configure device on NBU 6.5:
Veritas NetBackup ™ 6.5 Device Configuration Guide for UNIX, Linux, and Windows
Aziz,
I have new Iscalar with 6 drives, Solaris Master. I can see the drives LTO-4 Ok, but when I try to configure the Robot >tpconfig .or If I do sgscan I do not see the Robot?
In the cfgadm I get this error
s44ab002:zahrka0m:/usr/openv/volmgr/bin> cfgadm -c configure c3::500308c001f3c801
cfgadm: Library error: failed to create device node: 500308c001f3c801: Invalid argument
What do you suggest?
In addition info.
c3::500308c001f3c801 connected configured unknown
unavailable array-ctrl n /devices/pci@1d,700000/SUNW,qlc@2/fp@0,0:fc::500308c001f3c801
try:
#cfgadm -al
or
#cfgadm -o force_update -c configure
check tape device on ‘dev/rmt/’. 0cbn, 1cbn etc…
check each drives status, exp:
$ mt -f /dev/rmt/0cbn status
run tpconfig/sgscan later, you will got nothing until all devices detected by your OS..
Hello Aziz, I have a particular issue. I am tryng to setup a Netbackup server on Solaris x86, with one QLA2340 and two SUN HBAs. I could not get both Sun HBAs online simultaneously and Sun has confirmed that it is a known issue,
see message below:
————————————————-
Escalation engineer has determined this issue is due to current version
of Leadville san qlogic drivers
not supporting the point to point topology
The T10000 FC 4GB (Titanium) tape drives utilize a Qlogic In-line Credit
Extender (ICE) chip that
gives it the ability to support up to 600 Buffer to Buffer credits to
support long distance up to 100km.
However it does NOT support Loop mode (NL-to-NL), it requires either the
fabric (N-to-F) or
point to point (N-to-N) topology.
Leadville doesn’t not support the point to point topology, hence today,
the T10000 FC 4GB
cannot be in a direct attach configuration with a Solaris server.
Later versions of Leadville san qlogic drivers will have it but for now
work around solution
is to use a FCP switch in between
To summarize what Fibre Channel topologies that the T10 drives support are listed below:
T10k-2gb FCP (SCSI) protocol
1. N-to-N port connections, i.e. Direct connect, HBA N-port directly connected to T10k N-port.
2. N-to-F port connections, i.e. Switch connected, Switch F-port directly connected to T10k N-port.
3. NL-to-NL port connections, i.e. Private Loop, HBA NL-port to T10k NL-port via Loop port Hub or not.
4. NL-to-FL port connections, i.e. Public Loop, Switch FL-port to T10k NL-port via Loop port Hub or not.
T10k-4gb FCP (SCSI) protocol
1. N-to-N port connections, i.e. Direct connect, HBA N-port directly connected to T10k N-port.
2. N-to-F port connections, i.e. Switch connected, Switch F-port directly connected to T10k N-port.
———————————————-
Now my issue is that I have a Brocade switch and connected the HBAs to the root and both drives. I do not know how to proceed from there as it seems that all teh devices are geeting duplicated, ie same deice showing entry as Tape and Medium Changer
CMD >luxadm -e port
/devices/pci@0,0/pci8086,2601@1/pci8086,32a@0,2/pci1077,100@1/fp@0,0:devctl CONNECTED
/devices/pci@0,0/pci8086,2602@2/pci1077,142@0/fp@0,0:devctl CONNECTED
/devices/pci@0,0/pci8086,2605@5/pci1077,142@0/fp@0,0:devctl CONNECTED
CMD >luxadm probe
Found Fibre Channel device(s):
Node WWN:500104f0005f51e6 Device Type:Medium changer device
Logical Path:/devices/pci@0,0/pci8086,2601@1/pci8086,32a@0,2/pci1077,100@1/fp@0,0/medium-changer@w500104f0005f51e7,0
Node WWN:500104f0005f51fb Device Type:Tape device
Logical Path:/dev/rmt/0n
Node WWN:500104f0005f51e6 Device Type:Medium changer device
Logical Path:/devices/pci@0,0/pci8086,2602@2/pci1077,142@0/fp@0,0/medium-changer@w500104f0005f51e7,0
Node WWN:500104f0005f51fb Device Type:Tape device
Logical Path:/dev/rmt/1n
Node WWN:500104f0005f51e6 Device Type:Medium changer device
Logical Path:/devices/pci@0,0/pci8086,2605@5/pci1077,142@0/fp@0,0/medium-changer@w500104f0005f51e7,0
Node WWN:500104f0005f51fb Device Type:Tape device
Logical Path:/dev/rmt/2n
CMD >cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c1 fc-fabric connected configured unknown
c1::500104f0005f51e7 med-changer connected configured unknown
c1::500104f0005f51fd tape connected configured unknown
c2 scsi-bus connected configured unknown
c2::dsk/c2t0d0 disk connected configured unknown
c2::dsk/c2t1d0 disk connected configured unknown
c2::dsk/c2t2d0 disk connected configured unknown
c2::sg/c0t0l0 unknown connected configured unknown
c2::sg/c0t1l0 unknown connected configured unknown
c2::sg/c0t2l0 unknown connected configured unknown
c4 fc-fabric connected configured unknown
c4::500104f0005f51e7 med-changer connected configured unknown
c4::500104f0005f51fd tape connected configured unknown
c6 fc-fabric connected configured unknown
c6::500104f0005f51e7 med-changer connected configured unknown
c6::500104f0005f51fd tape connected configured unknown
Can you help me please
Thanks
As far as I know, this is an old issue with Sun-branded Emulex HBA. My friend Buntaran posted here:
http://unix.ittoolbox.com/groups/technical-functional/solaris-l/hba-sunemulex-problem-connectivity-with-drive-1481221
but no answer from ittoolbox expert ;-).
if you read carefully the installation guide, u will found this line:
—————————-
leadville considerations,
beginning with solaris 10 update 1, the emulex leadville FCA driver is bundled with the operating system. when the lpfc
driver is installed on solaris 10 update 1 (or later), the lpfc driver will not claim most of the HBAs, since they already
claimed by the emlxs driver. to change the driver HBA bindings, run the emlxdrv utility. this utility enables you choose
which driver (lpfc or emlxs) controls the Emulex HBAs in the system. this utility is available on the Emulex Website. the
emlxdrv utility is in the emlxu utility package.
more here:
—————-
Our L700 connected with Solaris 8, use leadville driver (SUNWemlxs). SUN suggest to upgrade the OS to Solaris 10. We still waiting our customer to upgrade their server, but for now If the problem occurs again, we just powered off all drives then powered on 1st drive, wait untill up/approx 1-3 minutes then continue to next drive..and problem solved he2..
Or you can also reinstall HBA driver with lpfc driver, we hv tested it on Solaris 9 and its work.
Good luck!
Hello Aziz,
In my case, The HBA are not Emulex but 375-3355-02 (Sun OEM HBA – equivalent to the QLE2462 as per Sun). Also, they are recognised by the qlc driver.
Any other suggestions please, especially with regards to the same device being detected more than one?
Thanks again for your support.
Owhh.. I see.
Sorry I dont hv any experience with thats HBA.
But, sometimes, If I stuck while troubleshooting, I remove all in “/dev/rmt/” directory and then remove existing driver:
/usr/sbin/rem_drv sg
/usr/bin/rm -f /kernel/drv/sg.conf
then run ‘devfsadm’ and ‘cfgadm -al’ then ‘boot -r”
CMIIW..
Pak Aziz,
referring to the following:
Naveen
April 29, 2008 at 3:28 pm
Hello Aziz, I have a particular issue. I am tryng to setup a Netbackup server on Solaris x86,…..
I don’t think NetBackup can be setup on Solaris for x86. As a client yes, but not as master & media server. Anyone had done this ?
Thanks.
@Kurniawan
I think you are right, from NetBackup Version 6 OS Compatibility Matrix; Netbackup only support as a Client on Solaris x86..
How can I install Cluster Server with Solaris 10?
Need your advice in this regards.
For VCS (Veritas Cluster Server) manual guide and technote; go to here :
http://seer.support.veritas.com/docs/284550.htm
and here:
http://seer.support.veritas.com/docs/275725.htm
Hello Sir
I have NBU 6.0 on Solaris & need to upgrade it to 6.5 ,but 6.5 I will install on different machine & migrate/transfer catalog from 6.0 to 6.5.
please help me with detailed steps & will there be any problems.
Thanks
Subhash
@subhash
For details on upgrading from NetBackup 6.0 to 6.5, see Chapter 4: Upgrading NetBackup in the NetBackup 6.5 Installation Guides. here the link:
Veritas NetBackup ™ 6.5 Installation Guide for Windows:
Veritas NetBackup ™ 6.5 Installation Guide for UNIX and Linux:
Other Netbackup 6.5 Manuals and Documentation can be found here:
http://www.symantec.com/business/support/documentation.jsp?language=english&view=manuals&pid=15143&version=NBUESVRPVER24910
Hi,
I have big issue with tape performance:
I’m trying to change block size for IBM tapes LTO3 on Solaris 10. HBA is Qlogic 2310f Sun OEM with QLC drivers. Normally is basic operation but this one case is little different. On Cisco SAN director I have a couple VSAN’s. My backup VSAN have 040 domainID and FCID start from 0x400xxx. I have very high target ID 4195560 for the tapes.
When I changing block size parameters in st.conf or IBMtape.conf nothing happens with performance of my backup. if I trying to write by DD to a tape with block size parameter (bs=2048 for eg.) then speed of my backup up to 30 times.
Is it any chance to change this very high target ID without change the DomainID on Cisco director?
best regards
HI Brunoc,
You should be able to set the block size to be used for backups within the backup product.
For example on Netbackup I would create the following touch files on the media server:
/usr/openv/netbackup/db/config/NUMBER_DATA_BUFFERS
/usr/openv/netbackup/db/config/SIZE_DATA_BUFFERS
For LTO3 I would recommend setting the size to 262144 (just insert 262144 into the “size” file) and the number to 32 (just insert 32 into the “number” file).
Hope this helps.
i want to configure SAN media server on netbackup 6.5
please advice with the procedure.
thanks
@subhash
you can read all the Veritas NetBackup ™ 6.5 Manuals here:
http://seer.entsupport.symantec.com/docs/290282.htm
Hi Aziz,
udah jago nih kelihatannya, hehehehe
inget gw dulu waktu lu baru masuk mit,……
salam buat my old fren Mr Zak ya
—
Wah, pa kabarnya mas Reza?, he2 dlu masih lugu bget ya;0). yah blum jago lah..klo udah jago ntar nyusul and ketemu di Singapore deh hii..
Hi can u send me how to install and configure veritas netbackup sostware in solaris
Aziz, We have a NetApp NAS filer that we trying to backup its disk to tape, Netbackup 6.5 , we created the NDMP host and put the credential but when try to verify the ndmp host connectivity we get the below information??
any Idea??
usr/openv/volmgr/bin> set_ndmp_attr -verify dha00730-nasp42
Connecting to host “dha00730-nasp42” as user “netbackup”…
Waiting for connect notification message…
Opening session–attempting with NDMP protocol version 4…
Opening session–successful with NDMP protocol version 4
host supports MD5 authentication
Getting MD5 challenge from host…
Logging in using MD5 method…
ndmp_connect_client_auth failed
set_ndmp_attr: host “dha00730-nasp42” failed
NDMP failed to verify host
Hi Aziz,
Firstly, Thanks for sharing your knowledge on various issues in your Knowledge base Blog.
I’m just a toddler in the area of Veritas netbackup and Unix.
I have a scenario at my work place which goes like this.
We have been having issues with our Vault job for past few months, which doesn’t generate a re-call list and causing a over head for us to expire the tapes manually. Even while manually expiring a tape by force, using a unix script :
part of the script added below:
********************************************
#!/bin/sh
for i in `cat /tmp/input.txt`
do
/opt/openv/netbackup/bin/admincmd/bpexpdate -m $i -d 0 -force
echo ” $i has been expired” >> /tmp/expired_tapes_.txt
echo “” >> /tmp/expired_tapes_.txt
done
more /tmp/expired_tapes_.txt |mailx -s
********************************************
It takes around 1 .5 to 2 hrs to expire a single tape, which really costs a great deal of time in say expiring 1000 tapes that we have.
Any inputs from you on resolving this will be much appreciated. Thanks in advance.
Abhi.
zonning the tape drives with the san switch and HBA’ can you please explain in detail ,
Appreciate it
Thanks
Nick
Guys,
iam getting following error while configuring net-backup client on solaris os
# ./bpclntcmd -ip 10.0.4.67
checkhaddr: host : scbackup-10: scbackup-10.isys.intraware.com at 10.0.4.67 (0xa000443)
checkhaddr: aliases: scbackup-10
Hi,
SOrry for the mistake , I need to configure netbackup client on solaris os..
following error.
# ./bpclntcmd -ip 10.0.4.67
checkhaddr: host : scbackup-10: scbackup-10.isys.intraware.com at 10.0.4.67 (0xa000443)
checkhaddr: aliases: scbackup-10
Assalam Aziz,
My env. has 1 Master on Sol 10 with 6.5.5 and 4 media server with 24 drives. I am adding 2 more to one of my media server. I am getting the following output from tpconfig.
root@P100XMED04 # /opt/openv/volmgr/bin/tpconfig -l
Device Robot Drive Robot Drive Device Second
Type Num Index Type DrNum Status Comment Name Path Device Path
robot 0 – TLD – – – – MASTERBKP
drive – 0 hcart3 14 UP – IBM.ULTRIUM-TKP-Drive14 /dev/rmt/0cbn
drive – 1 hcart3 13 UP – IBM.ULTRIUM-TKP-Drive13 /dev/rmt/1cbn
drive – 2 hcart3 16 UP – IBM.ULTRIUM-TKP-Drive16 /dev/rmt/2cbn
drive – 3 hcart3 15 UP – IBM.ULTRIUM-TKP-Drive15 /dev/rmt/3cbn
drive – 4 hcart3 17 UP – IBM.ULTRIUM-TKP-Drive17 /dev/rmt/6cbn
drive – 5 hcart3 18 UP – IBM.ULTRIUM-TKP-Drive18 /dev/rmt/7cbn
———————————————-
Out of scan command.
root@P100XMED04 # /opt/openv/volmgr/bin/scan -tape
************************************************************
*********************** SDT_TAPE ************************
************************************************************
————————————————————
Device Name : “/dev/rmt/0cbn”
Passthru Name: “/dev/sg/c0t0l0”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : “HP Ultrium 3-SCSI M63S”
Vendor ID : “HP ”
Product ID : “Ultrium 3-SCSI ”
Product Rev: “M63S”
Serial Number: “HU10737URK”
WWN : “”
WWN Id Type : 0
Device Identifier: “”
Device Type : SDT_TAPE
NetBackup Drive Type: 16
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
————————————————————
Device Name : “/dev/rmt/1cbn”
Passthru Name: “/dev/sg/c1t0l0”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : “HP Ultrium 3-SCSI M63S”
Vendor ID : “HP ”
Product ID : “Ultrium 3-SCSI ”
Product Rev: “M63S”
Serial Number: “HU10737WLT”
WWN : “”
WWN Id Type : 0
Device Identifier: “”
Device Type : SDT_TAPE
NetBackup Drive Type: 16
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
————————————————————
Device Name : “/dev/rmt/2cbn”
Passthru Name: “/dev/sg/c2t0l0”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : “HP Ultrium 3-SCSI M63S”
Vendor ID : “HP ”
Product ID : “Ultrium 3-SCSI ”
Product Rev: “M63S”
Serial Number: “HU10737UN4”
WWN : “”
WWN Id Type : 0
Device Identifier: “”
Device Type : SDT_TAPE
NetBackup Drive Type: 16
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
————————————————————
Device Name : “/dev/rmt/3cbn”
Passthru Name: “/dev/sg/c3t0l0”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : “HP Ultrium 3-SCSI M63S”
Vendor ID : “HP ”
Product ID : “Ultrium 3-SCSI ”
Product Rev: “M63S”
Serial Number: “HU10737WHN”
WWN : “”
WWN Id Type : 0
Device Identifier: “”
Device Type : SDT_TAPE
NetBackup Drive Type: 16
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
————————————————————
Device Name : “/dev/rmt/6cbn”
Passthru Name: “/dev/sg/c10t0l0”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : “IBM ULTRIUM-TD3 54K1”
Vendor ID : “IBM ”
Product ID : “ULTRIUM-TD3 ”
Product Rev: “54K1”
Serial Number: “1210059897”
WWN : “”
WWN Id Type : 0
Device Identifier: “IBM ULTRIUM-TD3 1210059897”
Device Type : SDT_TAPE
NetBackup Drive Type: 16
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
————————————————————
Device Name : “/dev/rmt/7cbn”
Passthru Name: “/dev/sg/c11t0l0”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : “IBM ULTRIUM-TD3 54K1”
Vendor ID : “IBM ”
Product ID : “ULTRIUM-TD3 ”
Product Rev: “54K1”
Serial Number: “1210060164”
WWN : “”
WWN Id Type : 0
Device Identifier: “IBM ULTRIUM-TD3 1210060164”
Device Type : SDT_TAPE
NetBackup Drive Type: 16
Removable : Yes
Device Supports: SCSI-3
Flags : 0x0
Reason: 0x0
———————————————-
But when i am going through Device Configuration through GUI it shows me 6 tape drive detected and after that screen it doesn’t shows me the actual drives in the last screen after which we need to commit the configuration.
Can u help..
Pingback: Tape Drive not recognize
Pak Aziz,
Kalau di Veritas Netbackup ada error 800 kira-kira apa ya masalahnya? At least bagaimana melakukan pengecekannya.
Thanks alot
Bernard.
Hello Aziz ,
, in my environment i have to add 3 additional tape drives which are lto5 , do i have to follow the same procedure as the above ?
Hi Aziz,
I have 4 LTO4 drives in the library. How can I reserve 2 drives for backup and 2 for duplication jobs.
Thanks
Pingback: How to Configure SL24 / SL48 with Netbackup « AZIZ's BLOG
Cazare Mamaia Apartament
This piece of writing gives clear idea for
the new people of blogging, that genuinely how to do running a blog.
mantap gan perkembangan teknologi sekarang, , klw kita gak ikuti bisa ketinggalan kereta , Aerith
Hiya, thanks for keeping this blog up. I have the following drives (LTO 4), this is a output from sgscan.
task: add another LTO 6 drives.
(/dev/rmt/10):
(/dev/rmt/11):
(/dev/rmt/12):
(/dev/rmt/13):
(/dev/rmt/16):
(/dev/rmt/18):
(/dev/rmt/2):
(/dev/rmt/3):
(/dev/rmt/5):
(/dev/rmt/6):
(/dev/rmt/7):
(/dev/rmt/8):
(/dev/rmt/9):
Issue pops here. When i get the san admin to zone the drives and do a cfgadm -alv, it does not show me 6 of the current LTO4s configured. It’s taken up by 6 LTO6 drives.
Also a a bit of digging around showed me :
DEVICE PROPERTIES for tape: /dev/rmt/13mbn
Vendor: HP
Product ID: Ultrium 4-SCSI
Serial Num: xxxxxxxxxxx
Path status: Reservation conflict
Few questions which i need to understand and finding it hard to comprehend.
1. First and foremost. Why is cfgadm -alv mask the existing 6 LTO4 drives ? having said that all the wwpns were visible to me on cfgadm -al -o show_FCP_dev. I confirmed all the wwpns with the storage/backup admin 😦
2. Can you help me find some resources in understanding SCSI SAN devices and implementation on Solaris. Which will lead me to understand and use the sgbuild command with some sense. I will and i am struggling to get the “-mt” and the “-ml” values. ls -l /dev/rmt/*cbn shows me values from 0 – 4 for the lun.
Finally, do you have an idea as to if this is some reservation conflict that needs to be fixed with some setting on the Library/drive or something that could be managed at the OS layer.
Thanks again for your good work.
OSP
The elements i missed were, this node is a DIO LDOM running on SPARC VM 3.1.
As i said the drives are visible, and this setup has been running well with the existing LTO4 drives.
Solaris 10 SunOS mediaman 5.10 Generic_150400-17 sun4v sparc sun4v
Pingback: How To Configure Ntp Server On Solaris 8 | Goods News
Pingback: How To Configure Ntp Client On Solaris 11 | Goods News
Hi Aziz,
I have a problem with a sunstoragetek SL24. Netbackup can manage it, do everything. But every time I have to write on a medium, both LT03 is LTO4 says that an incompatible media. At the moment the drive firmware is H61W .. I do not know what to do … I suppose it may be the drive’s firmware .. You have the ability to source opure I suggest other tests?
Thanks for you r help
Walter
Hello Walter, look like there is wrong media type configuration on your Netbackup. If the tape drives type is HCART3 then the media/cartridge should use HCART3. LTO4 mostly detected as HCART, then the media/cartridge type should be HCART also. you can change manually the media/cartridge type.
Thanks for your reply.
I trie follow your advice and i will notice the result
Walter
Hello Aziz, i tried to follow your advice .. but i have the same error. Incompatible media..
Do you suggest other ?
Regards
Walter
Hi,
Have u work on zfs ost plugin on netbackup. it has a issue that can not discover lun for additional media server.
Can u suggest on this?