or to the StoreOnce. The same approach should be taken for StoreOnce Catalyst Copy over Fibre
Channel zoning of source and destination copy devices.
• When zoning for StoreOnce Catalyst Copy over Fibre Channel, ensure that the source Initiator WWN
is zoned with the destination target WWN, and that the destination Initiator WWN is zoned with the
source target WWN. StoreOnce Catalyst Copy is a two way protocol and both the source and
destination must be able to communicate with each other over Fibre Channel.
• Use small Fibre Channel zones limiting the number of Fibre Channel ports in each zone.
• When using StoreOnce Federated Catalyst, the backup/media server communicates with each
Federation member directly. Ensure that at least one port belonging to each Federation member node
is zoned with the backup/media server. HPE recommends zoning multiple ports for higher availability
and performance.
• When using StoreOnce Catalyst over Fibre Channel to StoreOnce 6500 and 6600 appliances, ensure
that a backup/media server is zoned with both StoreOnce nodes in the couplet. On a failover event,
the World Wide Name of the sister node will be used to communicate with both StoreOnce service
sets. This is transparent to the backup application because applications connect using the StoreOnce
Catalyst over Fibre Channel Identifier or alias.
• StoreOnce Catalyst over Fibre Channel does not make use of or rely on any external multi-path
drivers. Connections are balanced using StoreOnce Catalyst over Fibre Channel internal algorithms.
Installed multi-path drivers are ignored by Catalyst over Fibre Channel.
Client configurations
Once the client has been Fibre Channel zoned with the StoreOnce appliance, there are a number of
considerations for each operating system.
Windows Clients
Administrator permissions are required to run Catalyst over Fibre Channel backups.
StoreOnce Catalyst over Fibre Channel presents a device type of “Processor.” In Windows Device
Manager, these devices are shown as “Other Devices.” After zoning the devices or changing the Number
of Devices per Initiator Port, right-click “Other Devices” and select “Scan for hardware changes” to detect
the new devices.
Linux Clients
StoreOnce Catalyst over Fibre Channel presents a device type of “Processor.” On Linux, these devices
files are created in
/dev/sg*
. By default,
/dev/sg*
devices are accessible by root users only. If
backups are run as a nonroot user, first grant the backup user permissions to access these device files
using a Linux
udev
rule.
The
lsscsi --generic
command can be used to determine which
/dev/sg*
device files belong to
Catalyst over Fibre Channel.
AIX Clients
• StoreOnce Catalyst over Fibre Channel presents a device type of “Sequential” on AIX. These device
files are created in
/dev/rmt*
. After zoning the devices or changing the Number of Devices per
Initiator Port, you must scan for device file changes by executing the
cfgmgr
command on AIX as a
root user.
• By default,
/dev/rmt*
device files are accessible by root users only. Running backups as a nonroot
user requires an additional one-time configuration step of running
storeonce-cofc-passthrough-
install.sh
. This installation script must be run as root and can be found in the backup application
installation
bin
directory. This step is only required when backups will not be run as a root user.
90
Client configurations