Supported CloudPoint operations on FUJITSU AF/DX models
You can perform the following CloudPoint operations supported on the FUJITSU AF/DX models:
Table: CloudPoint operations on FUJITSU AF/DX array
CloudPoint operations | Description |
|---|---|
Discover assets | CloudPoint discovers all the volumes and its snapshots. |
Create snapshot | To create a snapshot (snapOPCPlus), CloudPoint triggers a POST API call on the volume. The API returns the details of the snapshot job. using job ID, you can track the ongoing operation. A typical snapshot created by CloudPoint has the following naming convention: NB<unique_21digit_number> |
Delete snapshot | Delete a volume or snapshot: Before you try deleting a volume, snapshot, ensure that you first detach it from all hosts. Note the following:
To delete a volume or snapshot, CloudPoint triggers a delete REST API call with the required snapshot details. Then confirms that the snapshot is deleted successfully on the array. |
Restore snapshot | CloudPoint is uses volume snapshot restore API to restore volume snapshot to the point in time image on the volume. |
Export snapshot | When a snapshot export operation is triggered, a snapshot volume is attached to the host where it's exported. |
Deport snapshot | When a snapshot deport operation is triggered, the copy session of the source volume, host connection of snapshot volume, and exported snapshot volume are deleted. It is a revert of the export snapshot. |
Discovery
When you add the FUJITSU AF/DX plugin in the NetBackup or when the discovery happens, a call goes to the CloudPoint which discovers the assets like volumes, snapshots.
It discovers all the volumes and snapshots (snapOPCPlus). NetBackup discovers the snapshots which have names like NB<followed chars>.
Volumes are primary assets, each contains the associated snapshots, and asset ID. Then for the assigned asset ID NetBackup operations are performed.
Snapshot mapping
Create a new snapshot of a volume - When you create a snapOPCPlus copy session of volume then the targeted volume is referred as Snapshot Volume and it represents a point-in-time copy of the source volume. The snapshot volume is created on the same appliance as the source volume.
To create snapshot, you need a thin provision pool which have a flexsnap_pool prefix. if you don't create a thin provision pool with the prefix flexsnap_pool then snapshot operation fails.
Export
When a snapshot export operation is triggered, a snapshot volume is attached to the host where the snapshot is exported.
Follow the steps to export a snapshot:
Fetch initiators on which you want to perform export.
Based on the port and initiator fetch the host ID.
Create a new host LUN to map the snapshot volume.
Map the snapshot volume to the host.