ONTAP upgrade from BlueXP fails on CVO with SVM DR Destination vservers
Applies to
- CVO (Cloud Volumes ONTAP)
- AWS (Amazon Web Services)
- Azure (Microsoft Azure)
- GCP (Google Cloud Platform)
- ONTAP Upgrade from BlueXP
- SVM DR ( Storage Virtual Machine Disaster Recovery) destination
- ONTAP > 9.6.x (SVM DR supported on CVO)
- Identity preserve enabled
Issue
- AWS CVO ONTAP upgrade from BlueXP ("
New Version Available") fails with error below on BlueXPTimeline

Cause
- CIFS server start on SVM DR destination vserver on AWS CVO failed during upgrade process from BlueXP.
- The vserver is configured as the destination for identity preserve Vserver DR where this operation is not permitted.
Solution
If CVO contains vservers that are SVM DR destination and upgrade fails due to error message above, then
- Identify any SVM-DR vservers that are in an admin-state of "running"
destination_cluster::> vserver show -subtype dp-destination -fields admin-state,operational-state
- Stop each of the vservers in the above command that show "running"
destination_cluster::> vserver stop <vserver>
- Ensure the all Destination SVMs are in a stopped/stopped state
destination_cluster::> vserver show -subtype dp-destination -fields admin-state,operational-state
- Break the SVM DR from Destination Cloud Volumes ONTAP command line
destination_cluster::> snapmirror break -destination-path dvs1:
| Do not proceed with the upgrade without ensuring the destination SVM has both an Admin State and Operational State of "stopped" |
- Upgrade ONTAP from BlueXP
New version availableNotification
- Resync the SVM DR from Destination Cloud Volumes ONTAP command line
destination_cluster::> snapmirror resync -destination-path dvs1:

