What backup repositories are supported? | AWS S3 |
How is backup data transmitted to the repository? | DX, Public Internet |
Describe the implementation of the Datamover component |
|
Datamover Scale |
|
In large SDDCs (>500 VMs, >nTBs), your solution may scale data movers. How do you scale? |
|
How are additional data movers provisioned? | Customer controlled |
Describe additional functionalities of image-based backups |
|
Describe if in-guest backup options are available | Agentless, application-aware backup capabilities for Microsoft SQL databases inside the virtual machine. Administrators can perform granular recovery of Microsoft SQL databases. |
Describe security features |
|
Describe network bandwidth/utilization control features | Configurable bandwidth |
Describe design of deduplication/compression features | Source Side (VMC) data is processed at the backup proxy end for deduplication wherein, the deduplicated data is then sent to the Phoenix Cloud. |
Describe added-value services/features not listed above |
|
For a 1TB VM Full backup/Full restore, describe
| Full backup/Full restore takes approximately 2 hours to complete. The network bandwidth usage depends on the amount of data that can be compressed and deduplicated. Typically, a 500 Mbps pipe is required for an on-Premise environment. |
Hybrid centralized management: Describe how on-premises and VMC backups can be managed. Do you support single management console? |
|
Hybrid restore/migration mode: Describe how a VM can be restored from on-premises backup to VMC or from VMC to on-premises | The target repository for both--On-Premise / VMC remains the same i.e Druva storage (S3).
|
For example, let’s say that you have a hybrid configuration. On-premise with local backup, in VMC with cloud backup. What happens if an on-premise VM is migrated to VMC? Will the backup solution automatically update the location of the repository or will the VM still be backed up on premise? | Since our backup repository is in AWS i.e. the data always gets backed up to S3, whether the VM resides in an On-Premise VMware infrastructure or VMC doesn’t really matter to us. The customer will get the benefit of deduplication. The backup solution will not automatically update the repository, but the VM will continue to be backed up to AWS. If the VM was being backed up to the optional CloudCache component, the component since it won’t be reachable from the VMC, the VM will automatically fallback to back up directly to AWS. |
Scale: a. What are your supported maximums (# of VMs, # of TBs) both in number, and/or in simultaneous backup streams? b. Given your SLA, then what is the max bandwidth between VMC and repository? | There is no limit for the number of virtual machines or amount of data that can be backed up. By default, a single proxy can process 3 virtual concurrently. The deployment can be either scaled up or scaled out depending on requirements. |