Installation
- Jan Klinke
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
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. We recommend to start with dbvcontrol, continue to standby dbvagentmanager and as final step primary dbvagentmanager.
1. Linux
Never use root user for Installation of Dbvisit StandbyMP on Linux
This installation procedure is not valid for Oracle RAC and SEHA environments. Refer to Oracle SEHA and RAC on Linux instead
You need to comply to and take into account all installation prerequisites: Installation Requirements
1.1 Create a "Dbvisit Base" Directory
This step needs to be done on primary, standby and dbvcontrol server (if different from standby server).
This step is the only exception where we will need to use root privileges. The default location is /usr/dbvisit. You can specify any location you need as long as has enough free space (see Installation Requirements ). Following commands can be used to create installation directory:
sudo mkdir /usr/dbvisit
sudo chown oracle:oinstall /usr/dbvisitThe 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).
The latest available version can be downloaded from the Dbvisit web site https://www.dbvisit.com
Once the software is downloaded, you can upload / copy it to a temporary location on your server, do not use Dbvisit Base location. Make sure the ownership of the file is set to the same user who owne Dbvisit Base:
mkdir /tmp/dbvisit
cd /tmp/dbvisit
# now upload files
chown oracle:oinstall /tmp/dbvisit/standby-v12.1.tar.gz
tar -xzf standby-v12.1.tar.gzVerify you can now see two installer files:
-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.11.3 Install Dbvisit StandbyMP dbvagentmanager
This step needs to be done on primary and standby server only
You can start the installation by running in install-agent file:
cd /tmp/dbvisit
./install-agent-v12.1You will need to respond to following prompts during installation:
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 |
Agent File Transfer Port: (7890) |
| There’s usually no need to change the port, press enter to accept suggested value |
Fully Qualified Domain Name for this host: [? for help] (czlin0231) | czlin0231 | hostname (including domain name or not) of your primary server. Hostname must be resolvable into valid IPv4 address and such interface needs to be present on the host |
Fully Qualified Domain Name for the Control Center: | czlin0232 | hostname (including domain name or not) where you will install your dbvcontrol. Hostname must be resolvable into valid IPv4 address. It is not required for controlcenter to be installed / running at this point. |
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 complete output of installation:
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:
sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service install --user oracle
sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service startCreating 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:
cd /tmp/dbvisit
./install-control-v12.1You will need to respond to following prompts during installation:
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 complete output of installation:
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:
sudo /usr/dbvisit/standbymp/bin/dbvcontrol service install --user oracle
sudo /usr/dbvisit/standbymp/bin/dbvcontrol service startCreating systemctl service for dbvcontrol will ensure dbvcontrol will automatically startup after server reboot.
Once dbvcontrol is installed and started, you can verify accessibility by going to following URL:
https://<control center hostname>:4433default username and password is: admin/admin
2. Windows
This installation procedure is not valid for Oracle SEHA environments. Refer to Oracle SEHA on Windows instead
You need to comply and take into account all installation prerequisites: Installation Requirements
Windows installation uses .msi installer file and provides a guided process for installing Dbvisit StandbyMP on your Windows machine.
Each dbvcontrol and dbvagentmanager installer run is logged into directory C:\Users\<username who runs the .msi installer>\AppData\Local\Temp\<x>. You can review or upload this file for Dbvisit Support in case of any issues.
2.1 Download and Extract Latest Software
This step needs to be done on primary, standby and dbvcontrol server (if different from standby server).
The latest available version can be downloaded from the Dbvisit web site https://www.dbvisit.com. Once the file is downloaded, extract it to temporary directory (in this case C:\tmp) to get two .msi installer files:
2.2 Install Dbvisit StandbyMP dbvagentmanager
Run installer file agent-v12.x.x to install dbvagentmanager on local server.
Click Next in the very first step:
You must accept EULA (1) in order for installation to proceed (2):
On the next screen, you specify dbvagentmanager configuration:
Number | Description | Example Value | Comment |
|---|---|---|---|
1 | Fully Qualified Domain Name for this host | CZWIN0191 | hostname (including domain name or not) of your primary server. Hostname must be resolvable into valid IPv4 address and such interface needs to be present on the host |
2 | Fully Qualified Domain Name for the Control Center | CZWIN0192 | hostname (including domain name or not) where you will install your dbvcontrol. Hostname must be resolvable into valid IPv4 address. It is not required for controlcenter to be installed / running at this point. |
3 | User Domain, User, Password | acme, oracle, tiger123 | This user will be used for running Dbvisit StandbyMP dbvagentmanager service and will be interacting directly with the database engine. See Installation Requirements | 2.2 Windows for details how to choose this account. If you want to use local user only, leave the domain name blank. You can leave all these three fields empty to install dbvagentmanager to be run as “Local System” |
4 | Agent Communications Port | 5533 | There’s usually no need to change the port, press enter to accept suggested value. Port on which the dbvagentmanager will contact dbvcontrol |
5 | Agent File Transfer Port | 7890 | There’s usually no need to change the port, press enter to accept suggested value. Port on which the dbvagentmanager will listen on this server |
6 | The Agent will listen on the following discovered addresses | 10.0.2.15,192.168.8.205,127.0.0.1 | List of interfaces with their IP addresses discovered on the host |
7 | Next |
| Continue to next step |
You need to confirm by clicking Next that the hostname you entered in field “1” is resolvable into local interface IPs listed in field “6”:
In the next step, you need to specify the passphrase (1) and continue (2):
The passphrase is used for encrypting communication between dbvagentmanagers and dbvcontrol. It must match on all hosts. There is no complexity requirement.
On the following screen you are able to change default location for Dbvisit StandbyMP installation:
On the final screen, you need to click Install to start the installation or you can go Back to change any setting you entered:
Once the installation completes, you will be able to close the installer(1):
You will also see the installer log file location (2).
After the dbvagentmanager installation, you will be able to see dbvagentmanager service in the service list. You can view the list by runing services.msc:
You can change the Logon user for this service as well as change the startup type if needed.
2.2 Install Dbvisit StandbyMP dbvcontrol
The dbvcontrol installation is more straightforward as the dbvagentmanager installation. Run installer file control-center-v12.x.x to install dbvcontrol on local server. On the frist screen click on Next:
You must accept EULA (1) in order for installation to proceed (2):
On the next screen you can modify dbvcontrol configuration:
Dbvcontrol is not dependent on the hostname and dbvcontrol service will be always run as “Local System” and that is why the configuration is much simpler than dbvagentmanager:
Number | Description | Example Value | Comment |
|---|---|---|---|
1 | The Control Center will listen on the following discovered addresses | 10.0.2.15,192.168.8.205,127.0.0.1 | List of interfaces with their IP addresses discovered on the host |
2 | Control Center Web Server Port | 4433 | Port on which you will be able to access the dbvcontrol webserver interface as per: |
3 | Agent Communications Port | 5533 | There’s usually no need to change the port, press enter to accept suggested value. Port on which the dbvcontrol will accepts connections from dbvagentmanagers |
4 | Next |
| Continue to next step |
In the next step, you need to specify the passphrase (1) and continue (2):
The passphrase is used for encrypting communication between dbvagentmanagers and dbvcontrol. It must match on all hosts. There is no complexity requirement.
On the following screen you are able to change default location for Dbvisit StandbyMP installation:
On the final screen, you need to click Install to start the installation or you can go Back to change any setting you entered:
Once the installation completes, you will be able to close the installer(1):
You will also see the installer log file location (2).
After the dbvcontrol installation, you will be able to see dbvcontrol service in the service list. You can view the list by runing services.msc:
You can change the Logon user for this service as well as change the startup type if needed.
3. Batch Installation
It is possible to perform fresh installation of Dbvisit components in batch mode if needed for automation. Upgrade in batch mode is not possible.
3.1 Linux
You can run dbvagentmanager and dbvcontrol installer in batch mode using “-batch” switch. Each installer has different parameters and only non-default parameters (marked as “required to specify”) are needed.
Complete set of dbvagentmanager batch installation parameters for Linux:
-agent-communications-port int
Agent communications port number (default 5533)
-agent-file-transfer-port int
Agent file transfer port number (default 7890)
-control-center-address string
host address of the Control Center (required to specify)
-default-backup-dir string
default directory for SQL Server backup files (default value determined by $install-dir/standbymp/backup)
-host-address string
resolvable address of this host (default value determined by hostname)
-install-dir string
base directory to install into (default value /usr/dbvisit)
-passphrase string
passphrase used to secure communication between Agents and Control Center (required to specify)Complete set of dbvcontrol parameters is:
-agent-communications-port int
Agent communications port number (default 5533)
-install-dir string
base directory to install into (default /usr/dbvisit)
-passphrase string
passphrase used to secure communication between Agents and Control Center (required to specify)
-web-server-port int
Control Center web server port number (default value 4433)Example batch installation commands:
./install-agent-v12.1 -batch -install-dir /usr/dbvisit -host-address czlin0231 -control-center-address czlin0232 -passphrase a
./install-control-v12.1 -batch -passphrase Admin123You will need to create / start systemctl services same as when performing manual installation
3.2 Windows
Batch installation for Windows has different syntax than on Linux due to the fact that we’re using msi installer. The batch installation can be run by specifying /quiet switch together with specific parameters. Here’s complete set of dbvagentmanager batch installation parameters for Windows with example values:
INSTALLDIR="C:\Program Files\Dbvisit"
base directory to install into (default value C:\Program Files\Dbvisit)
DEFAULTBACKUPDIR="C:\Program Files\Dbvisit\standbymp\backup"
default directory for SQL Server backup files (default value determined by $install-dir\standbymp\backup)
AGENTMANAGERDOMAIN="."
Domain for User account who will run dbvagentmanager Windows Service (default empty: service is then created as "Local System")
AGENTMANAGERACCOUNT="Administrator"
User account who will run dbvagentmanager Windows Service (default empty: service is then created as "Local System")
AGENTMANAGERPASSWORD="abc"
passphrase used for User account who will run dbvagentmanager Windows Service (default empty: service is then created as "Local System")
HOSTADDRESS=czwin0191
resolvable address of this host (default value determined by hostname)
PASSPHRASE=Admin123
passphrase used to secure communication between Agents and Control Center (required to specify)
FTLISTENPORT=7890
Agent file transfer port number (default 7890)
NATSPORT=5533
Agent communications port number (default 5533)
NATSADDRESS=czwin0192
host address of the Control Center (required to specify)specifying “.” for AGENTMANAGERDOMAIN means local user will be used
Complete set of dbvcontrol batch installation parameters for Windows with example values:
INSTALLDIR="C:\Program Files\Dbvisit\standbymp"
base directory to install into (default value C:\Program Files\Dbvisit)
WEBLISTENPORT=4433
Control Center web server port number (default value 4433)
NATSLISTENPORT=5533
Agent communications port number (default 5533)
PASSPHRASE=Admin123
passphrase used to secure communication between Agents and Control Center (required to specify)Example batch installation commands:
agent-v12.1.msi /quiet AGENTMANAGERDOMAIN="." AGENTMANAGERPASSWORD="AdminUpwd" AGENTMANAGERACCOUNT="Administrator" PASSPHRASE=Admin123 NATSADDRESS=czwin0192
agent-v12.1.msi /quiet PASSPHRASE=Admin123 NATSADDRESS=czwin0192
control-center-v12.1.msi /quiet PASSPHRASE=Admin123note that although the .msi /quiet command itself will be immediately completed, the installation will run in background and take some time to complete