From 98ef34f020ce7020e3c3e75ee836a3fa391b2ab8 Mon Sep 17 00:00:00 2001 From: santhoshatdell Date: Wed, 13 Nov 2024 20:59:43 +0000 Subject: [PATCH] Update note on Metro snap restore and clone --- .../docs/replication/high-availability/powerstore-metro.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/docs/replication/high-availability/powerstore-metro.md b/content/docs/replication/high-availability/powerstore-metro.md index 2132435840..16efa096c7 100644 --- a/content/docs/replication/high-availability/powerstore-metro.md +++ b/content/docs/replication/high-availability/powerstore-metro.md @@ -45,16 +45,17 @@ volumeBindingMode: Immediate When a Metro `PV` is created, the volumeHandle will have the format ``. ### PowerStore Metro volume expansion -When a request is made to increase the size of a Metro `PV`, the metro replication session must be temporarily paused prior to the editing of Kubernetes resources. This can be done from the PowerStore Web UI or CLI. The size of the local/preferred volume is then increased. The metro session must then be manually resumed. It is important to note that the paths for the remote/non-preferred volume will not become active until the metro session is resumed and the remote/non-preferred volume reflects the updated size. +When a request is made to increase the size of a Metro `PV`, the metro replication session must be temporarily paused prior to the editing of Kubernetes resources. This can be done from the PowerStore Manager UI or CLI. The size of the local/preferred volume is then increased. The metro session must then be manually resumed. It is important to note that the paths for the remote/non-preferred volume will not become active until the metro session is resumed and the remote/non-preferred volume reflects the updated size. ### Snapshots on PowerStore Metro volumes When a VolumeSnapshot object is created for the Metro `PV`, snapshots are created on each side of the Metro session on the PowerStore systems. However, the VolumeSnapshot object only refers to the local/preferred side of the Metro volume. When a Metro `PV` is deleted, the remote/non-preferred volume, along with any snapshots associated with it, is also automatically deleted. ### Limitations - PowerStore driver only supports uniform host configuration for Metro volume where the host has active paths to both PowerStore systems. -- Metro volume only supports FC and iSCSI protocols for host access. - VolumeGroup Metro support is not currently available for uniform host configuration. +- Metro volume only supports FC and iSCSI protocols for host access. - Each Kubernetes node is automatically registered as a host object on both PowerStore systems when the node pods are running. However, the connectivity type of the host is set to 'Local Connectivity' by default. It needs to be updated manually with the correct 'Metro connectivity' option on both PowerStore systems using the PowerStore Manager UI. - Actions that need to be performed on the Metro session, such as pausing, resuming, or changing the preferred side, can only be done through the PowerStore Manager UI. - Some CSI Driver Capabilities, such as snapshot or clone, are not supported on the remote/non-preferred side of the Metro volume. +- While restoring a Metro snapshot or cloning a Metro volume on the local/preferred side, provide a non-Metro storage class. Configuring Metro on clones is not supported on the PowerStore. - The following [volume attributes](../../../csidriver/features/powerstore/#configurable-volume-attributes-optional) on PersistentVolumeClaims (PVCs) are not supported for Metro volumes: `csi.dell.com/volume_group_id`, `csi.dell.com/protection_policy_id` if the policy has replication rule. \ No newline at end of file