Operational Defect Database

BugZero found this defect 1659 days ago.

Veeam | kb3027

Secondary storage backup stops working after NetApp MetroCluster switchover

Last update date:

8/13/2020

Affected products:

Veeam Backup & Replication

Affected releases:

ALL

Fixed releases:

No fixed releases provided.

Description:

Challenge

After the MetroCluster switchover a backup job with the SnapVault or SnapMirror specified on the Secondary Target tab cannot update these relationships.

Cause

Unfortunately this is a bug in the OnTap Data Management software. In the event of a switchover Veeam Backup&Replication cannot identify SnapVault/SnapMirror relationships.

Solution

You can trigger manual relationship update with the mandatory -source-snapshot option (for example after switching back to production). In a few minutes the updated relationship appears in the output of zAPI get-destination-iter call.  IMPORTANT: there must be at least 1 storage snapshot that wasn’t transferred to the target. If you specify a snapshot in -source-snapshot that was already transferred, such relationship will not appear in the get-destination-iter output.

Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Solved

Learn More

Search:

...