Skip to main content
NetApp Knowledge Base

What is the impact of rebooting CVO , connector and mediator VM's ?

  1. Last updated
  2. Save as PDF
Views:
18
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
ds_cvo
Last Updated:

Applies to

  • BlueXP Connector
  • Cloud Volumes ONTAP (CVO)
  • Mediator
  • Google Cloud Provider (GCP)
  • Amazon Web Services (AWS)

Answer

  • Connectors can be safely rebooted without causing impact. The service is designed to overcome short outages of Connector availability
  • Mediator instances can be rebooted/stopped/started without affecting access to data. However, during the time that the Mediator is out of service the route tables will not be updated, if a CVO takeover were to occur clients could be affected if they normally access data over one of the routes that isn't updated during this time.
  • HA pair CVO’s can be rebooted one node at a time without any downtime. You just need to make sure that automatic takeover and giveback is enabled on both nodes using the command : storage failover show -fields auto-giveback,auto-giveback-after-panic,onreboot

Note: For Single Node CVO downtime is needed.

Additional Information

additionalInformation_text
NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.