Michael chose to conduct proofs of concept (POCs) with both Druva and a competitor in the backup arena, the latter of which Anglo-Eastern was already using to back up its VMware virtual machines (VMs).
It was a test of two very different solutions with cloud-native Druva and the other solution being on-premises. Performance and simple management were the success criteria for the POCs, and Anglo-Eastern expected the on premise solution to be the hands-down winner since bandwidth and connectivity were not an issue in Anglo-Eastern’s infrastructure.
Surprisingly, during the POCs the team discovered that the performance advantage of the on-premises, dedicated hardware was neutralized, as it found the Microsoft API was a bottleneck. No matter how robust the infrastructure, backup performance was limited by the throughput of the API.
At this point it became clear that Druva’s cloud-native solution held the most strategic advantage. Plus, using the competitor’s solution to protect cloud backups would have required on-premises storage. It made little sense backing up cloud data to on-premises hardware, as there was no foreseeable advantage.
This is when selecting Druva’s solution became a no-brainer, according to Michael. Using Druva, which is built on Amazon Web Services (AWS), meant zero infrastructure and zero maintenance, as well as a far friendlier user interface and simple administrative and management process.
Even the process of moving to Druva was simple. Thanks to its integration with Microsoft Azure Active Directory, it only took one day to get all 1,800 users onto the Druva platform.