|
 |
 Subscribe to our free newsletter and get the latest product news and announcements delivered directly to your Inbox.
|
|
 |
Subscribe |
|
|
|
|
 | Real Time Backup |  |
|
Your applications powered by Pervasive.SQL™ databases are mission critical. The data in these
applications are high-value, time-sensitive corporate assets. Unfortunately, there are numerous threats
to your data, including:
-
Hardware failures. The most common are computer or disk crashes. Causes range from random failures
to accidents like spilling water onto a server.
-
Site disasters. These range from high-profile disasters like fire or earthquake to more mundane occurrences
like power surges, water pipe breaks or virus attacks.
-
User and application errors. These encompass everything from accidents like incorrectly upgrading the
operating system to malicious acts like deleting files or introducing viruses.
The Pervasive DataExchange Real-Time Backup Edition addresses each of these threats.
Given the mission critical nature of your data, the business cost of data loss or data interruption is high.
When planning a disaster recovery strategy, the two key questions to ask are:
-
How much data can I lose? This is a data freshness question. Rapidly moving data from your mission-critical
system to a backup minimises data loss.
-
How long can I be down? This is a data recovery question. Having a functional database server on
standby minimises downtime.
Many companies use tape backup and/or server clustering as their backup strategy. Tape backup is a low cost
and reliable, but data on tape is only as fresh as the last backup, since it is impractical to backup a
large in-service database. Server clustering usually provides adequate protection against localised hardware
failures, but leaves data exposed to site disasters since the only safe copy of data is the tape.
The Real-Time Backup Edition contains everything you need to maintain a real-time backup of your mission-critical
data. It includes a DataExchange license for two Pervasive.SQL database engines (for the primary and the
backup) as well as a one-user count database license (for the backup). The DataExchange engines are restricted
to one-way replication, and the replication network is restricted to two databases.
|
