Moving the bundle from CMX to a different machine If High Availability is disabled, online and offline backups are supported on both primary and secondary. Note: If High Availability is established, online backup is supported only on primary server. If High Availability is not currently established between primary and secondary server, first determine which CMX has complete and most recent data and create a backup from it. Simply run cmxos backup -all -online command and transfer the files from the primary server. If the High Availability is currently up and running, since all databases are synced between primary and secondary, taking the backup from primary CMX is enough to save all client data. Created backup file /tmp/cmx_backup_mse33752_2019_04_28_22_39.tar.gz Backing up a High Availability setup Requested clearing snapshot(s) for Īt the end of the output, name of the backup archive is specified: Done Backup. Running: /opt/apache-cassandra-3.9/bin/nodetool -ssl -h -p 7199 clearsnapshot Running: sudo -u cmx /opt/cmx/bin/cmxctl dump Running: sudo -u cmx /opt/cmx/bin/cmxctl version In PuTTY, this can be done under "Connection" ~]$ cmxos backup -online -all Make sure to enable keepalive messages in your SSH client so that the session does not time out while backup is being created. On a fully loaded and utilized CMX, creation of backup bundle can take up to an hour. On a freshly installed CMX, backup process takes ~30 seconds. It is recommended to use the default /tmp directory. Directory needs to have read, write and execute permissions. You are prompted to enter the directory where you want to save the backup tar.gz archive. Add the parameter -online to perform the backup without stopping the CMX services. By default, backup process stops CMX services while being performed. Add the -allparameter to include the Influxdb data as well. By default, backup includes database, cache, cassandra, floormaps, licenses, setup, connectimages and configuration. Backup process Creating the backup bundleĬMX, no matter where installed, can be backed up using a cmxos backup command. If your network is live, ensure that you understand the potential impact of any command. All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment. Connectimages - Stores Images on Connect Captive Portal.Licenses - Stores Cisco CMX license information.Floormaps - Stores floor images for UI display.Influxdb - Stores metrics data for systems (not included by default).Cassandra - Stores location history data and analytics raw visits.Database - Stores configuration data, such as, maps, controllers, location, and aggregated analytics data.These components of CMX can be backed up: This includes CMX installed on a physical 3365/3375 appliance, as well as on a virtual machine. Components UsedĪll tests were performed on a CMX 10.6.0-177 running on MSE 3375 appliance, MacOS 10.4 and Windows 10 October 2018 update. This document describes how to back up and restore configuration and client data on a Cisco CMX 10.5 and later Prerequisites Requirements
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |