The Symantec Backup Exec for Windows Servers SAN Shared Storage Option
enables multiple media servers to share secondary storage devices, such as robotic
libraries, in a SAN. The secondary storage devices are not directly connected to
a single server by SCSI, but are connected to a Fibre Channel Switched Fabric
(FC-SW) or iSCSI.
To allow for sharing of storage devices and media between multiple media servers,
a shared Advanced Device and Media Management (ADAMM) database resides
on one media server called the database server or primary server. All media servers
on the SAN connect to this database to obtain a single, unified view of all shared
devices and media. Backup Exec uses this shared database to arbitrate all device
and media requests with comprehensive overwrite protection policies to prevent
accidental media overwrites. To resolve potential access conflicts between multiple
media servers, Backup Exec "reserves" robotic arms and tape devices while
operations are being performed.
Media catalogs are shared between media servers, so restore operations can be
performed using any media servers that share catalogs. If the media must be
moved from one device to another on the SAN, the media does not have to be
cataloged again. In a shared storage environment, secondary storage devices also
can be attached to the local SCSI, SATA, SAS, USB, or ATAPI buses of any media
server. However, these local devices, disk or tape drives connected to a server,
are only available to the server to which they are attached. Storage devices used
with the SAN Shared Storage Option must have a vendor-assigned serial number.
In the following example of a shared storage environment, the database server
and the media servers transmit data over the FC-SW through a fibre to SCSI bridge
(router) to secondary storage devices (SCSI robotic libraries).
Requirements for the SAN Shared Storage Option
The following are the minimum system requirements for running this release of
the SAN Shared Storage Option:
Windows 2000/2003/2008 must be installed. You cannot use SAN SSO with
the Windows Server Core installation option of Windows Server 2008.
Physical Memory Available, as shown in the Windows Task Manager, plus the
File Cache should exceed 256 MB.
The SAN Shared Storage Option must be locally installed at each server that
will be sharing secondary storage devices.
The devices in your SAN must be on the supported device list.
You can fine a list of compatible devices at the following URL:
http://entsupport.symantec.com/umi/V-269-2 All hardware drivers must be up to date and started.
You can fine a list of compatible drivers at the following URL:
http://entsupport.symantec.com/rd/bews-drivers.htm The primary server must have enough space for the catalogs of all the servers
in the SAN.
For a fibre channel-connected installation, note the following additional
requirements:
A fibre channel host adapter and its device drivers must be installed and
connected to the SAN.
A hub or switch must be connected to all the fibre to SCSI bridges or to the
fibre libraries on the SAN.
All the robotic libraries must be connected to the SCSI bridges or to the fibre
switches/hubs.
Symantec Backup Exec SAN Shared Storage Option 1625
Requirements for the SAN Shared Storage Option
The hub or switch must be powered up before the bridges or fibre channel
libraries.
All robotic libraries must be powered up before the bridges.
The bridges must be powered up before Windows loads the fibre channel driver
(usually during the boot phase).
