![]() ![]() It captures the actual metrics data, snapshots, and so on. The Controller Java keystore (600 byte file): /.appd.scskeystoreĪnd the Enterprise Console keystore: platform-admin/.appd.scsĪ complete backup saves all runtime data associated with the Controller installation.Run the script described in Using mysqldump to back up the Controller.By backing up metadata, you can avoid having to reconfigure monitored applications in the Controller in the event of a failure. It does not include what can be thought of as "runtime data", the big data tables that contain the metrics, snapshots, events, and top summary stats (top SQL, top URLs, and so on) generated in the monitored environment. Metadata defines the applications monitored by the Controller, business transactions, policies, and so on. Metadata Backup (Level 2)Ī metadata backup exports the data that encapsulates the environment monitored by the Controller. For a list of those files, see Migrate the Controller. This may be the case if you are migrating an existing Controller configuration to a new Controller installation, for example. While it is recommended that you copy the entire Controller home except for the data directory when performing a light backup, particularly before performing a Controller upgrade, there are scenarios in which you may wish to copy only site-specific configuration files. To perform this type of backup, simply copy everything in the Controller installation directory EXCEPT the data directory. This type of backup lets you avoid having to reconfigure the Controller in case of machine failure. Light Backup (Level 1)Ī light backup targets Controller configuration files like db.cnf and domain.xml. See Enterprise Console Back Up and Restore for more information. A level 3 backup also backs up the Enterprise Console data. In addition to performing a level 1 or 2 backup, you should also back up the data for the Enterprise Console with mysqldump on a regular basis. Level 3: Backs up all data, either by performing a cold backup of the /data directory or a hot backup using a third-party tool.Ī possible backup strategy may be to perform a level 1 and level 2 backup very frequently, say nightly, and a level 1 and level 3 backup about once a week.Level 2: A metadata backup involving all metadata associated with the installation except for big data tables.Level 1: A light backup of the installation environment only.The scope of a Controller backup can be categorized into these levels: That is, you may choose to perform partial backups more frequently and full backups less frequently. To balance the risk of data loss against the costs of performing backups, a typical backup strategy calls for backing up the system at different scopes at different times. Best Practices for Backupsīacking up the entire system each night may not be feasible when dealing with the large amount of data typically generated by a Controller deployment. It is to be noted that controller versions 4.3 and later will work only on restoring and backing up the /.appd.scskeystore file. Note that your Controller should be shut down before performing any import functions. This page provides an overview of the tasks and considerations related to backing up the Controller. ![]() In addition to regular backups, back up the Controller and Enterprise Console before upgrading or migrating them from one server to another. The BackupTools section describes tools that support each approach. Other approaches include using a disk snapshot mechanism or using database backup tools. A secondary Controller also makes it practical to take cold copies of the Controller data, since you can shut down the secondary to copy its data without affecting Controller availability. For information on HA, see Controller High Availability (HA). With high availability, the database on the secondary Controller keeps a replicated copy of the data on the primary Controller. One method of maintaining backups of the Controller is to implement high availability. ![]() AppDynamics strongly recommends that you perform routine data backups of the Controller.
0 Comments
Leave a Reply. |