Reconfiguring An Adm Deployment; Adding A Remote Database To An Existing Adm Deployment; Converting A Single-Box Or Aggregator To A Remote Database - VMware VCENTER APPLICATION DISCOVERY MANAGER 6.1.1 Administration Manual

Application Discovery Manager Administration Guide
15 Place the copied files to:
/tmp/adkb/custom
16 Overwrite any files or folders in the destination directory if prompted to do so.
17 Type the following command to check in the custom fingerprints:
/home/nlayers/Seneca/management/APIs/InSight_control.sh adkb --checkin /tmp
18 Type the following adm_control.pl command to restart the relevant services:
/home/nlayers/Seneca/Control/bin/adm_control.pl --restart all
N Distributed deployment: Repeat Step 1 through Step
OTE
deployment.

Reconfiguring an ADM Deployment

You can reconfigure deployment of physical IBM all‐in one, Aggregator and database appliances as follows:

"Adding a Remote Database to an Existing ADM Deployment" on page 38

"Converting a Single‐Box or Aggregator to a Remote Database" on page 38. Note important restrictions.

"Moving a Database to a Remote Appliance" on page 39
Virtual components must be redeployed as described in "Installing ADM" on page 15.

Adding a Remote Database to an Existing ADM Deployment

To add a remote database to the ADM deployment
1 Ensure that all components are running ADM version 6.0 or later before adding the remote database to
your ADM deployment. All appliances must be on the same version.
2 If you have an existing database, back it up using the steps described in "Product Support Packages" on
page 34.
3 After ensuring that all components are running the same ADM version, follow the instructions described
in "Upgrading Appliances" on page 42.
4 Restore the backed‐up database to the new database appliance as described in "Restore the ADM
Database" on page 36.

Converting a Single-Box or Aggregator to a Remote Database

Beware of the following before converting an existing component to a remote database:
C You cannot restore the data from a component that you are converting. All of the data on the
AUTION
Single‐Box or Aggregator component that you are converting to a remote database is lost during conversion.

You can only convert an Aggregator component that is not part of the ADM deployment into a remote
database. For example, if you have an Aggregator appliance that you are using in a test environment, and
another that you are using in your production environment, you can convert the test component into a
remote database.

You can convert an Aggregator component into a remote database when you already have more than one
Aggregator appliance.

You can convert an appliance that is running an Single‐Box setup into a remote database.
To convert the component to a remote database
1 Setup the database appliance as described in the "ADM Setup Procedures" on page 23.
2 Log in to the database appliance as user root.
38
18 for each collector in the ADM
VMware, Inc.