In the UI Infrastructure tab, select each physical machine and click Disable
Using the API, set the state of each physical machine to DISABLED
Check for operations in progress on the platform
Check that the Abiquo RabbitMQ queues are empty. The number of messages in all queues must be 0:
On standard environment, the RabbitMQ service is in the Abiquo API server. Depending on the environment, this will be the Abiquo Monolithic or the Abiquo Server appliance.
Check for any active V2V conversions by checking for the V2V or Mechadora processes
Stop platform services
Stop the API on the API Server or Monolithic Server
Stop the UI on the API Server or Monolithic Server or dedicated UI Server
Stop Remote Services server
Stop the database on the Monolithic Server or Database server.
For a datanode configuration, you will also need to stop the Galera cluster. For more details, see Stop and start HA configuration
Stop RabbitMQ (on the Monolithic Server or API Server or Datanode)
V2V Server - You do not need to stop anything because the BPM remote service is run on-demand only
Stop Monitoring server
On the Monitoring server, check if Cassandra is really dead
Get the process number for Cassandra (the first number in the output of the previous command), and kill it. In this example, Cassandra is process 12345.
Back up the main platform elements
Back up the Abiquo MySQL DBs with the date in timestamp format.
Dump the redis datastore and back it up.
Back up /opt/abiquo folder on all Abiquo platform servers.
Back up the UI
If you are using SAML authentication with multiple IdPs, back up this file from every API server: