Are you a member of the Splunk Community?
- Find Answers
- :
- Splunk Platform
- :
- Splunk AppDynamics
- :
- Restore Controller Database
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I want to restore the controller's database from metadata backup(level2) to new enviroment.
New environmet have same hostname and ip address and version.(Ver4.4.2)
The document states that using the user "controller @ localhost" to import the data,
but I do not set the password for the user "controller@localhost" when installing.
It was possible to restore using user "root @ localhost".
What is the password for user "controller @ localhost"?
As I did, is the restore correct using the user "root @ localhost"?
>$install/db/bin/mysql -u controller -p<ControllerDBpassword> controller < metadata_dump.sql
https://docs.appdynamics.com/display/PRO44/Controller+Data+Backup+and+Restore
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can use the same "root" user through which you took the dump or you can use "controller" user with default password as "controller"(<ControllerDBpassword>).
Thanks
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can use the same "root" user through which you took the dump or you can use "controller" user with default password as "controller"(<ControllerDBpassword>).
Thanks
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
pratik.maskey
Thank you for your replay.
I understood!
Community Content Calendar, September edition
Splunkbase Unveils New App Listing Management Public Preview
Leveraging Automated Threat Analysis Across the Splunk Ecosystem
