| and the data written to the PVOL side after the hardware |
| failure may be loss. |
| This parameter is not required to be set if a package is |
| configured for three data centers environment because three |
| data center does not support Asynchronous mode of data |
| replication. Leave this parameter with its default value in all |
| data centers. |
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 previous state: COPY or PAIR. |
| If the previous state was PAIR, it is completely safe to startup |
| the package at the remote site. If the previous state was |
| COPY, the data at the SVOL site is likely to be inconsistent |
| Values: |
| |
| 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 may be |
| inconsistent and the application may fail. However, there |
| is also a chance that the data is actually consistent, and it |
| is okay to startup the application. |
| If the package has been configured for a three data center |
| environment, this parameter is applicable only when the |
| package is attempting to start up in either the primary (DC1) |
| or secondary (DC2) data center. This parameter is not |
| relevant in (the third data center) in the recovery cluster. Use |
| this parameter’s default value in the third data center. |
CLUSTER_TYPE | This parameter defines the clustering environment in which |
| the script is used. Should 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. |
| If the package is configured for three data centers (3DC), |
| the value of this parameter must be set to “metro” for DC1 |
| and DC2 nodes and “continental” for DC3 nodes. |
DEVICE_GROUP | The Raid Manager device group for this package. This |
| device group is defined in the /etc/horcm<#>.conf file. |
| This parameter is not required to be set for a package |
| configured for three data centers environment. Device groups |
| for three data center's packages have new parameters. |
3DC_TOPOLOGY | This parameter is the differentiator between packages |
| configured for two data centers (2DC) and three data centers |
| (3DC). Unlike packages configured for two data centers |
| (2DC), this parameter must be set for a package configured |
| for a three data center environment. |
| This parameter can has the following values: |
| 1. |
| configured for 1:1:1, or cascaded, or multi hop |
479