Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page describes the installation process of Dbvisit StandbyMP on Linux and Windows platforms.

You must review & complete all Installation Requirements prior to starting installation: Installation Requirements

1. Linux

Note

Never use root user for Installation of Dbvisit StandbyMP on Linux

...

Info

There is no specific required sequence to install dbvagentmanagers and dbvcontrol. For example it doesn’t matter if you install first dbvcontrol on separate host, or if you first install primary dbvagentmanager.

You can choose any sequence for installing Dbvisit StandbyMP components which suits you best.

Table of Contents
stylenone

1. Linux

Note

Never use root user for Installation of Dbvisit StandbyMP on Linux

Note

This installation procedure is not valid for Oracle RAC and SEHA environments. Refer to <<TBD>> instead

...

1.1

...

 Create a "Dbvisit Base" Directory

  • This step needs to be done on primary, standby and dbvcontrol server (if different from standby server).

...

The ownership of the directory needs to be changed to the user who will install and run Dbvisit (Oracle/SQLServer/Postgres Database software owner). 

...

1.2

...

 Download and Extract Latest Software

  • This step needs to be done on primary, standby and dbvcontrol server (if different from standby server).

...

Code Block
-rwxr-xr-x. 1 oracle oinstall 188106709 Jan 28 09:54 install-agent-v12.1
-rwxr-xr-x. 1 oracle oinstall  64448219 Jan 28 09:52 install-control-v12.1

...

1.3

...

Install Dbvisit StandbyMP dbvagentmanager

  • This step needs to be done on primary and standby server only

...

