Frequently Asked Questions About Shared Storage Option - Symantec NetBackup Manual

Frequently asked questions about Shared Storage
Option
Verify that you did not interrupt a data path during a backup. If you do, the
NetBackup job fails. It can fail with media write errors or it may hang and have
to be terminated manually.
Verify that you do not use Berkeley-style close on the tape path (UNIX or Linux
servers only).
On Solaris systems, verify the following:
That you added tape configuration list entries in
needed).
That you defined configuration entries for expanded targets and LUNs in
and
sg.links sg.conf
/etc/devlink.tab
The first entry uses hexadecimal notation for the target and LUN. The
second entry uses decimal notation for the target and LUN.
Use a single tab character between the entries; do not use a space or a space
and a tab character.
That you configured the operating system to force load the
drivers.
For more information, see the Solaris chapter of the NetBackup Device
Configuration Guide.
Q. What combinations of SAN hardware components are supported for Shared
Storage Option?
A. Shared Storage Option works with many hardware combinations. Symantec
has an open policy on hardware support for Shared Storage Option. Consult your
hardware suppliers to verify the interoperability of their products.
A list of SAN components that have been tested with NetBackup is available on
the Symantec support Web site:
http://entsupport.symantec.com
Q. If NetBackup allocates four drives to a server and it finishes with two of the
drives, does NetBackup reallocate the two drives? Or does NetBackup wait until
the backup schedule that uses the four drives is completely finished before it
reallocates the drives?
A. The two available drives are reallocated and used. NetBackup monitors drive
status and notifies the NetBackup scheduler of drive availability.
Troubleshooting the Shared Storage Option

Frequently asked questions about Shared Storage Option

files. If you see problems with the entries in the
file (created from
sg.links
/kernel/drv/st.conf
), verify the following:
sg/st/fcaw
165
(if