D3
Hot
Backup FAQ
The Hot Backup system for the D3 AIX and D3 Linux platforms can be an integral part of your overall technology strategy. Below are some common questions regarding Raining Data’s Unix backup solution for uninterrupted operation.
| Q. |
Why would I need a solution for uninterrupted operation? |
| A.
|
Today’s focus is on security and protecting data against business interruptions of any kind. Where system failure is a major concern, it is very important to incorporate IT strategies that significantly limit downtime. A Hot Backup solution can dramatically reduce the financial costs involved as well as help protect a company’s valuable reputation. |
 |
| Q. |
What
is Hot Backup? |
| A.
|
Hot Backup is a D3 Unix software feature, which utilizes the D3 traditional transaction logging facilities. Selected transactions are transferred to the secondary D3 server, which acknowledges and processes the transactions, maintaining a copy of the database, ready to handle the workload should a system failure occur on the primary D3 server. |
|
| Q. |
How
does it work? |
| A.
|
A
secondary D3 server is required to be the same
specification as the primary D3 server. Hot Backup’s
secondary D3 server can be in any location, where
a reliable TCP/IP (an industry standard communications protocol)
network connection can be made between the two servers.
If the primary D3 server fails, users can be
switched immediately to the secondary D3 server,
minimizing downtime to just the time taken to re-establish
the users terminal connections on the secondary D3
server. |
|
|
|
Primary |
TCP/IP
Network |
Secondary |
 |
|
|
D3
Server |
Updates
sent to the
secondary D3 server |
D3
Server |
For information on the implementation of the D3 Unix Hot Backup utility, please see "Using Hot Backup” on the D3 Server Products documentation page.
To discuss your business security requirements and for Hot Backup sales and pricing information, please contact your Raining Data sales representative at (949) 442-4400 or email sales.
|
|
