Druva Phoenix is for server backups on cloud, which is the deployment model chosen by my customers. While Druva Phoenix is a good solution for a cloud-to-cloud environment, such as moving from AWS to another AWS, I see complexity when a customer wants to move from a physical environment or a physical VM backup to Druva cloud. Even if that happens, it takes a fairly longer time. The first backup is long because it is physical to cloud. Typically, Druva handles this requirement by providing a small accelerator box at a customer's location. That accelerator box would first do the backup and then at the backend would keep backing up on the cloud, but that still is, in my suggestion, a staging solution and not a performance improver. I have worked with Druva within the last twelve months. I am familiar with Druva Phoenix. Druva has white-listed cloud of their own, but I do know that the backend is on AWS infrastructure. As a solution provider for backup, they have their own software, and they use Amazon's AWS infrastructure as their backend.
The typical use case for Druva Phoenix depends on multiple workloads. If a customer wants a simple solution where we can manage the entire workload, or they want to back up with agent plus backup, we can accommodate that. It depends on the use case for what type of solution they are looking for.
Checking Hyper-V backups, checking file level backups, checking VMware backups, even Nutanix backups, even Azure backups. So, like, stored all the experts of Phoenix taking NAS backups. Earlier, I used to take SQL backups as well. All our customers are in the pharmaceutical industry.
Solutions Architect at a computer software company with 201-500 employees
MSP
Top 20
Apr 28, 2023
Druva Phoenix is used to have the ability to back up on-prem to the Druva cloud. It can back up many sources can be virtualized, physical systems, or VMware environments.
Druva Phoenix offers an easy-to-use, secure, and cost-effective cloud backup solution with simplified management and efficient data protection capabilities.Druva Phoenix is designed for environments needing straightforward setup and automated off-site backups without on-premises requirements. It provides global deduplication, optimizing storage and costs while offering robust ransomware protection through air-gapped environments. Users value its easy integration with cloud providers like AWS,...
Druva Phoenix is for server backups on cloud, which is the deployment model chosen by my customers. While Druva Phoenix is a good solution for a cloud-to-cloud environment, such as moving from AWS to another AWS, I see complexity when a customer wants to move from a physical environment or a physical VM backup to Druva cloud. Even if that happens, it takes a fairly longer time. The first backup is long because it is physical to cloud. Typically, Druva handles this requirement by providing a small accelerator box at a customer's location. That accelerator box would first do the backup and then at the backend would keep backing up on the cloud, but that still is, in my suggestion, a staging solution and not a performance improver. I have worked with Druva within the last twelve months. I am familiar with Druva Phoenix. Druva has white-listed cloud of their own, but I do know that the backend is on AWS infrastructure. As a solution provider for backup, they have their own software, and they use Amazon's AWS infrastructure as their backend.
The typical use case for Druva Phoenix depends on multiple workloads. If a customer wants a simple solution where we can manage the entire workload, or they want to back up with agent plus backup, we can accommodate that. It depends on the use case for what type of solution they are looking for.
We utilized the product to modernize backup as a service, eliminating the need for extensive hardware and ensuring data is securely backed off-site.
Checking Hyper-V backups, checking file level backups, checking VMware backups, even Nutanix backups, even Azure backups. So, like, stored all the experts of Phoenix taking NAS backups. Earlier, I used to take SQL backups as well. All our customers are in the pharmaceutical industry.
We use Druva Phoenix for backing up virtual environments, physical servers, and a few SQL workloads.
Druva Phoenix is used to have the ability to back up on-prem to the Druva cloud. It can back up many sources can be virtualized, physical systems, or VMware environments.
We've been using it just for a couple of on-premise servers where we needed to get the data stored somewhere else.
We use Druva for both local backups as well as to directly backup to AWS.