Share via

3.1.4.3.1.29 CLUSCTL_RESOURCE_ADD_REGISTRY_CHECKPOINT_32BIT

  • Article

The CLUSCTL_RESOURCE_ADD_REGISTRY_CHECKPOINT_32BIT resource control code SHOULD<164> associate registry data, as specified in section 3.1.1.1.1.1, from the 32-bit version of the registry of the server with the designated resource.

The client MUST provide the path, in the buffer that is designated by lpInBuffer, to the data in the alternate registry of the server, as specified in section 3.1.1.1.1.1. If the alternate registry does not exist, then the path specifies the location of data in the default registry of the server.

After successful completion of the method, the server SHOULD NOT write any data to the buffer that is designated by lpOutBuffer.

The server MUST restore the registry data on the node hosting the resource prior to bringing the resource online. The server MAY choose to detect changes in the registry data and take another checkpoint of the data associated with the resource. The server SHOULD monitor changes in the checkpointed registry key and take another checkpoint when a change has been detected.

The server MUST accept a CLUSCTL_RESOURCE_ADD_REGISTRY_CHECKPOINT_32BIT resource control code request if its protocol server state is in the read/write state, as specified in section 3.1.1.