eEVOS Off-Site Disaster Recovery

1. Asynchronous VM Replication

eEVOS enables you to replicate VMs asynchronously tofrom a remote eEVOS installation to this system. You can run copies on a schedule or keep selected VMs synchronized continuously so that they are available after a site failure.

Start a recovered VM only after you have confirmed that the source VM is shut down or isolated. Running the same VM at both sites can cause duplicate IP addresses, conflicting services, and application data corruption.

What the DR service does

• Connects this recovery system to one or more remote eEVOS installations.
• Copies the selected VMs to a local target drive.
• Runs according to a schedule or maintains a recent asynchronous copy.
• Shows the state of every protected VM in the DR overview.
• Allows an administrator to start a recovered VM when the source site is unavailable.

Off-site replication complements backups; it does not replace them. Keep separate, retention-based backups for deleted files, logical corruption, and ransomware recovery.

Open the DR overview

1. Sign in to the eEVOS system that will hold the recovery copies.
2. Open Offsite VM Disaster Recovery (DR).
3. Confirm that Service Status is active.
4. Review existing jobs, their remote server, VM, target drive, progress, and last full synchronization.

Create a DR job

1. Select Create Off-Site VM Disaster Recovery Job.
2. Choose one of the two replication types.

Configure a scheduled copy

1. Select Scheduled Remote Site Copy.
2. Enter a clear job name.
3. Select the weekdays on which the job should run.
4. Set the start time. Choose a window that does not overlap with heavy production or backup activity.
5. Select Select Remote Server.

Configure asynchronous synchronization

1. Select Async Remote Site Sync.
2. Choose the remote eEVOS installation that contains the source VMs.
3. Continue to VM and target-drive selection.

Asynchronous synchronization minimizes the age of the recovery copy, but replication delay still depends on change rate, network throughput, storage performance, and interruptions. Treat the displayed last synchronization time as the current recovery point.

Select the remote installation

The server list shows the configured remote installations, their members, and whether they are cluster-protected.

1. Verify the host name and member addresses.
2. Select the intended remote installation.
This
3. If it is missing, close the wizard and configure it under Remote Servers first.

Select VMs and recovery targets

The wizard lists the VMs available on the selected remote installation.

1. For each VM you want to protect, select the local target drive.
2. Leave VMs that should not be copied set to Exclude.
3. Ensure that the target drive has enough capacity for the VM, its changes, and operational reserve.
4. Select Next, review the summary, and create the job.

Monitor the DR job

Return to the DR overview and use Refresh to update the status.

Investigate failed, stalled, or increasingly delayed jobs. Check network connectivity, remote-server credentials, free capacity, VM state, and system is running, changes to the VMs are periodically synced to the off-site location, ensuring that your backup is always up to date.logs.

Recover

Dataa Protection:VM Asynchronous replication ensures that even if the primary system experiences an issue, the replicated data onat the remote site

remains
intact
1. Confirm that the production VM and readyits source network are shut down or isolated.
2. Check the job status and last successful synchronization time.
3. Verify that the recovery site's virtual networks and storage are available.
4. Select Start for recovery.the required VM.
5. ReducedConnect Latency:it Unliketo synchronousan replication,isolated asynchronousrecovery network first when your runbook requires validation before production access.
6. Verify boot, application consistency, IP configuration, DNS, dependencies, and user access.
7. Document the recovery point and the services started at the recovery site.

Operational checks

• Review all DR jobs daily and investigate missed schedules or delayed synchronization.
• Monitor free space on every target drive.
• Test recovery regularly without connecting duplicate services to the production network.
• After application or network changes, update the recovery runbook.
• Protect remote-server credentials and limit DR administration to authorized users.
• Keep enough compute, memory, storage, and network capacity at the recovery site for the VMs you intend to start.

Choosing the replication doestype

not

Use requirescheduled thecopies for systems towhose wait for every change to be confirmed by the remote site, allowing for better performance.

• Disaster Recovery Readiness: In the event of a disaster, the off-site copy of your VMsdata can be quickly brought online, ensuring that your services remain available.

2. Scheduled Replication

eEVOS provides the flexibilityrecovered to schedulea defined daily or weekly point and where replication jobstraffic basedmust onstay your needs. You can define how frequently the VMs are replicated to the remote site, whether onwithin a daily,fixed hourly,window. orUse customasynchronous schedule.

• Customizable Backup Strategy: Set replication schedules to fit your business needs, balancing data currency with system performance.
• Automated Backups: eEVOS automatically manages the replication process, ensuring that your disaster recovery site is always prepared without manual intervention.
• Granular Control: You can select individual VMssynchronization for replication or replicate entire clusters, providing flexibility in your disaster recovery planning.

3. Full VM Recovery

In case of a critical failure or disaster, eEVOS allows you to fully restore VMs from the off-site disaster recovery location. This ensures that your VMs, along with their data, configurations, and applications, are ready to be brought back online as soon as needed.

• Seamless Recovery: Replicated VMs can be restored in full to ensure the fastest possible recovery with minimal configuration required.
• Entire VM Recovery: Bring back the complete virtual environment, including system settings, to quickly restore operations.
• Business Continuity: With off-site disaster recovery, you can continue operations in a different location, reducing the impact of the disaster.

5. Simplified Setup and Management

Setting up Off-Site Disaster Recovery in eEVOS is straightforward, with an intuitive interface that allows you to easily configure replication schedules and select which VMs or clusters to replicate.

• User-Friendly Interface: eEVOS provides a simple setup wizard to configure off-site replication with minimal effort.
• Centralized Management: Manage replication tasks and monitor the status of off-site backups from a central dashboard.
• Scalability: eEVOS disaster recovery is scalable to your needs, whether you’re managing a few business-critical VMs orthat need a largemore infrastructurerecent withcopy. multipleA clusters.
mixed

Conclusion

The Off-Site Disaster Recovery feature in eEVOSapproach is anoften essentialappropriate: toolcontinuous synchronization for businesses seeking to ensure the highestmost levelscritical of data protectionservices and availability. With asynchronous replication, scheduled backups,copies fullfor VMless andtime-sensitive file-level recovery, and an easy-to-use interface, eEVOS provides a comprehensive solution that protects your infrastructure from data loss and ensures fast recovery in any disaster scenario.workloads.