 |
|
|
Syncsort ExpressDR™ server imaging technology provides extremely fast recovery of entire machines from stored virtual volume images. Compared to conventional bare metal recovery techniques, ExpressDR technology dramatically simplifies server recovery:
The ExpressDR feature utilizes routine, scheduled Syncsort AdvancedClient snapshots and thus does not require special disaster recovery backups. This has major benefits:
- Does not require system interruption during the backup process.
- Does not require any system reboots.
- Does not interfere with users.
- Does not require significant system resources (CPU, memory, temporary disk space, network bandwidth).
Utilizing a supplied ExpressDR CD, the ExpressDR feature initiates and controls fast, block-level recovery that provides dramatic benefits compared to traditional methods:
- Eliminates the need to manually reinstall the operating system and root volume applications.
- Streamlines the recovery process, significantly reducing the time that a root volume or operating system is inoperable.
- Rapidly recovers an entire or partial system. Depending on recovery needs, the ExpressDR feature can restore the operating system, system settings, patches, partition information, applications, configurations and data - all in a fraction of the time required by manual methods.
In addition to fast recovery of a failed machine, experienced administrators can adapt ExpressDR server imaging to deploy a virtual volume image to multiple machines, continually update off-site secondary systems, keep test and staging environments in sync with production systems, and transfer staged configurations to production servers.
The ExpressDR feature supports Windows and SPARC Solaris systems and protects Oracle, Exchange, SQL Server, and other applications.
| Conventional Bare Metal Recovery |
Syncsort ExpressDR Server Imaging Recovery |
| Special bare metal restore backup job required |
Routine server image snapshots used for full system recovery |
| Reboot necessary for bare metal restore backup job |
Non-disruptive, image block-level backup technology has minimal CPU impact |
| Each full backup uses significant elapsed time and storage resources |
Block-level incremental backups are very fast and use minimal storage resources |
| Server is down during bare metal restore backup job, affecting users |
Users are not affected during a block-level incremental backup |
| Backups occur infrequently, leading to longer point-in-time recovery options: significant amounts of lost data |
Backups occur very frequently, leading to extremely short point-in-time recovery options: little or no lost data |
| Local tape often required for restore |
Block-level disk-to-disk recovery requires no tape |
For more information:
|
|
|
