Integrating Arcserve Replication with Arcserve Backup › Integrating Arcserve Replication with Arcserve Backup › Capabilities and Benefits

Capabilities and Benefits

The integration between Arcserve Backup and Arcserve Replication lets you use replication and continuous protection (using Arcserve Replication) and backup (using Arcserve Backup) for archiving and compliance.

The integration provides the following core capabilities and benefits:

• Use of the familiar Arcserve Backup interface for backup job configuration, scheduling, and management.
• High-performance D2D, D2T, and D2D2T backup and snapshots.
• Backup encryption and integrated antivirus protection.
• Built-in device and media management.
• Real-time, continuous replication of files and data as they change to ensure that the most recent data is always available for restore or recovery.
• Backups are done from the Replica server, which minimizes the impact on the Master server and provides an unlimited backup window.
• Multiple recovery options as follows:
  • Recovery through Arcserve Replication using Failover. Recovery capability of an application to a standby server at another location and push-button failback of the application once the production server is restored.
  • Recovery through Arcserve Replication using Data Rewind. Recovery capability to rewind to any previous point in time (rewind points) to recover from corrupted data, which provides continuous data protection (CDP).
  • Recovery through Arcserve Backup. Recovery capability from tape or other traditional backup media.
• Real-time consolidation of data from multiple remote branch offices (RBOs) to a central data center (CDC), which provides centralized backup and data consolidation. You can use the replica residing in the central data center to perform centralized backup and reduce the need for IT support at every location.
• Assured Recovery capability to provide nondisruptive, fully automated, in-depth testing of the disaster recovery replica server. This allows recoverability testing of the application on the Replica server without any disruption to the Master server, to the replication process, or to the automated failover protection mechanisms that are in place in case of a disaster.