Arcserve UDP has several recovery capabilities to reduce downtime and minimize risk like bare metal, virtual stand by and full system high availability.

Depending on the severity of the protected node and the time for recovery; UDP provides a single interface for getting your systems back online in an emergency.

Full System High Availability (FSHA) monitors all critical events, including global server failure and all service failures. It provides continuous full system replication with near-instant recovery of entire system including business applications, files & data. You may configure it to automatically reverse server roles, called failover, or manually switch server roles, called switchover, when a critical event is detected. This means the Replica server becomes active while the Master server stands by. FSHA also provides assured recovery testing to give peace and mind. The Assured Recovery option enables you to perform a full transparent test of the recoverability of your data on the Replica server. The Replica server that is tested is the one that would take over the production server if it will be down. The Assured Recovery option is a true test of the actual server, applications and actions that will be required in the event the Replica server will have to switch, become the Active server, and carry out its functions.


Arcserve Full System High Availability is featured in Arcserve Premium plus edition. Customer can create scenarios for physical or virtual masters within the UDP web console for central management. Running a Full System High Availability will avoid server downtime and reduce any risk that may have detrimental effect to the business. This scenario uses a replica virtualization server as the replica standby. It supports Hyper-v, ESX, ESXi, vCenter and Citrix Xen Server.

To make Arcserve FSHA work you need to understand two important components.

  1. The Control Service functions as the single-point-of-control in the Replication or High Availability operation. It contains the entire dataset of the existing scenarios. The Control Service communicates with the Engines and the UDP Consoles. It is responsible for the management of all scenario-related-tasks, such as, creation, configuration, monitoring, and running of the scenarios. After installing the Control Service, you can then add it to the Arcserve UDP Console HA tab.
  2. The Engine is a service that must be running before any scenario can start. It is installed on every server participating in any given scenario, meaning the Master (source) and Replica (target) hosts. Each Engine supports both Master and Replica functionality, for both Replication and High Availability scenarios. Engines can be installed either locally on each host at a time, or through a remote installer on numerous hosts at once, and can be installed during scenario creation, if needed.