The Revelation Universal Driver Heavy (UDH) may be the most important product used to protect your Revelation data. The UDH is client/server software designed to allow real time mirroring of your Revelation data. It is designed to handle intensive Revelation applications that need to scale up and have high availability. UDH permits real-time mirroring of Linear Hash data.
The current release is UDH v4.7.2 - The UDH 4.7.2 is a minor upgrade from UDH 4.7. It resolves a significant issue with corrupted table header counts and sizes, a potential memory leak/overrun issue when running in 'debug output' or logging mode, and eliminates "hanging" when shutting down the service. This should allow sites to terminate and restart the UDH without requiring a server reboot.
The Universal Driver Heavy can only be installed on servers running the following versions of Windows:
Server 2003 32-bit & 64-bit
Server 2008 32-bit & 64-bit
Server 2012 (non-core)
Supported workstations are:
Windows 10 32-bit & 64-bit
Windows 8 32-bit & 64-bit
Windows 7 32-bit & 64-bit
Two servers are required, one will be the primary server and the other a secondary server for mirrored data. The minimum hardware requirements for both servers are:
Physical or virtual server
100/1000 MB LAN with 1 MS > latency between servers.
4 GB RAM
Xeon or Opteron class CPU with 2 cores.
Low latency disk access with high 4 KB random IOPS such as an enterprise capable RAID controller with on battery backup disk cache, SSD drives, SAS drives, or SAN with caching.
Both servers must have local disks with identical drive letter settings.
Please Read the Universal Driver Heavy FAQ below:
Universal Driver Heavy FAQ
What is the Universal Driver Heavy?
The UDH is client/server software designed to allow real time mirroring of your Revelation data. It is designed to handle intensive Revelation applications that need to scale up and have high availability. UDH permits real-time mirroring of Linear Hash data.
Has it been tested on 64-bit platforms?
The UDH 4.7 has been tested and approved to be installed on Windows 64-bit server platforms.
Is the secondary backup maintained continuously (every time a record is written), or does the backup to the secondary server only occur on a timed basis(once per hour or day), or is it manually initiated?
You can do all three of these things.
Could switching to the backup server occur automatically and seamlessly when an interruption occurs on the primary server, or would the switchover have to be manually imitated? Could the UDH automatically switch between servers on a timed basis to periodically test the readiness of the backup server and detect switching problems?
At this time, the switchover cannot be done automatically. There are one or two small changes that need to be made to the mirrored copy of OI before it can go live. So, no, it cannot automatically switch between servers on a timed basis.
Is the backup server (database) an exact duplicate of the primary? If switching is necessary, are there any data or file compatibility issues between the databases?
It is almost an exact duplicate. Because the mirror copy of OI is not running, there are one or two steps mentioned above that need to be performed. They include copying over .DBTs - more common in a development environment, as well as confirming the tables are attached - which will update the index definitions. Aside from that, there should be no data or file compatibility issues.
User Locks: Can User Locks be freed-up without affecting anything else on the system? Eliminate resetting the server? Could User Lock management be set up to automatically log out an RDS that was open for >an extended period of time (>20 min.)?
Locks can be freed up without affecting anything else on the system - this is done with an included LH Server Manager Console. It will eliminate resetting the server. As is, the User Lock management does not have the capability to automatically log out a lock that has been open for an extended period. You may be able to do this within the Console, as it is a limited development copy of OI.
Will the UDH impact indexer cycle time or in some other way impact the access speed of the system?
It should not impact indexer cycle time. In one of our tests, while in development mode and running on a TS server, there was some occasional delay in the application. The Mirror server was two switches and over forty meters of patch cable away. We have not seen this delay on other tests, and have not heard any reports of speed being affected from our beta testers.
Any integration issues to existing copies of OI?
You will need to run the client installation. You may need to allow access to the Database Manager module from your runtime to allow the mirror to attached the tables as mentioned above.
Is the UDH compatible with our current version of OpenInsight? What about when we perform OpenInsight upgrades in the future?
The UDH is compatible with OI 4.1.x and above. It will handle upgrades in the future as well.
What impact is there to install the UDH software? System downtime? Support available?
Should be minimal impact to install. It should not entail system downtime - though anticipate making OI inaccessible to your users while configuring. Support is included in the price.
What is the purchase price of the software? Is this a one-time fee?
Price of the software is $15,000. There is a 20% annual fee, which includes all upgrades and support.