![]() 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |