Data Protection using NetApp OnCommand Unified Manager

Creating, monitoring, and troubleshooting protection relationships

Unified Manager enables you to create protection relationships, to monitor and troubleshoot mirror protection and backup vault protection of data stored on managed clusters, and to restore data when it is overwritten or lost.

Depending on the deployment of your data storage topology, Unified Manager enables you to configure multiple types of SnapMirror protection relationships. All variations of SnapMirror protection offer failover disaster recovery protection, but offer differing capabilities in performance, version flexibility, and multiple backup copy protection.

Creating a SnapMirror protection relationship from the Health/Volume details page

  

You can use the Health/Volume details page to create a SnapMirror relationship so that data replication is enabled for protection purposes. SnapMirror replication enables you to restore data from the destination volume in the event of data loss on the source.

Before you begin

• You must have the OnCommand Administrator or Storage Administrator role.

• You must have set up Workflow Automation.

Go to Health/Volume page and select the unprotected volume to protect.

Then Select the Snapmirror tab.

Specify the Destination information.

Select an existing schedule or create a new schedule.

Once you submit, the protection job starts.

This protection job initiates the snapmirror workflow in OnCommand WFA.

Check with OnCommand WFA, it automatically schedules and executes the protection workflow the specified details.

Snapmirror workflow executing.

Check in the Cluster using System Manager, a new DP type volume created.

You can the new snapmirror relationship also.

Snapmirror workflow completed successfully.

Protection job status with full view details.

Volume protection details view.

In Protection/Volume Relationship page, you do monitor, manage and restore.

Quiesce  the data protection relationship.

Now it is quiescied.

Now break the relationship.

Now the status changed to broken-off.

Now resync the relationship.

The relationship successfully synced.

For each and every action, WFA executes the according workflow.