Registering ONTAP target storage with NetApp Data Availability Services Edit on GitHub Request doc changes

Contributors netapp-aherbin netapp-forry

The first step of backing up your data to the cloud or StorageGRID is to add an ONTAP target in the NetApp Data Availability Services (NDAS) app. The target is the NDAS proxy in the ONTAP secondary cluster; that is, the SnapMirror destination for the peered primary (source) cluster. A registration key is generated automatically within the NDAS app and the key must be entered on the ONTAP target cluster using ONTAP (formerly OnCommand) System Manager.

Before you begin

ONTAP and AWS prerequisites must be satisfied before registering NetApp Data Availability Services with the ONTAP target cluster.

About this task

NetApp Data Availability Services registration is a one-time operation required to establish connectivity with each target ONTAP secondary cluster providing NDAS proxy services. An NDAS administrator can generate the single-use registration key, but ONTAP administrator privileges are required to enter the registration key on the secondary cluster using System Manager.

After the registration key is entered on the cluster and credentials on the target cluster are authenticated, discovery of the registered cluster’s on-premises topology begins, and the discovery results are displayed in the NDAS app Dashboard pane. Discovery of additional clusters peered with the registered cluster requires authentication, so the associated cluster credentials for all peered clusters must also be entered on the NDAS app Targets window.

Steps
  1. In the NDAS app, click Dashboard in the left pane to open the Dashboard window.

    After initial setup, this operation can also be performed from the Targets window by clicking the Add menu.

  2. In the Protected to Disk box, click the Add Disk Target button.

    Step result: a registration key is automatically generated.

  3. Copy the registration key by clicking on the Copy icon.
    Do not pass the key using methods like email or text. Each registration key is supported for single-use only and expires after 24 hours.

  4. Open an instance of System Manager on the target ONTAP secondary cluster and log in with administrator credentials.

  5. Click Configuration → Cloud Registration.

  6. Paste the configuration key that you obtained in the NDAS app.

  7. Select the IPspace.

    The values for the intercluster LIFs, ports, and netmask are automatically populated.

  8. Click Register to register the ONTAP cluster with the NDAS app.

    • On successful registration, the server name (FQDN), IPspace, and status are displayed.

    • If the status is unavailable or disconnected, you must reregister the ONTAP cluster with the NDAS account by using a new configuration key.

  9. In the app, a notice is shown in the Dashboard window about registration status.

    Successfully registered <cluster>

  10. In the app, click Targets in the left pane to open the Targets window.

    The secondary cluster newly registered with NetApp Data Availability Services is seen.

  11. Click Authenticate Now to authenticate the newly registered secondary cluster.

    Enter the use ID and password for the cluster administrator.

    Step result: NetApp Data Availability Services discovers the peered source primary clusters.

  12. When authenticated secondary peer clusters (also known as "source clusters") are listed in the Targets window, click Authenticate Now to initiate authentication of primary clusters.

    • When source clusters are displayed on a new page, select a source cluster from which you want to protect volumes and click Authenticate.
      Enter the user ID and password for the cluster administrator.

      Successful authentication is indicated by a green check mark in the Authenticate field after a brief wait.

    • If you want to protect volumes from another source cluster, repeat the above authentication step for that source cluster.
      You need not authenticate all peered source clusters. However, if not authenticated you will not be able to discover volumes or protect data on those source clusters.

      Step result: when authentication is complete, the discovery process begins on the NDAS app for all the source clusters that you authenticated.

  13. Return to the Dashboard view to confirm the discovery existing data protection relationships and policies.