NetBackup Support Utility (NBSU)

Did you know what is NBSU or NetBackup Support Utility? this is a great tools to gather diagnostic information in where Netbackup is installed and running. Its replaced what is known as “nbsupport” in previous versions.

“The NetBackup Support Utility (NBSU) is a Symantec utility used to gather diagnostic information about the system on which the utility is run. By default, NBSU gathers appropriate diagnostic information based on the Operating System and NetBackup environment.  With the availability of many command line options, the diagnostic information gathered can be tuned as desired”.

Actually, if you install Netbackup on Solaris, you can also run the Explorer command using an option “nbu_extended” like this:

/opt/SUNWexplo/bin/explorer -w default,nbu_extended

with “nbu_extended” option, the Explorer will collects Extended NetBackup information. Its not only gather the log, it will also run a few commands, collect the directories and more. see here to know what Explorer with nbu_extended do later on your systems.

Back to NBSU, for more detail about this great tools and to understand well on how to run nbsu commands, please click the link below:

DOCUMENTATION: What is the nbsupport utility and where can it be found?
http://support.veritas.com/docs/264785

DOCUMENTATION AND DOWNLOAD: NetBackup Support Utility (NBSU) Usage and Examples for 6.x. NBSU was released with 6.5, 6.0 MP6, and 5.1 MP7, and replaces what is known as “nbsupport” in previous versions.
http://support.veritas.com/docs/323434

Symantec NetBackup 7

Still waiting for Symantec NetBackup 7 release announcement. It has not been released yet,  but actually since Dec 2009, Symantec has been offered what they call as Symantec NetBackup 7.0 First Availability (FA) program.

What’s New In Symantec NetBackup 7

Just a little bit overview of new features in the latest NetBackup 7.0 release:

Integrated Deduplication
Includes native deduplication within the NetBackup client and allows customers to increase the speed of backups in remote offices, the data center, and virtual environments.
  • Built-in client-side deduplication improves physical & virtual backups speeds by up to 10x
  • Software-based deduplication reduces costs by up to 70% versus appliance approaches
  • Integrated client and target-side deduplication provides more coverage with fewer tools
  • Manage and improve the performance of 3rd party deduplication appliances using OpenStorage
Simple & Comprehensive Data Protection for Virtual Environments
Simplifies virtual server data protection by standardizing backup of Hyper-V and VMware.
  • New VMware data protection improves speed by 50% and reduces storage by up to 40%
  • Only NetBackup offers instant file recovery from any type of VMware or Hyper-V backup
  • Complete deduplication across all virtual and physical systems regardless of backup method
  • No backup or recovery compromises for customers who backup directly to tape
Faster Disaster Recovery with Global Data Protection
Ensure rapid and easy recovery of critical applications and backup data at other sites with integrated replication features.
  • Recover terabytes of application data in seconds from anywhere at any point-in-time
  • Efficiently manage and move up to 80% less data between different sites with optimized replication
  • Unified analytics and reporting reduces recovery risk across locations and backup products
Improved Management Console and Usability
Provides centralized console for integrated reporting, monitoring, alerting and management for multiple backup and archive domains.
  • Better predict backup and archiving storage consumption
  • Analyze risk and quantify exposure and assess the recoverability of clients and applications
  • Easily track backup success rates by backup application across the entire organization
Expanded Support for Windows Server and Applications
  • NetBackup 7 fully supports Windows 2008 R2, Vista/XP/Windows 7, and Storage Server 2008
  • NetBackup 7 offers full backup and recovery support for Exchange 2010 DAG environments and Exchange 2003

For more detail, you can attend the Webcast: What’s New in Symantec NetBackup 7 on Tuesday, February 2 2010 @ 9:00 AM PT Presented By: Peter Elliman, Senior Product Marketing Manager, NetBackup.

Attend this webcast and learn how NetBackup 7 can enable your company to:

  • Reduce backup storage growth and network utilization by up to 80-90%
  • Streamline global backup and recovery management across both physical and virtual environments
  • Simplify and speed recovery of critical information from anywhere

REGISTER Webcast here.

Related docs:

NetBackup 7.0 Upgrade Portal (Updated Jan 19th, 2010):
The NetBackup 7.0 Upgrade Portal contains important information regarding upgrading to NetBackup 7.0 from a previous 6.x version.

UPDATE:

Netbackup 7 released already. Read the manual guide:

Installation:

NetBackup 7.0 Upgrade Portal    http://entsupport.symantec.com/docs/332137
NetBackup Release Notes    http://entsupport.symantec.com/docs/340098
Additional Operational Notes    http://entsupport.symantec.com/docs/337179
Installation Guide for Windows  http://entsupport.symantec.com/docs/340100
Installation Guide for UNIX and Linux  http://entsupport.symantec.com/docs/340101
LiveUpdate Guide  http://entsupport.symantec.com/docs/340102

Administrator Guides:

Administrator’s Guide for UNIX,Linux, I  http://entsupport.symantec.com/docs/340103
Administrator’s Guide for UNIX,Linux, II  http://entsupport.symantec.com/docs/340104
Administrator’s Guide for Windows, I  http://entsupport.symantec.com/docs/340105
Administrator’s Guide for Windows, II  http://entsupport.symantec.com/docs/340106
OpsCenter Administrator’s Guide  http://entsupport.symantec.com/docs/340107
OpsCenter help set  http://entsupport.symantec.com/docs/340108
NDMP Administrator’s Guide  http://entsupport.symantec.com/docs/340109
Snapshot Client Administrator’s Guide  http://entsupport.symantec.com/docs/340110
NetBackup for Hyper-V Guide  http://entsupport.symantec.com/docs/340111
NetBackup for VMware Guide  http://entsupport.symantec.com/docs/340112

For complete manual guides, go to here:

http://seer.entsupport.symantec.com/docs/341274.htm

Top 10 Recommended Veritas NetBackup TechNotes

Document ID: 284146

http://support.veritas.com/docs/284146

Top 10 Recommended Veritas NetBackup ™ TechNotes


Details:

TechNote ID Description
183702 NET_BUFFER_SZ, SIZE_DATA_BUFFERS and NUMBER_DATA_BUFFERS – how they work and how to configure them
276739 STATUS CODE: 156 “snapshot error encountered” occurs when utilizing VSP or VSS for open file backups.
290185 Welcome to the Veritas NetBackup ™ 6.5 Upgrade Portal!
254809 DOCUMENTATION: How to configure email notifications for Windows clients using BLAT and nbmail.cmd in Veritas NetBackup ™
274063 Robtest commands that can be used to test the SCSI functionality of a robot
280202 GENERAL ERROR: When attempting to expire a media in Veritas NetBackup ™ 6.0 with the bpexpdate command, the message “requested media id was not found in the EMM database” is received.
278533 STATUS CODE: 800, NetBackup 6.0 jobs are failing with Status 800 (resource request failed).
244652 DOCUMENTATION: How to configure buffers for NetBackup in a Windows NT/2000 environment to improve performance
264924 DOCUMENTATION: How to restore an Exchange 2000/2003 database to the same or alternate client
245184 DOCUMENTATION: How to configure NetBackup for Mailbox backups of an Exchange 2000/2003 server

Note: Links to each of the documents listed in the following chart (by TechNote ID) can be found below, in the Related Documents section.

Related Documents:

183702: NET_BUFFER_SZ, SIZE_DATA_BUFFERS and NUMBER_DATA_BUFFERS – how they work and how to configure them
http://support.veritas.com/docs/183702

244652: DOCUMENTATION: How to configure buffers for NetBackup in a Windows NT/2000 environment to improve performance
http://support.veritas.com/docs/244652

245184: DOCUMENTATION: How to configure NetBackup for Mailbox backups of an Exchange 2000/2003 server
http://support.veritas.com/docs/245184

254809: DOCUMENTATION: How to configure email notifications for Windows clients using BLAT and nbmail.cmd in Veritas NetBackup ™
http://support.veritas.com/docs/254809

264924: DOCUMENTATION: How to restore an Exchange 2000/2003 database to the same or alternate client
http://support.veritas.com/docs/264924

274063: Robtest commands that can be used to test the SCSI functionality of a robot
http://support.veritas.com/docs/274063

276739: STATUS CODE: 156 “snapshot error encountered” occurs when utilizing VSP or VSS for open file backups.
http://support.veritas.com/docs/276739

278533: STATUS CODE: 800, NetBackup 6.0 jobs are failing with Status 800 (resource request failed).
http://support.veritas.com/docs/278533

280202: GENERAL ERROR: When attempting to expire a media in Veritas NetBackup ™ 6.0 with the bpexpdate command, the message “requested media id was not found in the EMM database” is received.
http://support.veritas.com/docs/280202

290185: Welcome to the Veritas NetBackup ™ 6.5 Upgrade Portal!
http://support.veritas.com/docs/290185

Veritas Netbackup Status Code and Troubleshooting Guide

If you got failed or error with Netbackup, sometimes it’s not easy to troubleshoot. The common error that always faced with my customer is ‘status code 196 : client backup was not attempted because backup window closed‘, or the worst is the got ‘status code 96 : unable to allocate new media for backup, storage unit has none available‘.

I think if you familiar with Netbackup, and somebody told you about these error code, probably with confident smile you will say, “Owh, its easy man; for status code 196, check the backup schedule then re-arrange the backup window time between all server, client and mediaserver and then for status code 96, just simply put new cartridges on its volume pool, then run backup again, I bet 100% the error code will gone. right?.

But do you remember the whole Netbackup status code and how to troubleshoot? If you don’t then here are the Technote contains a table for NetBackup’s Status Codes, with links to potential resolutions for each:

http://seer.entsupport.symantec.com/docs/301522.htm

or, you can also directly go to this page:

http://www.symantec.com/business/support/overview.jsp?pid=15143

then just put the keyword, exp: “status code 196”.

Example:

Download also the “Veritas NetBackup Troubleshooting Guide for UNIX, Linux, and Windows

Decommision Media Server

When a media server is decommisioned b4 removing from Netbackup , plz follow the below steps to make the setup stable once again.

Step 1 : go to server host properties & delete the media server name in the “Media server” List & also in the “server” list.

Step 2. Remove the storage unit which belongs to the particular decomissioned media

Step 3 : stop all the services then, Go to \install path\volmgr\database.

Rename the below files. globdb, robtic_def & ltdevis to .old
go to misc folder & delete all the files except the robotic_def directory.
get inside to this robotic_def dir & delete the files.

Step 4. start all the netbackup services

Open cmd promt & go to volmgr\bin dir
type

vmglob -set_gdbhost

Step 5. go to configure storage devices wizard. you can still see the decommisioned media server entry checkbox.

Delete the decomissioned media server entry alone & discover the conf storage device for the remaining servers

Now u will be able to run bpmedialist without any issues. Some of the tapes will show DBBackup status. You can bring them to scratch or secure the data. (solution given in previously for other person). run thru the forum for this.

This is the solution for ur query & nothing more u need.

Thank’s to Ranjith Kumar. J for the article..

Replace drive in SSO environment

In case one of our customer had drive replacement it’s mean that serial number also change. So in order to update the serial number in SSO environment. Here’s the steps.

1. tpautoconf -report_disc , this command will list what device that had been missing or found.
2. tpautoconf -replace_drive drive_name –path drive_path, this command will update the existing device configuration with the new one.

———
#cd /usr/openv/volmgr/bin
#tpautoconf -report_disc
===== Missing Device (Drive) =====
Drive Name = IBMULTRIUM3-TD03
Drive Path = /dev/rmt/c36t6d0BESTnb
Inquiry = “IBM ULTRIUM-TD3 64D0”
Serial Number = xxxxxxxxxxxx
ACS(4) definition ACS = 0 LSM = 0 PANEL = 1 DRIVE = 4
Hosts configured for this device:
Host = xxxxxxxxxxxx
Host = xxxxxxxxxxxx

=====Missing Device (Drive) =====
Drive Name = IBMULTRIUM3-TD02
Drive Path = /dev/rmt/c35t6d0BESTnb
Inquiry = “IBM ULTRIUM-TD3 64D0”
Serial Number = xxxxxxxxxxxx
ACS(4) definition ACS = 0 LSM = 0 PANEL = 1 DRIVE = 8
Hosts configured for this device:
Host = xxxxxxxxxxxx
Host = xxxxxxxxxxxx

===== Missing Device or no local control path (Robot) =====
Defined as robotic ACS(4)
Inquiry = “-”
Serial Number =
Robot Control Host = xxxxxxxxxxxx
Hosts configured for this device:
Host = xxxxxxxxxxxx
Host = xxxxxxxxxxxx

===== New Device (Tape) =====
Inquiry = “HP C5683A C305”
Serial Number = xxxxxxxxxxxx
Drive Path = /dev/rmt/c4t0d0BESTnb
===== New Device (Tape) =====
Inquiry = “IBM ULTRIUM-TD3 64D0”
Serial Number = xxxxxxxxxxxx
Drive Path = /dev/rmt/c35t6d0BESTnb
===== New Device (Tape) =====
Inquiry = “IBM ULTRIUM-TD3 5BG2”
Serial Number = xxxxxxxxxxxx
Drive Path = /dev/rmt/c36t6d0BESTnb
# tpautoconf -replace_drive IBMULTRIUM3-TD02 -path /dev/rmt/c35t6d0BESTnb
Found a matching device in global DB, IBMULTRIUM3-TD02 on host xxxxxxxxxxxx
update of local DB on host xxxxxxxxxxxx completed
globalDB update for host xxxxxxxxxxxx completed
Found a matching device in global DB, IBMULTRIUM3-TD02 on host xxxxxxxxxxxx
etc…

etc…

————–

Device Configuration must be run on all servers to complete drive replacement

Configure Netbackup Device (Robot & drive) on AIX

Hardware :
Sun Storagetek L40 with SCSI LVD/SE.
2 drive : Seagate LT01 and SDLT 320
SCSI ID : Robotic = 6
Drive 0 = 0
Drive 1 = 1
———

1. run command : lsdev –C –c adapter (to determine the logical indetifier for the SCSI controler)
# lsdev -C -c adapter
ent0 Available 10-80 IBM 10/100 Mbps Ethernet PCI Adapter (23100020)
fda0 Available 01-D1 Standard I/O Diskette Adapter
mg20 Available 10-70 GXT130P Graphics Adapter
paud0 Available 01-Q2 Ultimedia Integrated Audio
ppa0 Available 01-R1 CHRP IEEE1284 (ECP) Parallel Port Adapter
sa0 Available 01-S1 Standard I/O Serial Port
sa1 Available 01-S2 Standard I/O Serial Port
scsi0 Available 10-60 Wide/Fast-20 SCSI I/O Controller (used for CDROM & SCSI Hardisk)
scsi1 Available 10-88 Wide/Ultra-2 SCSI I/O Controller (Tape & robotic)

sioka0 Available 01-K1-00 Keyboard Adapter
siokma0 Available 01-K1 Keyboard/Mouse Adapter
sioma0 Available 01-K1-01 Mouse Adapter
siota0 Available 01-Q1 Tablet Adapter

2. run command : lsdev –C –s scsi (to display the SCSI device files)
# lsdev -C -s scsi
cd0 Available 10-60-00-1,0 16 Bit SCSI Multimedia CD-ROM Drive
hdisk0 Available 10-60-00-9,0 16 Bit LVD SCSI Disk Drive
rmt0 Available 10-88-00-0,0 Other SCSI Tape Drive
rmt1 Available 10-88-00-1,0 Other SCSI Tape Drive

Note:
Detected two drives, but robotic didn’t detected.

3. to detect robot, run this command :
#cd /usr/openv/volmgr/bin/driver
#./install_ovpass {to install the SCSI passthru driver}

Then run:
#mkdev -c media_changer -s scsi -t ovpass -p controller -w id,lun

Where:
◆ controller is the logical identifier of the drive’s SCSI adaptor, such as scsi0, scsi1 or vscsi1.
◆ id is the SCSI ID of the robotic connection.
◆ scsi_id is the fibre channel identifier for the N_Port address (D_ID) of the robotic connection.
◆ lun is the logical unit number of the robotic connection.

Example:
# mkdev -c media_changer -s scsi -t ovpass -p scsi1 -w 6,0

4. run command : lsdev –C –s scsi (to display the SCSI device files)
# lsdev -C -s scsi
cd0 Available 10-60-00-1,0 16 Bit SCSI Multimedia CD-ROM Drive
hdisk0 Available 10-60-00-9,0 16 Bit LVD SCSI Disk Drive
ovpass0 Available 10-88-6,0 VERITAS Media Changer {SCSI device driver for robotic}
rmt0 Available 10-88-00-0,0 Other SCSI Tape Drive {SCSI device driver for drive0)
rmt1 Available 10-88-00-1,0 Other SCSI Tape Drive {SCSI device driver for drive1)

