
Configuring Primary and Secondary Disks
108 NetBackup ServerFree Agent System Administrator’s Guide
▼ Configure the arrays, depending on your requirements
The next steps depend on the results of the pairdisplay listings and the requirements
of your site.
◆ If all required disks are correctly paired (status of PAIR), the primary-secondary
configuration is finished.
◆ If required disks are paired but currently split (PSUS, SSUS), or if they are not paired
at all (SMPL), you must resynchronize or configure them, respectively.
Note If a mirror-type frozen image backup attempts to access a disk that is split or not
paired, the backup fails with a status code 11.
◆ If disks are paired but need to be unpaired or otherwise reconfigured, you must split
them and create a new association.
If disks are split:
1. Enter the following to resynchronize the split disks:
pairresync -g groupname -d dev_name
where groupname is the name listed under dev_group, and dev_name is the device
name, as defined in the configuration files. To resynchronize the disks listed as split
(PSUS, SSUS) in the above example (see “Resulting output:” on page 106), enter:
pairresync -g wiltest -d dev2
2. Enter the following to view the result:
pairdisplay -g wiltest -d dev2 -CLI -fc
When the resynchronization starts, the Status column reads COPY. When it is nearly
completed, the Status column reads PAIR (see the % column for percentage
completion).
If disks are not paired:
1. Enter the following to create a pair of primary and secondary:
paircreate -g groupname -d dev_name -vl
where groupname is the name listed under dev_group, dev_name is the device
name, as defined in the configuration files, and -vl specifies that the current instance
number is the primary.
To associate the dev3 disks as a pair (the ones listed as SMPL in the above example;
see “Resulting output:” on page 106), enter the following:
Comentarios a estos manuales