| Table of Contents | ||||
|---|---|---|---|---|
|
1. Dbvisit Standby
...
Concept
...
Dbvisit Standby
...
The Dbvisit standby has two main components:
...
It is important to note that the user running Dbvisit on Unix-based systems MUST be the same user used to install and run the Oracle/SQLServer Database software. But, the services are stopped and started using the root user.
On Windows-based systems
...
The installation for Oracle-based systems does not have to be the same user as the Oracle Home Owner, but MUST be in the ORA_DBA and Local Administrators group with "Log on as a service" permission.
...
product manages the complete lifecycle (creation, synchronization, activation and more) of standby database for Oracle, SQL Server and Postgres database platforms with RPO and RTO measured in minutes.
Dbvisit uses very similar concept for standby database synchronization for Oracle, SQL Server and Postgres.
Oracle concept:
| Info |
|---|
Oracle Standby database is in MOUNT status during synchroniation. It can be opened READ-ONLY, but in this state, apply of archivedlogs is paused |
SQL Server concept:
...
| Info |
|---|
Similar to Oracle, SQl Server Standby database is in RESTORING status during synchroniation. It can be opened READ-ONLY, but in this state, apply of archivedlogs is paused |
Postgres Streaming concept:
...
| Info |
|---|
Dbvisit Standby allows to create Postgres Standby cluster in HOT mode (read-only access is possible during synchronization) or WARM mode (read-only access can’t be obtained). |
| Info |
|---|
For postgres platform, Dbvisit offers also support for WAL shipping. |
| Note |
|---|
For Dbvisit Standby, there’s no requirement for shared storage between primary and standby server. This goes for all three database platforms. |
2. Dbvisit Standby Components
Dbvisit Standby must be installed directly on primary and standby database servers, it’s not possible to deploy it to environment without direct operating system access.
There are two main components for Dbvisit Standby MultiPlatform:
dbvagentmanager (Dbvisit Agent) | This component should be installed once on each database server. The Dbvisit Agent is responsible for connecting to the Oracle and/or SQL Server databases, and communicating with the Dbvisit Control Center. |
dbvcontrol (Dbvisit Control center/GUI) | This component should be installed once only, ideally on a 3rd server separate from either the primary or standby database server. It is also possible to install this on the standby server. The Dbvisit Control Center contains the communication hub, logic center, the user interface, and the Observer. In simple terms, the Control Center is the brains behind the operation - it is through the Control Center that you will interact with the product the vast majority of the time. |
Example architecture with 2 primary and 2 standby database servers with separate host for dbvcontrol:
...
2. Dbvisit Standby MultiPlatform Directory Structure.
The following are the directory structure for Dbvisit Standby Multiplatform. The default location for Unix based system is /usr/dbvisit and for Windows, it's c:\Program Files\Dbvisit. It is however recommended to install the dbvcontol or the Control Center to be installed on a separate machine and not on the database servers.
...
Unix Based Systems (Dbvagentmanager)
...
Windows Based Systems(Dbvagentmanager)
...
| Code Block | ||
|---|---|---|
| ||
/usr/dbvisit/standbymp
├── backup
├── bin
├── certificates
├── conf
├── db
├── dbvnet
│ ├── conf
│ └── log
├── log
└── oracle
├── backup
├── conf
├── doc
├── gs
├── lib
├── log
├── meta
├── pid
├── snap
├── support
├── tmp
└── trace |
...
| Code Block |
|---|
C:\Program Files\Dbvisit\standbymp>tree
├───backup
├───bin
├───certificates
├───conf
├───db
├───dbvnet
│ ├───conf
│ └───log
├───log
└───oracle
├───backup
├───conf
├───doc
├───gs
├───log
├───meta
├───pid
├───snap
├───support
└───tmp |
...
Unix Based Systems(dbvcontrol)
...
Windows Based Systems(dbvcontrol)
...
| Code Block |
|---|
/usr/dbvisit
├── standbymp
│ ├── backup
│ ├── bin
│ ├── certificates
│ ├── conf
│ ├── db
│ └── log
└── upgradeBak |
...
It is important to note that the user running Dbvisit components on Unix-based systems MUST be the same user used to install and run the Oracle/SQLServer Database software. But, the services are stopped and started using the root user.
On Windows-based systems, the installation user for Dbvisit components does not have to be the same user as the Oracle Home Owner, but MUST be in the ORA_DBA and Local Administrators group with "Log on as a service" permission.
| Info |
|---|
Dbvisit installation is very small (~ 500MB), but we require and recommend to have at least 10GB of free space per server for tracefiles and Dbvisit internal repositories. |
3. Using Dbvisit Standby
After the installation of the Dbvisit Standby MultiPlatform, you are recommended to use the central console for creating configurations for Oracle/SQLServer. Once the configuration is created you should be able to set your DR databases.Please ensure you have reviewed the Release notes as well as system requirements and pre-requisiteswill be able to use four user interfaces:
dbvcli (command line tool)
dbvctl (Oracle database platform specific command line tool)
API
Webserver GUI (provided by dbvcontrol)
Each installation and deployment of Dbvisit by default and always contains all four methods. You’ll be free to switch among using all four interfaces after installation freely.