Cluster Server 8.0 Bundled Agents Reference Guide - Windows
- Introducing VCS bundled agents
- Storage agents
- Network agents
- FileShare agents
- Services and applications agents
- VCS infrastructure and support agents
- VCS hardware replication agent for NetApp
- Troubleshooting bundled agents
Attribute definitions
Table: RegRep agent required attributes
Required Attributes | Description |
---|---|
Keys | The list of registry keys to be monitored. From the 'name-value' pair of a registry key, you must provide the name of the registry keys to be synchronized and not the value for that key. When defining the keys, you must use the abbreviations listed in See Configuring registry keys. The agent also enables you to replicate a registry key without replicating the subkeys.See Ignoring subkeys. for instructions. This attribute can take localized values. Warning: Do not configure more than 63 keys for a single RegRep resource otherwise the resource will go in an UNKNOWN state. Type and Dimension: string-association |
MountResName | The name of the MountV resource on which the Registry Replication resource depends. The MountV resource specifies the mount drive on the shared disk where the log file is created. In case of a NetApp storage environment, this will be the name of the NetAppSnapDrive resource. Type and Dimension: string-scalar |
ReplicationDirectory | The directory on the shared disk in which the registry changes are logged. The agent creates a directory with the specified name if one does not exist. Default is "\\REGREP\\DEFAULT". Note: This attribute can take localized values. Type and Dimension: string-scalar |
Table: RegRep agent optional attributes
Optional Attributes | Description |
---|---|
DebugMonitor | Defines whether debug logging is to be enabled for the executable (RegRepMonitor.exe) that monitors the registry keys. The value 0 indicates that the logging is enabled. The value 1 indicates that it is not. Default is 1. Type and Dimension: integer-scalar |
ExcludeKeys | A list of the subkeys to be excluded from replication. For more information on how the agent excludes keys, see Excluding keys. When defining the keys, you must use the abbreviations listed in Configuring registry keys. Note: This attribute can take localized values. Type and Dimension: string-vector |
ForceRestore | Defines the agent behavior when the registry update fails on a node where the resource is being brought online. A registry update may fail if any of the keys being updated are open. If set to 1 and the registry update fails, the agent tries to forcibly restore the keys by:
If the update fails again, the agent reapplies the original values of the registry keys from the backup. If set to 0, the agent does not try to forcibly update the registry when an update fails. Default is 0. Type and Dimension: boolean-scalar |
ListOpenKeys | Defines whether the agent lists a set of registry keys, including keys having open handles, when a registry update fails. The list is logged to the agent log. The value 1 indicates the agent lists the registry key set. The value 0 indicates the agent does not. Default is 1. Type and Dimension: boolean-scalar |
RestoreLocally | Defines whether the agent restores the keys on the node if it was taken offline from the same node. For example, if the agent was taken offline from SystemA and brought online again on SystemA, this attribute determines whether the registry keys would be restored on SystemA. The value 1 indicates the agent restores the keys on the system.The value 0 indicates it does not. Default is 0. Type and Dimension: boolean-scalar |