2018-01-29 10:16 PM
We are having an issue. We have two clusters with SVM-DR Replications. When we create replication admin-state of replica is running.But when we break replication for testing porpuse and set it again, admin state shows stopped.
Whe we try to run admin state we get error:
"Error: command failed: This operation is not permitted on a Vserver that is configured as the destination for Vserver DR"
OCUM shows warning "SVM Stopped".
2018-01-30 10:08 AM
Exactly. I stop SVM on primary site to simulate a failure, and everything works perfect on secundary site. Whe I set replication again from Primary to Secundary site then I get Admin State stopped.
2018-01-31 05:19 AM
I don't think i'm following it because we do this without issue.
So if you are running in DR, you need to stop the vserver in DR and then failback.
Maybe you can post your error from CLI here
2018-05-09 07:42 AM
I know this is a few months old, but what Quico says is absolutely true. At the time of initialization the DP-Destination SVM is clearly in the running admin state, but operationally in the Stopped state. However, if you failover the SVM and then attempt to resync the SVM DR relationship, the DP-Destination from that point forward shows both the Admin and Operational states as being Stopped. This is also causing OCUM to trigger alerts for a stopped SVM for us as well. This is apparently a "known issue"...see the following: https://kb.netapp.com/app/answers/answer_view/a_id/1005979/loc/en_US#__highlight
The workaround is to acknowlege the event, but not mark as resolved... Clearly not a "real" solution, and I still think that there's something fishy about the discrepancy between the SVM states when you "test" a SVM DR relationship and when you first set it up.