Search <book_title>...

Veritas CloudPoint Administrator's Guide

Last Published: 2019-11-18

Product(s): CloudPoint (2.2.1)

Platform: Linux

Supported CloudPoint operations on NetApp storage

You can perform the following operations on supported 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"]` Note: 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 takes a LUN snapshot, it internally triggers a copy-on-write (COW) 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. Additionally, CloudPoint also adds the LUN's serial number as a prefix in the snapshot name. All snapshot names use the following convention: `<lun_serial_number>.<specified_snapshot_name>` For example, if `5431fd754` is the LUN serial number and `test_snapshot` is the snapshot name provided, CloudPoint assigns the following name to the snapshot: `5431fd754.test_snapshot` In a NAS deployment, CloudPoint takes a snapshot of the NetApp NFS shares. Note: Snapshot names can contain integers, letters, parenthesis ('()'), hyphen ('-'), underscore ('_'), plus ('+'), and dot ('.') characters.
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 snapshot, CloudPoint only restores the particular LUN on which the restore is triggered. The LUN snapshot is a COW 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 snapshot of the share.
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: Fibre Channel (FC) Internet Small Computer Systems Interface (iSCSI) 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. Note: The export policy assigned to the exported snapshot share must be other than the default policy assigned by the array. If the share is assigned the default policy, then the snapshot export operation will fail.
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, CloudPoint 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.
The CloudPoint user interface (UI) does not support running the snapshot export and deport operations.
Use the following CloudPoint API to perform these operations:
```
(POST) /v3/assets/<disk-ID>/snapshots/<snap-id>/exports/
(DELETE) /v3/assets/<disk-ID>/snapshots/<snap-id>/exports/<export-ID>
```
Here are some sample cURL commands:
For SAN Export:
curl -H "Content-Type: application/json" -H "Authorization: Bearer <token> -X POST -d '{"host-name":"offhost_server", "protocol":"fc|iscsi", "port":"<wwn given to host>"}' -k https://localhost/cloudpoint/api/v3/assets/<disk-ID>/snapshots/<snap-id>/exports/
For SAN Deport:
curl -H "Content-Type: application/json" -H "Authorization: Bearer <token>" -X DELETE -k https://localhost/cloudpoint/api/v3/assets/<disk-id>/snapshots/<snap-id>/exports<export-id>
For NAS Export:
curl -H "Content-Type: application/json" -H "Authorization: Bearer <token> -X POST -d ' {"host-name":"client ip to add rule ", "protocol":"nfs", "port":"-"} ' -k https://localhost/cloudpoint/api/v3/assets/<disk-ID>/snapshots/<snap-id>/exports/
For NAS Deport:
curl -H "Content-Type: application/json" -H "Authorization: Bearer <token>" -X DELETE -k https://localhost/cloudpoint/api/v3/assets/<disk-id>/snapshots/<snap-id>/exports/<export-id>
You can access the CloudPoint REST APIs using Swagger.
See Accessing the Swagger-based API documentation.