This topic provides an overview of how to configure and administer Controller data storage.
About Controller Data Storage
The Controller requires persistent data storage to store the following type of information:
- Design of your applications (all metadata about business transactions, tiers, policies, and so on)
- History of the performance of your applications (metric data)
- Transaction snapshot data and events
- History of incidents that occurred (both resolved and unresolved incidents)
Controller Data Directory Location
By default, the AppDynamics Controller uses MySQL as its storage mechanism. The Controller bundles a MySQL instance with the Controller. At installation time, the Enterprise Console creates the necessary tables and artifacts in the database.
By default, the database files and data are stored in: <controller_home>/db.
Manage the Database User Password
The Enterprise Console creates the user account that the Controller uses to log into the database to perform database-related operations. The username of the account is "root", and the password is the one you supply to the Enterprise Console during the Controller installation process.
When attempting to access the data, the Controller reads the database user password from these sources and in the priority shown:
- From the MYSQL_ROOT_PASSWD environment variable
- From user input to a command line prompt
If you do not keep the password in the environment variable, you will need to supply it in response to a command-line prompt whenever performing an operation that involves accessing the database, starting the database, stopping the database, or logging into the database.
Moving the Controller Data Directory
After installation, you can move the data directory to a new location. This may be necessary, for example, if there is not enough disk space available during Controller installation.
If you are using symlinks, you must create the symlink outside of the root Controller install directory and move the data directory to the new volume after you install the Controller.
Warning: Do not mount a file system on <controller_home>/db/data. During Controller upgrade, the Enterprise Console moves the data directory to data_orig. Upgrade will fail if the Enterprise Console cannot complete this move.
You can also update the datadir path on the Controller Database Configurations page of the Enterprise Console GUI.
To relocate the Controller data directory
- Stop the Controller and its database. See Start or Stop the Controller.
Modify following properties in the <controller_home>/db/db.cnf file to point to the new location of the data directory.
datadir
tmpdir
log
slow_query_log_file
CODE
Copy (or move) the existing data directory <controller_home>/db to the new location.
For example, to copy the data on Linux:
cd <controller_home>/db/
cp data <new-location>
CODE
- Start the Controller. See Start or Stop the Controller.
- Check the database.log and server.log for any errors related to the database connection.