Snapcenter 6.1

[SteveBaskerville]

Setting up Snapcenter to manage snapmirror after the backup.  I check the box for snapmirror and there is a relationship for all drives: Data, Logs, and DLM which seems to be the replacement for snapinfo. Regardless it seems to replicate the snapshots to the cluster protecting them, but it constantly give warnings below.

Are these erroneous warnings?  has anyone else had this issue? 

Activity 'Replicating to Secondary' failed with error: You have selected a backup policy indicating that you want to backup to a secondary storage

system. Some of the resources you want to backup are located on a storage system that does not have replication relationships set up. Establish your

SnapVault or SnapMirror relationships before proceeding.

Microsoft SQL Server

ms-utility-sql.regent.edu

MS-UTILITY-SQL

SQL Daily Full and Logs

05/19/2025

10:31:01 AM

0.00:01:38

Warning

Failed on 'MS-UTILITY-SQL':

Activity 'Replicating to Secondary' failed with error: You have selected a backup policy indicating that you want to backup to a secondary storage

system. Some of the resources you want to backup are located on a storage system that does not have replication relationships set up. Establish your

SnapVault or SnapMirror relationships before proceeding.

Activity 'Creating SQL Backup' failed with error: The following activities failed:Replicating to Secondary,Grouping Resources. Please check the activities

for detailed error message.

SnapCenter Backup Report

Updated on: 05/19/2025 11:30:17 AM

05/19/2025 11:30:17 AM

[chenguanghui · Accepted solution]

hello:

  In SnapCenter, modify the resource group and then select the  Load Locators  button to refill the secondary relationship.If it method still doesn't work, I hope the following link will be helpful to you.

https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapCenter_SnapVault_update_job_fails_but_replication_succeeds_to_secondary_storage 

Best regards.

[Sanaman]

You can, as I do. I let SnapCenter to manage the snaps on the primary and Ontap schedule to manage the secondary site. We keep more on secondary site.

[SteveBaskerville]

This problem is now resolved, but I have another question. In the documentation it states:

If you set up SnapMirror replication, the retention policy is mirrored on the destination volume.

Is is possible to have a different retention policy for the destination volume?

I would like to keep fewer offsite copies of the backups on the destination cluster due to space constraints.

local copies 7 and destination copies 2.