https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IzMDI3IiwiaGFzaCI6ImE4Y2VlOTVmLTBlZGItNGQ4Ny1iMzliLWYwMjIyYmVhM2Y1MCJ9
1-800-691-1991 | 9am - 8pm ET
EN

Secondary storage backup stops working after NetApp MetroCluster switchover

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. 

KB ID:
3027
Product:
Veeam Backup & Replication
Published:
2019-11-12
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later