Veeam : On-premises repositories include backup proxy local folder, DAS connected to the backup server (i.e. Customers cannot store backups on traditional storage platforms on-premises On-Premises Repository – Traditional Storageĭruva : Backups can only be stored in Druva’s cloud (AWS). (Note: VBO does not offer a feature to simply move backups across repositories) Ability to add/change backup repository platforms. Full control over data location and access, by storing data in any location. Veeam : Full control over performance, by adding, removing, and modifying as many backup proxies and repositories as required. Customers are locked in Druva (no easy migration off Druva). Customers have no control over the infrastructure, performance, or data location. Veeam : Deployable on-premises (on virtual and physical machines), in the cloud, or as BaaS (with VCSP).ĭruva : All components and settings are controlled by Druva. Druva runs inSync Cloud on AWS using Amazon EC2 for compute, Amazon EBS for storage volume, Amazon RDS for configuration management, and Amazon S3 for storage. Customers must use Druva’s cloud, which runs on AWS. Druva’s Capabilitiesĭruva: Druva cannot be deployed on-premises or in customers’ cloud accounts.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |