This operation can be started automatically after you have finished creating a volume resource hierarchy, or from an existing volume resource hierarchy, as described in the section on extending resource hierarchies. The following additional data is required to extend a volume resource hierarchy.
| Field | Tips | |||||||
|---|---|---|---|---|---|---|---|---|
| Volume Type | Select Shared Disk if using shared storage, Create Mirror if using SIOS DataKeeper and the mirror does not exist, or Existing Mirror if using SIOS DataKeeper and the mirror has already been created. | |||||||
| Network end points (Target/Source) | If Volume Type Create Mirror or Existing Mirror, select the network end points for the mirror. End points must be IP addresses. | |||||||
| Mode | If Volume Type Create Mirror, then select the mode of the mirror. Asynchronous Mirror: Source writes are queued for transmission to the target, and return immediately. Less reliable than synchronous, but source writes are quicker. Synchronous Mirror: All writes to the source volume will be committed to the target volume immediately. Higher reliability, lower performance. |
|||||||
| When extending the volume resource to a third system in the cluster, you must specify the volume type for each of the equivalent systems in the cluster. | ||||||||
| Volume Type (Shared or SIOS DataKeeper) | Select Shared Disk or the network end points for the mirror between the equivalent systems. | |||||||
Note: Mirrors created from the LifeKeeper GUI will be deleted when the volume resource hierarchy is deleted. To prevent the mirror deletion, set the LifeKeeper Delete Mirror Flag to False.
Post your comment on this topic.