Register SnapCenter Server

Contributors netapp-soumikd

Only a user with SnapCenterAdmin role can register the host on which SnapCenter Server 4.6 or later is running. You can register multiple SnapCenter Server hosts.


  1. In BlueXP UI, click Protection > Backup and recovery > Applications.

  2. From the Settings drop-down, click SnapCenter Servers.

  3. Click Register SnapCenter Server.

  4. Specify the following details:

    1. In the SnapCenter Server field, specify the FQDN or IP address of the SnapCenter Server host.

    2. In the Port field, specify the port number on which the SnapCenter Server is running.

      You should ensure that the port is open for the communication to happen between SnapCenter Server and the Cloud Backup for Applications.

    3. In the Tags field, specify a site name, city name, or any custom name with which you want to tag the SnapCenter Server.

      The tags are comma separated.

    4. In the Username and Password field, specify the credentials of the user with SnapCenterAdmin role.

  5. Click Register.

After you finish

Click Backup & Restore > Applications to view all the applications that are protected using the registered SnapCenter Server host.

By default, the applications are automatically discovered every day midnight. You can configure the schedule to discover the applications.

Note For SQL Server databases, the Application Name column displays the name in application_name (instance name) format.

The supported applications and their configurations are:

  • Oracle database:

    • Full backups (data + log) created with at least one daily, weekly, or monthly schedules


  • Microsoft SQL Server database:

    • Standalone, failover cluster instances, and availability groups

    • Full backups created with at least one daily, weekly, or monthly schedules


  • SAP HANA database:

    • Single Container 1.x

    • Multiple Database Container 2.x

    • HANA System Replication (HSR)

      You should have at least one backup on both primary and secondary sites. You can decide to do a pro-active failure or a deferred failover to the secondary.

    • Non-data Volumes (NDV) resources such as HANA binaries, HANA archive log volume, HANA shared volume, and so on

The following databases will not be displayed:

  • Databases that have no backups

  • Databases that have only on-demand or hourly policy

  • Oracle databases residing on NVMe