Disruptive actions for Aria Operations cluster that could cause data loss

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

While troubleshooting, maintaining Aria Operations cluster nodes, it is important that you are aware of the list of disruptive actions that could impact historical data.

Environment

Aria Operations

Resolution

You should avoid below changes into the product, to safeguard metrics/data stored : 
 

• Do not reboot/manipulate Aria Operations VMs (Cluster Nodes) outside Admin UI (i.e. reboot VMs from vCenter without taking cluster offline first)
• Do not delete Dashboards/Policies/Views/Reports/Alert Definition or any other custom content from Product UI without first cloning or taking a backup
• Do not delete more than one node in the cluster without HA enabled
• Do not delete a node in a non-HA cluster
• Do not move Cluster nodes in different DCs
• Do not delete objects from Operations > Configurations > Inventory Management as this will also remove its historical data.
• Do not delete an adapter instance from Administration > Integrations, including related objects. This will also delete historical data.
• Do not delete Cloud Proxies that are managing telegraf agents
• Do not delete Cloud Proxies that are part of CP with Persistence option enabled

From CLI/ssh standpoint, you should avoid running any : cp, mv, rm, dd, vi, DB commands without prior taking VM snapshot or backup.

For more info about snapshots, please refer to this Snapshot creation in Aria Operations