Supported CloudPoint operations on NetApp storage
CloudPoint performs the following management operations on the NetApp storage arrays:
Table: CloudPoint operations on NetApp storage
CloudPoint operation | Description |
|---|
Discover assets | In a SAN deployment, CloudPoint discovers the LUNs that are created from storage volumes. Only LUNs whose status is online, read-write operations are enabled, and the Snapshot auto delete parameter is set to false, are discoverable. ["state":"online","vol_type":"rw"," is_snapshot_auto_delete_enabled": "false"]
In a SAN deployment, CloudPoint can discover only the snapshots that are created using CloudPoint. In a NAS deployment, CloudPoint discovers all the NFS shares on the NetApp storage. The shares must have an active junction_path configured so that CloudPoint can discover them.
|
Create snapshot | In a SAN deployment, CloudPoint takes a snapshot of the NetApp LUNs. When CloudPoint triggers a LUN snapshot on the NetApp storage, it internally triggers a redirect-on-write (ROW) snapshot of the entire volume to which the LUN belongs. If the volume contains multiple LUNs, the snapshot includes data from all the LUNs that reside on that volume. A typical snapshot created by CloudPoint has the following naming convention: NB<unique_21digit_number>
In a NAS deployment, CloudPoint takes a snapshot of the NetApp NFS shares.
|
Delete snapshot | In a SAN deployment, when you delete a LUN snapshot, CloudPoint internally deletes the snapshot of one or more volumes to which the LUN belongs. In a NAS deployment, CloudPoint deletes the snapshot of the share.
|
Restore snapshot | In a SAN deployment, when you restore a LUN from a snapshot, CloudPoint only restores the particular LUN on which the restore is triggered. The LUN snapshot is a ROW snapshot of the underlying volume and that volume can contain multiple additional LUNs. Even if the snapshot contains data from multiple LUNs, the restore is performed only for the selected LUN. Data on the other LUNs remains unchanged. In a NAS deployment, CloudPoint restores the volume using the specified snapshot.
|
Export snapshot | In a SAN deployment, when a snapshot export operation is triggered, CloudPoint creates a LUN from the snapshot and attaches it to target host. The target host is assigned read-write privileges on the exported LUN. The export operation is supported using the following protocols: In a NAS deployment, when a snapshot export operation is triggered, a new rule is created in the export policy and is assigned to the exported snapshot that is available as a network share. The target host is assigned read-only privileges on the exported snapshot share. The export operation is supported using the NFS protocol. CloudPoint does not modify the SVM's "default" export policy. The export operation will fail if the volume is attached only to the "default" export policy on NetApp. You must assign the NAS volume to a non-default export policy.
|
Deport snapshot | In a SAN deployment, when a snapshot deport operation is triggered, CloudPoint removes the LUN mapping from the target host and then deletes the LUN. In a NAS deployment, when a snapshot deport operation is triggered, NetBackup deletes the new rule that was created in the export policy when the snapshot was exported. |
Snapshot export related requirements and limitations
The following requirements and limitations are applicable in a NetApp environment:
The host on which the snapshot is to be exported must be zoned and added to the Storage Virtual Machine (SVM) where you wish to attach or export that snapshot.
The CloudPoint snapshot export operation fails for shares that are assigned the default array export policy. Ensure that you assign a different export policy (other than the default) to the share before you run the export operation.
A snapshot cannot be exported multiple times.
An exported snapshot cannot be deleted.