Expand
titleOutput
Code Block
[oracle@czlin0231 mp]$ ./install-agent-v12.1.0DEV-49-ga7643cd35
+----------------------------------------------------------------------+
|          ____  _                  _ _           __  __ ____          |
|         / ___|| |_ __ _ _ __   __| | |__  _   _|  \/  |  _ \         |
|         \___ \| __/ _' | '_ \ / _' | '_ \| | | | |\/| | |_) |        |
|          ___) | || (_| | | | | (_| | |_) | |_| | |  | |  __/         |
|         |____/ \__\__,_|_| |_|\__,_|_.__/ \__, |_|  |_|_|            |
|          Copyright 2024                   |___/   By Dbvisit         |
+----------------------------------------------------------------------+

Welcome to Dbvisit StandbyMP setup version v12.1.0DEV-49-ga7643cd35.

? Please carefully read the end-user license agreement at https://dbvisit.com/eula. Do you agree to the terms of this agreement? Yes
? Which directory should the software be installed into? /usr/dbvisit

- - - You are now configuring the Dbvisit StandbyMP Agent - - -

The Agent will listen on the following discovered addresses:
 -  127.0.0.1
 -  10.0.2.15
 -  192.168.8.231
? Agent File Transfer Port: 7890
? Fully Qualified Domain Name for this host: czlin0231
? Fully Qualified Domain Name for the Control Center: czlin0232
? Agent Communications Port: 5533
Each Dbvisit StandbyMP Agent and the Dbvisit StandbyMP Control Center must
be configured with the same passphrase. This is how we know that they are all
intended to be part of the same system. Please specify a strong passphrase - we
suggest at least 12 characters, containing at least 2 numbers and 2 symbols.
? Passphrase: *
? Confirm Passphrase: *

- - - Dbvisit StandbyMP Agent configuration finished - - -


- - - Ready to perform installation - - -

? Do you wish to proceed with the setup using the supplied configuration options? Proceed with setup

- - - Performing installation - - -

Copying software files to '/usr/dbvisit'...
Writing Agent configuration file '/usr/dbvisit/standbymp/conf/dbvagentmanager.ini'...

- - - File creation complete - - -


- - - Configuration Summary - - -

Install Directory:                                  /usr/dbvisit
Fully Qualified Domain Name for this host:          czlin0231
Fully Qualified Domain Name for the Control Center: czlin0232
Agent Communications Port:                          5533
Agent File Transfer Port:                           7890

- - - Installation Summary - - -

The following actions have been performed:
 -  Installed Dbvisit StandbyMP Agent software into: /usr/dbvisit/standbymp
 -  Agent settings are available in the configuration file: /usr/dbvisit/standbymp/conf/dbvagentmanager.ini
 -  Generated new security certificates in: /usr/dbvisit/standbymp/certificates

- - - INSTALLATION SUCCESSFUL - - -


To enable the installed Dbvisit StandbyMP components to run as system services, you will need to execute some commands as the "root" user in order to complete the setup.

To install the system service(s), you can run, substituting the name of the user to run as if it is different from the current user:
        sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service install --user oracle
To start the system service(s), you can run:
        sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service start

Directly after the installation of dbvagentmanager is finished, you have the option to create dbvagentmanager systemctl service by copying and running the last lines in the installer output:

Code Block
sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service install --user oracle
sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service start

Creating systemctl service for dbvagentmanager will ensure dbvagentmanager will automatically startup after server reboot.

1.4 Install Dbvisit StandbyMP dbvcontrol

  • This step needs to be done on server where you intend to install dbvcontrol (separate host or standby server).

You can start the installation by running in install-control file:

Code Block
cd /tmp/dbvisit
./install-control-v12.1

You will need to respond to following prompts during installation:

Info

When installing dbvcontrol on standby server, choose same dbvisit base as you’ve chosen for dbvagentmanager, do not separate dbvcontrol installation from dbvagentmanager

Prompt

Example Value

Comment

Please carefully read the end-user license agreement at https://dbvisit.com/eula. Do you agree to the terms of this agreement?

Yes

Installation will proceed only with response “Yes”

Which directory should the software be installed into?

/usr/dbvisit

Dbvisit Base directory you prepared earlier

Control Center Web Server Port: (4433)

There’s usually no need to change the port, press enter to accept suggested value.

Agent Communications Port: (5533)

There’s usually no need to change the port, press enter to accept suggested value.

Passphrase:

Admin123

passphrase used for encrypting communication between dbvagentmanagers and dbvcontrol. Must match on all hosts. There is no complexity requirement.

Example output of installation:

Expand
titleOutput
Code Block
[oracle@czlin0231 mp]$ ./install-control-v12.1.0DEV-49-ga7643cd35
+----------------------------------------------------------------------+
|          ____  _                  _ _           __  __ ____          |
|         / ___|| |_ __ _ _ __   __| | |__  _   _|  \/  |  _ \         |
|         \___ \| __/ _' | '_ \ / _' | '_ \| | | | |\/| | |_) |        |
|          ___) | || (_| | | | | (_| | |_) | |_| | |  | |  __/         |
|         |____/ \__\__,_|_| |_|\__,_|_.__/ \__, |_|  |_|_|            |
|          Copyright 2024                   |___/   By Dbvisit         |
+----------------------------------------------------------------------+

Welcome to Dbvisit StandbyMP setup version v12.1.0DEV-49-ga7643cd35.

? Please carefully read the end-user license agreement at https://dbvisit.com/eula. Do you agree to the terms of this agreement? Yes
? Which directory should the software be installed into? /usr/dbvisit

- - - You are now configuring the Dbvisit StandbyMP Control Center - - -

The Control Center will listen on the following discovered addresses:
 -  127.0.0.1
 -  10.0.2.15
 -  192.168.8.231
? Control Center Web Server Port: 4433
? Agent Communications Port: 5533
Each Dbvisit StandbyMP Agent and the Dbvisit StandbyMP Control Center must
be configured with the same passphrase. This is how we know that they are all
intended to be part of the same system. Please specify a strong passphrase - we
suggest at least 12 characters, containing at least 2 numbers and 2 symbols.
? Passphrase: *
? Confirm Passphrase: *

- - - Dbvisit StandbyMP Control Center configuration finished - - -


- - - Ready to perform installation - - -

? Do you wish to proceed with the setup using the supplied configuration options? Proceed with setup

- - - Performing installation - - -

Copying software files to '/usr/dbvisit'...
Writing Control Center configuration file '/usr/dbvisit/standbymp/conf/dbvcontrol.ini'...

- - - File creation complete - - -


- - - Configuration Summary - - -

Install Directory:              /usr/dbvisit
Control Center Web Server Port: 4433
Agent Communications Port:      5533

- - - Installation Summary - - -

The following actions have been performed:
 -  Installed Dbvisit StandbyMP Control Center software into: /usr/dbvisit/standbymp
 -  Control Center settings are available in the configuration file: /usr/dbvisit/standbymp/conf/dbvcontrol.ini
 -  Generated new security certificates in: /usr/dbvisit/standbymp/certificates

- - - INSTALLATION SUCCESSFUL - - -


To enable the installed Dbvisit StandbyMP components to run as system services, you will need to execute some commands as the "root" user in order to complete the setup.

To install the system service(s), you can run, substituting the name of the user to run as if it is different from the current user:
        sudo /usr/dbvisit/standbymp/bin/dbvcontrol service install --user oracle
To start the system service(s), you can run:
        sudo /usr/dbvisit/standbymp/bin/dbvcontrol service start

Directly after the installation of dbvagentmanager is finished, you have the option to create dbvagentmanager systemctl service by copying and running the last lines in the installer output:

Code Block
sudo /usr/dbvisit/standbymp/bin/dbvcontrol service install --user oracle
sudo /usr/dbvisit/standbymp/bin/dbvcontrol service start

Creating systemctl service for dbvcontrol will ensure dbvcontrol will automatically startup after server reboot.

2. Windows