#Hp 3par ssmc os how to
#Hp 3par ssmc os driver
#Hp 3par ssmc os manual

#Hp 3par ssmc os driver

Currently, the HPE CSI Driver only supports Remote Copy Peer Persistence mode.

targetCpg, targetName, targetSecret and targetSecretNamespace are mandatory for HPEReplicationDeviceInfo CRD.

The CRD object name will be used to define the StorageClass parameter replicationDevices.

#Hp 3par ssmc os how to

Set the remoteCopyGroup parameter to the existing remote copy group name.ДЇor a tutorial on how to enable replication, check out the blog Enabling Remote Copy using the HPE CSI Driver for Kubernetes on HPE PrimeraДЄ Custom Resource Definition (CRD) of type must be created to define the target array information. It is recommended to pre-create the remote copy group with 'Auto Synchronize' and 'Auto Recover' enabled using either the SSMC or with the CLI using: setrcopygroup pol auto_failover,auto_synchronize.

'How Remote Copy recovers synchronous Remote Copy groups following replication link failure' in Disaster-Tolerant Solutions with HPE 3PAR Remote Copy.

'Remote Copy group policies' in HPE Primera OS: Configuring data replicationusing Remote Copy over IP.

This will be addressed in an upcoming release of the HPE Primera and 3PAR WSAPI.ДЇor more information on Auto synchronize:

#Hp 3par ssmc os manual

Due to this, any automatically create remote copy groups (RCG) through the HPE CSI Driver will require a manual recovery and restore once both HPE Primera or 3PAR systems are online and both Remote Copy links are up. Please see using the HPE CSI Driver for additional StorageClass examples like CSI snapshots and clones.Дue to a limitation within the HPE Primera/3PAR WSAPI, the auto-synchronize policy for replicated volumes is not available.

Restrictions applicable when using the CSI volume mutator:ДЎ = Parameters that are editable after provisioning.Дў = Volumes with snapshots/clones can't be modified. Indicates name of custom resource of type hpereplicationdeviceinfos.Д®nable the batch processing of persistent volumes in 10 second intervals and add them to a single remote copy group.Дuring this process, the remote copy group is stopped and started once.Д¬reates a dedicated Remote Copy Group per persistent volume.Д¬omma separated list of the array iSCSI port IPs. Name of a new or existing remote copy group on the array. Name of the volume set which has QoS rules applied. Name of the PersistentVolumeClaim to snapshot. Name of the PersistentVolumeClaim to clone. Indicates Thin Deduplication volume type. Indicates that the volume should be compressed. Defaults to value of cpg if not specified. The name of the snapshot CPG to be used for volume provisioning.

If the cpg parameter is not specified, the CSP will automatically set cpg parameter based upon a CPG available to the array. The name of existing CPG to be used for volume provisioning. The access protocol to use when accessing the persistent volume. Common Provisioning Parameters В¶ Parameter StorageClass Parameters В¶ДЄll parameters enumerated reflects the current version and may contain unannounced features and capabilities. It's recommended to use the edit role for security best practices. The CSP requires access to a user with either edit or the super role.

Please refer to SPOCK for the list of Platform supported OS. Ubuntu is not a supported OS option for the HPE CSI Driver when using HPE Alletra 9000 and HPE Primera. The documentation reflected here always corresponds to the latest supported version and may contain references to future features and capabilities. Refer to the HPE Single Point of Connectivity Knowledge (SPOCK) for specific platform details (requires an HPE Passport account) of the CSP. Always check the corresponding CSI driver version in the compatibility and support table. The following has been tested and validated for HPE CSI driver version with HPE Alletra 9000, HPE Primera and 3PAR. For help getting started with deploying the HPE CSI Driver using HPE Alletra 9000, Primera or 3PAR storage, check out the tutorial over at HPE DEV.