
Our business is keeping other companies connected, so protecting single virtual machines was never going to be enough. Vinchin now covers all four of our hosts from one console, and it gave us a defined path for the day the whole data center is gone, backup server included. That is what lets us promise continuity to our own customers.

Mazin Abdulhadi
IT Manager
DataNet

About DataNet
DataNet is a nationwide service provider in Iraq, working as an ISP and delivering end-to-end IT services. It supplies businesses with the communications services they rely on to keep daily operations running. Its virtual estate consists of four ESXi hosts running VMware vSphere.
Business Challenge
Planning for Recovery Beyond the Data Center
Most backup discussions focus on recovering individual virtual machines. DataNet was concerned with a much larger scenario: the loss of its entire virtual infrastructure, including vCenter and all ESXi hosts. The team needed to understand how recovery would work if the original infrastructure was gone and there was no existing platform to restore the VMs to.
Ensuring Backups Survive a Site-Wide Outage
Backup data stored alongside the infrastructure it protects is vulnerable to the same site-wide failure. DataNet needed an offsite backup copy that would remain accessible and usable even if the entire primary site had to be rebuilt.
Defining a Recovery Sequence Before Disaster Strikes
Knowing that data can be recovered is only part of the equation. DataNet also needed a clear, practical recovery sequence that its team could follow under pressure: which components to rebuild first, where to retrieve the backup data, and how to bring the virtual infrastructure and workloads back online.
Why Choose Vinchin?
DataNet evaluated Vinchin Backup & Recovery and put its recovery questions to Vinchin's support engineers in a single session. Four points settled the decision:
VMs can be restored to a rebuilt virtual infrastructure. Vinchin restores virtual machines to an environment where the underlying platform has already been rebuilt. This means the recovery process starts with restoring vCenter and the hosts, followed by the virtual machines. DataNet now has a clear understanding of the recovery sequence.
Offsite backups provide a flexible recovery option. If the infrastructure is rebuilt at the secondary site, virtual machines can be restored directly from the offsite backup copy. If the primary site is rebuilt instead, the backup data is first transferred back to the primary site before the VMs are restored.
The backup server itself can be recovered. Configuration Backup captures the backup server’s configuration settings. This allows the server to be rebuilt and its configuration restored, helping ensure that a backup server failure does not leave the team without a recovery plan.
Recovery questions were answered in a single session. DataNet’s team walked through its recovery scenarios with Vinchin’s support engineers and received clear answers, covering both site-rebuild options and the scenario in which vCenter itself is lost.
Vinchin Solution
DataNet deployed Vinchin Backup & Recovery across its VMware environment, with a protection strategy designed to cover a wide range of recovery scenarios, from the loss of a single virtual machine to a complete site outage.
Agentless VMware backup. All four ESXi hosts are registered with a single backup server, with no agents required on individual guest VMs. Backups are performed at the hypervisor level, minimizing the impact on production workloads.
Instant Restore for individual VMs. Vinchin can start a virtual machine directly from its backup in approximately 30 seconds, eliminating the need to restore the entire virtual disk before bringing the VM online.
vCenter protected as a virtual machine. Since vCenter runs as a virtual machine, it is protected and restored through the same backup workflow as other workloads. This ensures that the management layer is included in the recovery plan.
Offsite backups for site-level recovery. Backup data can be replicated to a secondary location. After the infrastructure is rebuilt, VMs can be restored directly from the offsite copy or from backup data transferred back to the primary site. In either case, the recovered VMs can be brought up on the newly rebuilt vCenter.
Configuration Backup for the backup server. Vinchin includes Configuration Backup, which captures the backup server’s configuration settings. This allows the backup server to be restored with its original configuration, reducing the need for manual reconfiguration.
The Results
DataNet now manages backup and recovery across its four VMware hosts through a single console, with a second copy held offsite. The plan has been exercised twice since go-live: in the most recent drill the team declared a full-site loss and had every production VM running at the secondary site in 2 hours 40 minutes.
Key Benefits
Centralized backup management across four hosts. All four ESXi hosts and their backup jobs are managed through a single console, giving the team one place to monitor backup operations and manage recovery tasks.
A defined recovery path for a complete site outage. DataNet can follow either of two recovery paths: restore virtual machines directly at the secondary site or transfer backup data back to the primary site before restoring the VMs.
Recovery targets are stated in hours and checked against drill results. Site recovery is targeted at four hours and last measured at 2 hours 40 minutes; the offsite copy holds a 24-hour RPO, while critical VMs are backed up every two hours.
The components that usually break a recovery plan are covered. The team has rebuilt the backup server from its own configuration backup in 25 minutes during a drill, and vCenter came back through the same VM restore job, without a separate tool or a rebuild from scratch.