Manage FlexCache volumes

This page describes how to manage your FlexCache volumes.

View FlexCache volume details

A FlexCache volume functions like a normal volume but includes a cacheParameters block that provides specific cache information.

Use the following instructions to view details of a FlexCache volume using the Google Cloud CLI.

gcloud

To view details of a FlexCache volume:

gcloud beta netapp volumes describe VOLUME_NAME --location=LOCATION

Example output:

...
cacheParameters:
 cacheState: PEERED
 enableGlobalFileLock: false
 peerClusterName: my-cluster
 peerSvmName: my-svm
 peerVolumeName: origin1
 cachePrePopulateState: done
...

Edit a FlexCache volume

You can edit a FlexCache volume like a regular volume in Google Cloud console, but you can't manage FlexCache settings. However, certain operations might fail when using the Google Cloud console. If this occurs, use the Google Cloud CLI instead.

Use the following instructions to edit a FlexCache volume using the Google Cloud CLI.

gcloud

If the peering isn't established, you can modify the peer-ip-addresses using the establish-peering command. If you need to change any other peer parameters before peering is complete, you need to delete the volume and recreate it.

A peering which isn't established is indicated by the cacheState as PENDING_CLUSTER_PEERING or PENDING_SVM_PEERING. This occurs due to network issues such as routing or firewall issues, or incorrect PEER_IP_ADDRESSES. After one hour, the peering process will time out.

To fix the incorrect PEER_IP_ADDRESSES or to restart the peering process:

gcloud beta netapp volumes establish-peering VOLUME_NAME --location=LOCATION \
  --peer-cluster-name=PEER_CLUSTER_NAME \
  --peer-svm-name=PEER_SVM_NAME \
  --peer-volume-name=PEER_VOLUME_NAME \
  --peer-ip-addresses=PEER_IP_ADDRESSES

Replace the following information:

  • PEER_CLUSTER_NAME: the name of the ONTAP cluster hosting the source volumes.

  • PEER_IP_ADDRESSES: the InterCluster-LIF IP addresses of the ONTAP cluster. The source cluster must provide one IC-LIF per node, separated by # signs. Make sure to specify them all.

    The following example shows you how to add multiple IC-LIF IP addresses of the ONTAP cluster:

    peer-ip-addresses=10.0.0.25#10.0.0.26

  • PEER_SVM_NAME: the name of the storage virtual machine (SVM), also known as vserver that owns the source volume.

  • PEER_VOLUME_NAME: the name of the source volume.

After peering is established which is indicated by cacheState as PEERED, you can no longer change the peering parameters for that volume. However, you can modify the cache-config parameters.

To change the cache-config parameters:

gcloud beta netapp volumes update VOLUME_NAME --location=LOCATION \
  --capacity=CAPACITY --protocols=PROTOCOL \
  --share-name=SHARE_NAME --storage-pool=STORAGE_POOL \
  --snapshot-directory=FALSE --multiple-endpoints=TRUE \
  --cache-parameters=enable-global-file-lock=ENABLE_GLOBAL_FILE_LOCK,cache-config=cifs-change-notify-enabled=ENABLE_CIFS_CHANGE_NOTIFY#write-back-enabled=ENABLE_WRITE_BACK

Replace the following information:

  • ENABLE_GLOBAL_FILE_LOCK: Optional: a boolean flag indicating whether global file locking is enabled on the cache volume. The default is false.

  • cache-config: Optional: use the cache-config parameter block to specify additional parameters. Individual parameters must be separated by # signs.

    • ENABLE_CIFS_CHANGE_NOTIFY: Optional: a boolean flag indicating whether a CIFS change notification is enabled for the cache volume. The default is false.

    • ENABLE_WRITE_BACK: Optional: a boolean flag indicating whether to enable write-back mode. The default is false, which corresponds to using write-around mode.

Delete a FlexCache volume

You can delete a FlexCache volume like any other volume. For more information about instructions, see Delete a volume.

What's next

Prepopulate a FlexCache volume.