VMware and private cloud
VMware repository / CBT and OpenStack/Safir data transfer use different architectures. Review backup, metadata and target recovery scenarios separately on the platform pages.
VIRTUALIZATION SOLUTIONS
Different hypervisors.
Protection for your environment.
Plan source platforms, data paths and recovery targets together. Keep platform-specific prerequisites visible across heterogeneous infrastructure.
STEP-BY-STEP GUIDES
From installation to recovery.
01
0203040506070809010
VMware Backup
Prepare VMware backup step by step, from vCenter connectivity and test VM selection to HotAdd prerequisites and the full/CBT chain.
Open guide02VMware Restore
Plan VMware recovery point selection, target vSphere resources and datastore checks, then validate recovery in a new isolated VM.
Open guide03Hyper-V Backup Guide
Prepare Hyper-V backup with source connection, VM/disk selection, retention and initial acceptance checks.
Open guide04Hyper-V Restore Guide
Plan recovery point, disk chain and Hyper-V targets within the scope exposed by the source template.
Open guide05Proxmox Backup Guide
Prepare Proxmox backup with source connection, VM/disk selection, retention and initial acceptance checks.
Open guide06Proxmox Restore Guide
Plan recovery point, disk chain and Proxmox targets within the scope exposed by the source template.
Open guide07KVM Backup Preparation Guide
KVM Backup Preparation Guide: assess releases, source access and validated target scope.
Open guide08KVM Restore Preparation Guide
KVM Restore Preparation Guide: assess releases, source access and validated target scope.
Open guide09Sangfor Backup Preparation Guide
Sangfor Backup Preparation Guide: assess releases, source access and validated target scope.
Open guide010Sangfor Restore Preparation Guide
Sangfor Restore Preparation Guide: assess releases, source access and validated target scope.
Open guideDEFINE YOUR SCENARIO
Other virtualization platforms
We assess agents, hypervisor versions and restore methods for Hyper-V, standalone KVM and Sangfor. KVM workflows inside OpenStack do not automatically establish support for every standalone KVM deployment.
Choose the recovery target early
A new isolated VM, another location and a second cloud have different prerequisites. CPU/firmware, disk layout, network mappings and storage capacity belong in the acceptance test.
COMMON QUESTIONS
Start with
the right questions.
Is migration between platforms possible?
Source-target combinations, guest boot and driver requirements need separate validation. Automatic migration between all platforms is not guaranteed.
START WITH YOUR INFRASTRUCTURE
Virtualization — let’s discuss your needs.
Share your workloads and recovery objectives. Let’s define the technical scope together.
