Druva Phoenix for VMware Cloud on Dell EMC
Article ID: 324720
Updated On:
Products
VMware Cloud on Dell EMC
Issue/Introduction
This article provides information about the support of Druva Phoenix for VMware Cloud on Dell EMC.
Disclaimer: The partner solution referenced in this article is a solution that is developed and supported by a partner. The use of this product is also governed by the end-user license agreement of the partner. You must obtain from the partner the application, support, and licensing for using this product. For more information, see druva.com.
An optional software component—CloudCache is available to store data locally on-premises. CloudCache holds data for 30 days locally if there are sites with weak WAN bandwidth. CloudCache can upload data to the AWS S3 storage. All the data is deduplicated, compressed, and encrypted.
The following diagram illustrates the Druva Phoenix architecture for VMC.
The minimum bandwidth required depends on the amount of data that needs to be processed in a given time. Given that we have an optional component in CloudCache, we have had customers with extremely low bandwidth backing up the data locally and slowly replicating it to the AWS S3 storage. Our primary repository is S3 and the On-Premise component is block storage as well. It is a software component that can reside on any commodity hardware.
Disclaimer: The partner solution referenced in this article is a solution that is developed and supported by a partner. The use of this product is also governed by the end-user license agreement of the partner. You must obtain from the partner the application, support, and licensing for using this product. For more information, see druva.com.
Solution Architecture
The Druva Phoenix architecture remains the same for both VMC and Datacenter use cases. For ROBO use cases, there is no need for multiple storage/hardware deployments thus, experience a single pane of glass for all ROBO offices. No need for multiple backup repositories/backup servers at each location thus, effectively manage the TCO.An optional software component—CloudCache is available to store data locally on-premises. CloudCache holds data for 30 days locally if there are sites with weak WAN bandwidth. CloudCache can upload data to the AWS S3 storage. All the data is deduplicated, compressed, and encrypted.
The following diagram illustrates the Druva Phoenix architecture for VMC.
The minimum bandwidth required depends on the amount of data that needs to be processed in a given time. Given that we have an optional component in CloudCache, we have had customers with extremely low bandwidth backing up the data locally and slowly replicating it to the AWS S3 storage. Our primary repository is S3 and the On-Premise component is block storage as well. It is a software component that can reside on any commodity hardware.
| Â | Storage | Bandwidth (minimum) | Latency |
| Backup (Datacenter architecture) | S3 | Depends on RPO | Depends on the destination (backup) AWS region |
| Restore (Datacenter architecture) | S3 | Depends on RTO | Depends on the restore destination |
| Backup ROBO architecture | S3, optional block storage software - CloudCache | Depends on RPO | Depends on the source (backup) AWS region |
| Restore ROBO architecture | S3, optional block storage software - CloudCache | Depends on RTO | Depends on the restore destination |
Support Information
Feedback
Yes
No
Powered by
