Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access XP P9000 for Linux B.12.00.00

1 – Startup the package after making the SVOL writable.
The risk of using this option is that the SVOL data might
actually be non-current and the data written to the PVOL
side after the hardware failure might be loss.
AUTO_SVOLPSUE (Default = 0)
This parameter is applicable when the PVOL and SVOL both
have the state of PSUE. This state combination occurs when
there is an Continuous Access link, or other hardware failure,
or when the SVOL side is in a PSUE state while we can not
communicate with the PVOL side. This will only apply while
in the Asynchronous mode.
The SVOL side becomes PSUE after the Continuous Access
link timeout value has been exceeded at which time the
PVOL side will try and flush any outstanding data to the
SVOL side. If this flush is unsuccessful, then the data on the
SVOL side will not be current.
Values:
0 – (Default) Do NOT startup the package at the secondary
site and allow package to try another node. Require user
intervention to either fix the problem by resynchronizing the
PVOL and SVOL or force the package to start on this node
by creating the FORCEFLAG file.
1 – Startup the package on the SVOL side. The risk of using
this option is that the SVOL data might actually be
non-current and the data written to the PVOL side after the
hardware failure might be loss.
AUTO_SVOLPSUS (Default = 0)
This parameter applies when the PVOL and SVOL both have
the state of suspended (PSUS). The problem with this situation
is we cannot determine the earlier state: COPY or PAIR. If
the earlier state was PAIR, it is completely safe to startup
the package at the remote site. If the earlier state was COPY,
the data at the SVOL site is likely to be inconsistent.
Values:
0—(Default) Do NOT startup the package at the secondary
site. Require user intervention to either fix the problem by
resynchronizing the PVOL and SVOL or force the package
to start on this node by creating the FORCEFLAG file.
1 – Startup the package after making the SVOL writable.
The risk of using this option is the SVOL data might be
inconsistent and the application might fail. However, there
is also a chance that the data is actually consistent, and it
is okay to startup the application.
CLUSTER_TYPE This parameter defines the clustering environment in which
the script is used. Must be set to “metro” if this is a
Metrocluster environment and “continental” if this is a
Continentalclusters environment. A type of “metro” is
supported only when the HP Metrocluster product is installed.
A type of “continental” is supported only when the HP
Continentalclusters product is installed.
FENCE Fence level. Possible values are NEVER, DATA, and ASYNC.
Use ASYNC for improved performance over long distances.
58 Package attributes for Metrocluster with Continuous Access XP P9000 for Linux