- Key Features
- VM Backup
- Agentless VM Backup
- ESXi Backup
- vCenter Backup
- Backup Storage Targets
- RTO RPO < 15 mins
- VM/Disk Exclusion
- Application-aware Processing & Log Truncation
- VMware Quiescing
- Flexible Backup Scheduling
- CBT based Incremental Backup
- Synthetic Full Backup
- Basic Retention
- GFS Retention – Incremental/Full
- Backup Data Encryption
- Backup Proxy
- VM Backup to Cloud
- Create Backup using Template
- VM Recovery
- VM Replication
- Disaster Recovery
- Management
- Backup Settings
VMware Backup Proxy
The backup proxy processes backup jobs and delivers traffic while the backup server administers tasks. You can configure one or more backup proxies and assign backup proxy for each VMware backup job. This way, a backup proxy will process the backup data of the virtual machines configured in the job.
A backup proxy’s basic operations are as follows:
- Obtaining data from Virtual Machines (VMs)
- Encryption of data storage (AES 256-bit)
- Send the data to a backup repository
Benefits of having a Backup Proxy
Load Balancing
BDRSuite allows users to choose a backup proxy server to distribute the load of the backup server. When you use the BDRSuite Backup Proxy in your environment, you have complete control over the impact on the vSphere infrastructure and backup traffic flow. Proxies are the workhorses that are required to achieve fast backup and restore speeds.
LAN-Free Backup Transport Modes
Depending on your backup architecture, BDRSuite Backup Proxy supports the following LAN-Free data transport modes:
SAN: SAN mode necessitates that applications run on a backup server/backup proxy that has access to SAN storage (Fiber Channel, iSCSI, or SAS connected) that contains the virtual discs to be accessed. This method is efficient because no data must be transferred through the production ESXi host. A physical machine must be used as an SAN backup proxy.
HotAdd: A virtual machine must be used as the HotAdd backup proxy. HotAdd involves attaching a virtual disc to the backup proxy in the same way that a disc is attached to a virtual machine. The HotAdd proxy must have access to the same datastore as the target virtual machine, and the target VM’s VMFS version and data block sizes must be the same as the datastore where the HotAdd proxy resides.