
Chapter 4, SAN Configuration for ServerFree Agent 67
Create Offhost Backup Configuration Files
- If the 3pc.conf file does not have an identification descriptor for each
device (or the descriptor is not supported by the third-party copy device),
enter the world-wide port name (w=) for each device. (Obtain the world-wide
port name from your “Device Checklist” on page 56.)
Create the mover.conf File
This section describes how to create a list of the available third-party copy devices in a
mover.conf file (required for the Third-Party Copy Device method only).
1. On the NetBackup media server, enter the following command:
/usr/openv/netbackup/bin/admincmd/bpmoverinfo
This creates the following file:
/usr/openv/volmgr/database/mover.conf
The bpmoverinfo command discovers any third-party copy devices available on the
SAN and lists them in the mover.conf file. Any tape drives with third-party copy
capability are listed first.
For a description of the bpmoverinfo command, refer to the commands appendix.
Note For bpmoverinfo to correctly list third-party copy devices in the mover.conf file,
the third-party copy devices must already have passthru paths defined. For an
example, see “Solaris only: Example for sg.links, sg.conf, and st.conf files” on
page 54.
2. If you need to control the circumstances under which a third-party copy device is
used, create a separate mover.conf file for a policy or storage unit:
/usr/openv/volmgr/database/mover.conf.policy_name
or
/usr/openv/volmgr/database/mover.conf.storage_unit_name
For information on these naming formats and possible mover file entries, refer to
“mover.conf Description” on page 62 and “Naming the Mover File” on page 64.
Following are example storage environments and mover.conf files.
Komentarze do niniejszej Instrukcji