This backup file has the same format as the primary backup file.Īs your data retention and recovery requirements evolve, however, maintaining the 3-2-1 Rule can become a cost, and resource, prohibitive endeavor. When the backup copying job starts, Veeam Backup & Replication accesses backup files on the source backup repository, retrieves data blocks for a specific machine from the backup file, copies them to the target backup repository, and composes copied blocks into a backup file on the target backup repository. In Veeam Backup & Replication, backup copy is a job-driven process. 3: You must keep at least one backup offsite (for example, in the cloud or in a remote site).2: You must use at least two different types of media to store copies of your data (for example, local disk and cloud).1: You must have at least three copies of your data: the original production data and two backups.This is the mechanism that the Veeam Cloud Connect Backup solution provides to help you follow the the 3-2-1 rule: Veeam: An image-level backup will use the cloud-native snapshot capabilities and store the image into a specific Veeam repository.įull and incremental backup will be created depending upon the backup policy session.įor VBAWS: perform a cloud-native snapshot backup prior to an Image-level backup or snapshot replication.īackup copy allows you to create several instances of the same backup data in different locations. Ability to configure backup windows, so as to avoid impacting end-users’ activities.ĭruva CloudRanger: No capacity to create backups (copy to S3) from cloud snapshotsĭruva CloudRanger protects cloud instances with cloud-native snapshots instead of image-level backups like Veeam. Ability to schedule backups to run daily at a chosen time, on selected days, or periodically, as often as every 5 minutes.
VEEAM BACKUP SOLUTION FULL
Veeam : Full control over backup schedules.
[Scheduled backup and Manually Triggered (Admin only). external USB/SATA drives), SAN, and SMB 3.0 share (experimental).ĭruva : Druva does not enable customers to customize backup start time or backup window, and offers only preset backup frequencies (backup every 4/8/12/24 hours, or every 1/2/3/7 days) 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.