Building Disaster Recovery Serviceguard Solutions Using Metrocluster with EMC SRDF

B Package attributes for Metrocluster with EMC SRDF
This appendix lists all Serviceguard package attributes that are modified or added for Metrocluster
with EMC SRDF. HP recommends that you use the default settings for most of these variables, so
exercise caution when modifying them.
AUTOR1RWSUSP Default: 0
This variable is used to indicate whether a package must be
automatically started when it fails over from an R1 host to another R1
host and the device group is in suspended state. If it sets to 0, the
package will halt unless ${PKGDIR}/FORCEFLAG file has been
created. The package halts because it is not known what has caused
this condition. This could be caused by an operational error or a
Symmetrix internal event, such as a full primary memory. In such a
situation if you want to automatically start the package, set the
AUTOR1RWSUSP variable to 1.
AUTOR1RWNL Default: 0
This variable indicates that when the package is being started on an
R1 host, the Symmetrix is in a Read/Write state, and the SRDF links
are down, the package will be automatically started. Although the
script cannot check the state of the Symmetrix on the R2 side to validate
conditions, the Symmetrix on the R1 side is in a ‘normal’ state. To
require operator intervention before starting the package under these
conditions, set AUTOR1RWNL=1 and create the file
/etc/cmcluster/package_name/FORCEFLAG.
AUTOR1UIP Default: 1
This variable indicates that when the package is being started on an
R1 host and the Symmetrix is being synchronized from the Symmetrix
on the R2 side, the package will halt unless the operator creates the
$PKGDIR/FORCEFLAG file. The package halts because performance
degradation of the application occurs while the resynchronization is
in progress. More importantly, it is better to wait for the
resynchronization to complete to guarantee that the data are consistent
even in the case of a rolling disaster where a second failure occurs
before the recovery from the first failure. To always automatically start
the package even when resynchronization is in progress, set
AUTOR1UIP=0. However, this results in inconsistent data in case of a
rolling disaster.
AUTOR2WDNL Default: 1
AUTOR2WDNL=1 indicates that when the package is being started
on an R2 host, the Symmetrix is in a Write-disabled state, and the
SRDF links are down, the package will not be started. Since we cannot
verify the state of the Symmetrix on the R1 side to validate conditions,
the data on the R2 side might be non-current and thus a risk that data
loss will occur when starting the package up on the R2 side. To
automatically start the package under these conditions, set
AUTOR2WDNL=0
AUTOR2RWNL Default: 1
AUTOR2RWNL=1 indicates that when the package is being started
on an R2 host, the Symmetrix is in a read/write state, and the SRDF
links are down, the package will not be started. Since we cannot verify
the state of the Symmetrix on the R1 side to validate conditions, the
data on the R2 side might be non-current and thus a risk that data loss
will occur when starting the package up on the R2 side. To
87