5. make sure with the performing command: ./scan from /usr/openv/volmgr/bin/
#cd /usr/openv/volmgr/bin
# ./scan
************************************************************
*********************** SDT_TAPE ************************
*********************** SDT_CHANGER ************************
*********************** SDT_OPTICAL ************************
************************************************************
————————————————————
Device Name : “/dev/rmt0.1”
Passthru Name: “/dev/rmt0.1”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : “SEAGATE ULTRIUM06242-XXX1619”
Vendor ID : “SEAGATE ”
Product ID : “ULTRIUM06242-XXX”
Product Rev: “1619”
Serial Number: “xxx”
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/rmt1.1”
Passthru Name: “/dev/rmt1.1”
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: “xxx”
WWN : “QUANTUM SDLT320 xxx”
WWN Id Type : 1
Device Identifier: “QUANTUM SDLT320 xxx ”
Device Type : SDT_TAPE
NetBackup Drive Type: 11
Removable : Yes
Device Supports: SCSI-2
Flags : 0x4
Reason: 0x0
————————————————————
Device Name : “/dev/ovpass0”
Passthru Name: “/dev/ovpass0”
Volume Header: “”
Port: -1; Bus: -1; Target: -1; LUN: -1
Inquiry : “STK L40 xxx”
Vendor ID : “STK ”
Product ID : “L40 ”
Product Rev: “0215”
Serial Number: “LLC0220xxx”
WWN : “”
WWN Id Type : 0
Device Identifier: “”
Device Type : SDT_CHANGER
NetBackup Robot Type: 8
Removable : Yes
Device Supports: SCSI-3
Number of Drives : 0
Number of Slots : 0
Number of Media Access Ports: 0
Flags : 0x0
Reason: 0x0
# lsdev -C -s scsi
cd0 Available 10-60-00-1,0 16 Bit SCSI Multimedia CD-ROM Drive
hdisk0 Available 10-60-00-9,0 16 Bit LVD SCSI Disk Drive
ovpass0 Available 10-88-6,0 VERITAS Media Changer
rmt0 Available 10-88-00-0,0 Other SCSI Tape Drive
rmt1 Available 10-88-00-1,0 Other SCSI Tape Drive
# lsdev -C -c adapter
ent0 Available 10-80 IBM 10/100 Mbps Ethernet PCI Adapter (23100020)
fda0 Available 01-D1 Standard I/O Diskette Adapter
mg20 Available 10-70 GXT130P Graphics Adapter
paud0 Available 01-Q2 Ultimedia Integrated Audio
ppa0 Available 01-R1 CHRP IEEE1284 (ECP) Parallel Port Adapter
sa0 Available 01-S1 Standard I/O Serial Port
sa1 Available 01-S2 Standard I/O Serial Port
scsi0 Available 10-60 Wide/Fast-20 SCSI I/O Controller
scsi1 Available 10-88 Wide/Ultra-2 SCSI I/O Controller
sioka0 Available 01-K1-00 Keyboard Adapter
siokma0 Available 01-K1 Keyboard/Mouse Adapter
sioma0 Available 01-K1-01 Mouse Adapter
siota0 Available 01-Q1 Tablet Adapter
#

6. ALL DETECTED NOW!!
To ensure the driver device files are accessible after each system boot, the following command should be placed in the systemstartup script:
/usr/openv/volmgr/bin/driver/mkdev_ovpass

7. If u get an error, maybe there caused by the SCSI connection.
to remove the SCSI passthru driver, run : ./remove_ovpass from /usr/openv/volmgr/bin/driver

Netbackup – How do I expire, delete tapes from the database?

First you need to make sure that there are no valid images on the tape that you want.
NetBackup\bin\admincmd\bpimmedia -mediaid -L

If there are no images that you need, expire the tape:
NetBackup\bin\admincmd\bpexpdate -m -d 0 -host -force
This expires the images in the media database which resides specifically on the media server.

Verify that the images have been expired by re-running:
NetBackup\bin\admincmd\bpimmedia -mediaid -L

Now make sure that the tape is deleted from the volume manager on the master server. This step is automatically run by Veritas twice a day, and if you have used bpexpdate the tape will be removed but you can force it to take effect immediately:
volmgr\bin\vmquery -m
This gets some information on the tape such as its assigned date, pool number and status. If the status is anything other that 0x0, that issue needs to be resolved first – The most likely issue is a Frozen tape – IT must be unfrozen before you deassign it.

To unfreeze a tape:
NetBackup\bin\admincmd\bpmedia -unfreeze -m -h
If the tape was suspended you can replace -unfreeze with -unsuspend

If you are unsure which media server the tape belongs to:
NetBackup\bin\admincmd\bpimmedia -L -mediaid

This step will deassign and remove the volume images.
Volmgr\bin\vmquery -deassignbyid

Finally delete the tape:
volmgr/bin/vmdelete -m

Thats all!!

How to Configure Tape Drive on Solaris for Veritas Netbackup

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