NDS Volume Registration

To complete the process of attaching a volume to NDS, you must register the volume in the Nasuni Management Console (NMC).

This is a one-time process unless you rotate or change the encryption keys of the object storage account backing the volume. In that case, you need to repeat this process to restore connectivity between NDS and the volume(s).

Prerequisites

Before beginning, access the UaaS API URL from the Nasuni Portal. To do this, follow these steps:

1. Log in to https://portal.nasuni.com/.

2. Navigate to Cloud Services → UniFS as a Service.

3. Click the UaaS stack hosting your NDS deployment.

4. Locate and copy the UaaS API URL from the top of the page.

Volume Registration Process

Register Volumes in the NMC

Each volume presented via NDS must be registered by temporarily enabling cloud-based snapshot retention.

To register volumes in the NMC, follow these steps:

1. Log in to the NMC and navigate to Volumes > Snapshot Retention.

   Important: Record the current retention settings of your volumes (take a screenshot for reference). You temporarily modify the retention settings, and then revert them back as the last step in this process.

2. Select the target volume(s) that you have attached to NDS via Nasuni Portal, and click Edit Volumes.

3. Toggle Update Retention Policy.

4. Set the Retain drop-down to Snapshots Within a Range.

5. Use the Years field to temporarily set the retention period to 25 years. This prevents retention processing.

6. Set Run Snapshot Retention on to Cloud.
   

7. Paste the UaaS API URL in the URL field.

   Note: The URL is structured like https://<uniquevalue>.execute-api.<region>.amazonaws.com or https://uaas-<uniquevalue>.azurecontainerapps.io

8. Click Save and wait for the UI to reflect the new cloud configuration for each of the enabled volume(s).
   
   

9. Revert each volume to its prior retention settings, referencing the screenshot you took in step 2.

   If Snapshot Retention was not configured, click the Retain drop-down and select All Snapshots.
   The Retention Provider column no longer displays “Cloud” for the volume(s) in scope.
   

   Important: Failure to revert each volume to its prior retention settings might cause cloud-based snapshot retention to run, which generates cloud costs billed to you by AWS or Azure.