Suppose recommended architecture is implemented with an installation of HVR on or near the source and destination data stores. In that case, the HVR executables will be sending data and changes over TCP/IP on the port of your choice. The hub installation of HVR always initiates the communication, which means that relative to the hub firewalls must be opened (on the port you select; default is 4343) to initiate connectivity. (i.e, if the hub resides on-premises and the target is in the cloud, then a firewall port must be opened to reach the cloud installation of HVR from the on-premises hub. If the hub resides in the cloud then the firewall must be opened to reach the on-premises server from the cloud instance.)If you set up HVR to use a remote database connection, then the database listener port must be open to allow the connection. HVR supports the use of a proxy server to route requests and act as an additional security buffer.
The HVR GUI is part of the standard HVR installation. If you install the HVR hub on-premises on a Windows server, you can run the HVR GUI there, too, and operate it using a remote desktop connection. Alternatively, you can install the HVR GUI on a PC (using the standard HVR installation) and connect with it to a hub running on any OS (Windows, Unix, etc.). The GUI is supported on Unix (X) too.
At present, the GUI does not run natively on a Mac. You must run a Windows or Linux-based virtual machine on a Mac, or use X-forwarding or a remote desktop to run the GUI on the Mac.
Yes, bi-directional SSL using custom-generated SSL public/private keys can be set up to secure data transfers.
HVR uses a distributed architecture. In any setup, one of the HVR installations must be nominated to be the hub. The architecture is flexible and modular, which means the hub can be collocated with the source, with the destination, or the hub can be running on its own server or virtual machine. The hub requires a connection to a database (the hub database). Setting up (real-time) data integration in HVR is done through a GUI connection with the hub. It is highly recommended to install HVR on the source database server and on or close to the target. Such a setup optimizes resource utilization and generally minimizes latency. In some cases, installing the source database server is a requirement to support log-based change data capture. This type of installation is called an HVR remote listener agent and acts like a child from the parent hub – no local configuration.
When you obtain a license from HVR you will be given access to software downloads on our website. All functionality of HVR is contained in a single product in one download and installation.
HVR will do most of the management tasks itself. Its robust communication will automatically recover from most errors. HVR can send alerts by email or SNMP if recovery takes too long or an unrecoverable error occurs. In the HVR GUI, graphs and reports are available on the past and current replication status.
Commonly-used operating systems are supported, including Linux and Windows, Solaris, AIX, and HP-UX (virtual or physical). On most of these, based on supported databases available on these platforms, HVR is available for 32 and 64-bit architectures.
A rich set of commonly-used sources and destinations is supported, including Oracle, SQL Server, and DB2 on commonly-used platforms. File systems including sftp and HDFS are supported as source and destination as well. For a complete overview, check the Platform Support page.
Tap into frequently searched expert notes, how-to articles, and error messages.
Download an HVR installation
HVR’s Documentation includes concepts, terminologies, requirements, architecture, and more.
Full on demand courses, as well as smaller How-To courses for the implementation, running and maintenance of HVR.