Dbvisit Standby version 10.0.x will only support Microsoft Windows 64bit Installations.
Note that Dbvisit Standby uses IPv4 and not IPv6 - if using hostnames in the configurations, you will need to make sure that they resolve to a valid IPv4 address. If not, using the IPv4 IP address should be used.
For Microsoft Windows Platforms the following is recommended:
Please make sure you test Dbvisit Standby in your Development or Test environment prior to implementation into production to ensure Virus Software, Firewall, UAC and Group policies do not affect the normal operation of Dbvisit Standby. |
The following Microsoft Windows versions (64bit) are supported (Base release including Service Packs are supported):
When using Windows-based systems, it is recommended not to make use of the Uniform Naming Convention (UNC) paths - example: \\server\share_name But to make use of local filesystem naming example: c:\folder_name\ |
Dbvisit Standby Supports the following Oracle Editions:
Please note that the primary and standby database server Oracle Editions must match! Having mixed Oracle Database Editions are not supported. |
The following Oracle Database versions are supported with Dbvisit Standby version 10.0.x:
The Oracle Database software version between primary and standby servers must match. Having different versions such as patch levels are not supported and can cause unexpected results if Graceful Switchover (GS) or Activation/Failover is attempted. |
The following features are not supported in 12.1 and above of Oracle
|
The following features are not supported in 12.1 and above of Oracle
|
The following advanced configurations are supported:
If using Oracle RAC configurations, using the latest patch sets are highly recommended. |
Important:
Dbvisit Standby version 8 and 9 had a different implementation for handling Oracle RAC configurations compared to version 7. There are a few important changes you must be aware off before you install the version 8 and 9 in an Oracle RAC configurations and it remains the same for Version 10:
In addition to the above mentioned, Dbvisit Standby version 10 supports the following options:
Dbvisit Standby version 10.0.x does not support the following configurations/options:
Dbvisit Standby is installed on all servers forming part of the Standby Database configuration.
The following system requirements are the minimum required for Dbvisit Standby installation:
Dbvisit Standby makes use of a Dbvisit Archive Destination referred to as ARCHDEST (on the standby server) and ARCSOURCE (on the primary server) This is used to store the archive logs shipped from the primary server to the standby server. This location is NOT the same as the database archivelog destination. This location should be big enough to keep at least 1 to 2 day's worth of archive logs, but the capacity to store three days or more is recommended. Example, if you generate 2GB worth of redo (archive logs) on the primary in one day, you should have at least 2GB as an absolute minimum free space on the standby in the folder specified as the ARCHDEST. |
If you are using ODA machines, It is required that you create the dbstorages before creating the standby databases using Dbvisit. Please refer the blog for further details. http://blog.dbvisit.com/configuring-dbvisit-standby-on-an-oda/ |
Dbvisit Standby supports two methods of communication between the primary and standby database servers:
It is important to make sure sufficient bandwidth is available to cater for your required Recovery Point Objective (RPO) as well as the Recovery Time Objective (RTO).
Dbvisit Standby can make use of compression (highly recommended) to ensure more effective use of bandwidth. Compression can be enabled either during network transfer (making use of Dbvnet compression / or SSH compression), or you can enable compression of Archive logs prior to being copied between the primary or standby servers.
It is recommended you test your network to make sure it can handle the required redo generation rate and that you do not have any network throttling such as packet shaping causing undesirable results affecting your RPO/RTO.
Ports that need to open for communication between Primary and Standby
IPV6 is not supported. Please, ensure you are using only IPV4 protocol. |
The following browsers are supported when using the Dbvisit Standby Web-Based interface:
Using the latest versions of the above list of browsers are recommended. It is important to note that it might be possible that certain browser configurations or add-on installations might limit or restrict the use of the Dbvisit Standby console. |
Dbvisit Standby is making use of the latest SSL versions.
From 9.x TLS1.2 and above is used.