You can find requirements for Dbvisit StandbyMP software installation on this page. There are requirements which common for all installation, and requirements which are platform specific (Windows / Linux) and also specific for each database platform.

You always need to fullfill all applicable requirements to your concrete installation at the same time. For example, if installing Dbvisit StandbyMP on Windows Oracle Server, you will need to fulfill Common Requirements, OS Platform Windows Requirements and Database Platform Oracle Requirements.

1. Common Requirements

These requirements must be satisfied for all Dbvisit StandbyMP installations.

1.1  Network

...

Communication Requirements

Dbvisit Standby Multiplatform has two components: dbvagentmanager (Agent) and dbvcontrol (Control Center). More information in Dbvisit StandbyMP concept: https://dbvisit.atlassian.net/wiki/spaces/DSMPV12/pages/4396875777/Introduction#2.-Dbvisit-StandbyMP-Components

...

1.2  Network Hostname Resolution Requirements

Dbvisit StandbyMP uses hostnames throughout the whole installation and database synchronization configruation. Usage of IP addresses is not recommended. You must verify that hostname resolution is equal on all hosts where you need to deploy Dbvisit. Hostname resolution can be tested by running:

ping <primary hostname>
ping <standby hostname>
ping <dbvcontrol hostname>

You need to run these commands on primary, standby and dbvcontrol server (if different from standby). The resolved IP addresses must match on all hosts. It is not required that the ping command receives response (for example Windows system prohibits ping by default).

In case you have not working DNS server or if resolved IP addresses differ, you must establish hostname resolution via hosts file on all hosts to correct this behavior.

Linux: /etc/hosts

Windows: C:\Windows\system32\drivers\etc\hosts

1.3  Storage Requirements

A. Storage Space Requirements

...

• CIFS is not supported for Dbvisit StandbyMP deployment

1.

...

4  CPU and Memory Requirements

...

1.

...

5  Dbvcontrol Webserver Browser Requirements

We recommend and support Chrome Browser for accessing dbvcontrol. However, other browsers such as Edge or Firefox will work as well. In case of any observed issues, we recommend to switch to Chrome Browser.

1.

...

6  SMTP Server Requirements

Dbvisit StandbyMP uses SMTP server client to send notifications (which are optional). To use the notification feature, it is necessary that dbvcontrol component has direct access to SMTP Server.

...

Dbvisit StandbyMP supports following SMTP server communication protocols: StartTLS ,TLS/SSL or NoEncryption.

2. OS Platform

...

Requirements

These requirements must be satisfied When installing Dbvisit StandbyMP on specific OS platform (Windows/Linux).

...

Following is a list of Linux platform specific requirements.

• Default installation directory is /usr/dbvisit (this can be modified during installation)

• We recommend to installing Dbvisit StandbyMP as same OS user which runs Database Engine (oracle, postgres …)

• If you have dedicated mount for /tmp, make sure it is NOT mounted with “noexec” option. This can be verified with for example “mount -l” command.

• After the Dbvisit StandbyMP installation, user can choose to create systemctl service for dbvagentmanager and dbvcontrol to automate startup. In this case, root access will be required to start and stop these components.

• SELINUX must be set to disabled or permissive. In Enforcing mode SELINUX will prevent dbvagentmanager and dbvcontrol services from working correctly. You can find out the status by running:

...

Chronyd and ntpd services will ensure system date correct synchronization. If system date is not synchronized, there can be issues with connection issues because of certificates validity (which is based on actual date).

2.2  Windows

When installing Dbvisit StandbyMP onto a Windows environment, user account is required to run the msi installer file and perform the setup. During installation you will be prompted for another username which will be user for installing dbvagenmanager Windows Service. They can be different accounts, but you can also use same account for both actions.

A. User performing Installation

This can be any account (for example named user) who will perform Dbvisit StandbyMP software installation.

• The User performing installation of Dbvisit Standby may be a local or a domain user who is part of Local Administrators group

• Default installation directory is C:\Program Files\Dbvisit (this can be modified during installation). User running the Dbvisit installation will assume ownership of installation directory C:\Program Files\Dbvisit

B. Dbvisit StandbyMP User specified during installation

During Dbvisit StandbyMP installation you will be prompted for username and password. This user will be used for running Dbvisit StandbyMP dbvagentmanager service and will be interacting directly with the database engine.

• This user needs to be local or a domain user who is part of Local Administrators group

• This user needs to be granted the "Log On As Service" policy to allow the user to run the Dbvisit Standby Services. To grant, run from command line:

secpol.msc

And afterwards add user:

...

• This user must have complete privileges to interact with the database Engine present on the server

C. Other Requirements

• For installation It is recommended that User Account Control be turned off - not strictly required, but highly recommended.

• For the duration of installation it is recommended to turn of any 3rd party antivirus software (excluding Windows Defender). It can be enabled again after installation is completed, if whole Dbvisit installation directory is whitelisted and excluded from scan

3. Database Platform Requirements

Below you will find requirements specific for individual database platform. There are different requirements for Windows and Linux platforms.

3.1  Oracle

A. Linux

• We strongly recommend to use user who was used for oracle home installation (typically oracle) for installation of Dbvisit StandbyMP prouct

• Installation user must have same user id and group id on primary and standby server:

[oracle@czlin0231 ~]$ id
uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall),54322(dba),54323(oper),54324(backupdba),54325(dgdba),54326(kmdba),54330(racdba)

B. Windows

• User who is selected to run Dbvisit StandbyMPdbvagentmanager service during installation must be member of following groups:

ora_dba
Local Administrators
Oracle Home DBA group - (if using 12c make sure the user is in the new Oracle Home DBA group)

C. Common

• Dbvisit StandbyMP doesn’t require Oracle Listener for its operation

• When installing Dbvisit StandbyMP on RAC or SEHA environments, additional prerequisites must be fulfilled. See Oracle RAC and SEHA documentation for further details: <<<< TBD >>>>>

• ORACLE_HOME system-wide environment variable must be set to existing oracle home software location

• PATH system-wide environment variable must include ORACLE_HOME\bin directory

3.2  SQL Server

A. Linux

• It is required to Install Dbvisit StandbyMP product as user who is used for runnning SQL Server instance

B. Windows

• We recommend to not specify any user for Dbvisit StandbyMPdbvagentmanager service (so as the installed dbvagentmanager service runs as Local System)

3.3  Postgres

A. Linux

• It is required to Install Dbvisit StandbyMP product as user who is used for runnning Postgres database cluster

B. Windows

• We recommend to not specify any user for Dbvisit StandbyMPdbvagentmanager service (so as the installed dbvagentmanager service runs as Local System)