It is recommended to limit the use for primary backup jobs to the integrated deduplication appliances, where synthetic operations can be used. This can lead to long snapshot commit, so this mode needs to be planned carefully. The downside of active fulls is the need to transport the entire amount of virtual machines on a weekly/monthly basis. This two-step process can generate significant load on the appliance, slowing down operations.Īlso, consider that Instant VM Recovery might not be as fast as expected – unless the deduplication appliance offers a fast non deduplicated area for the most recent restore points (such as ExaGrid). During backup files transformation the same blocks are read and then written back to the appliance where they are de-hydrated (deduplicated) again. Note: "Re-hydration" is the act of restoring the original blocks in a non-deduplicated form. Such operations require significant time and I/O.
Unless you are using DDBoost protocol on EMC DataDomain storage or Catalyst on HPE StoreOnce, you should configure primary jobs for forward incremental with active full backups - since jobs with transformation will require block "de-hydration" and then "re-hydration" on the storage. Deduplication Appliance as a Primary Backup Repository Using a Deduplication ApplianceĪs a storage-agnostic product, Veeam Backup & Replication can use any deduplication appliance as a repository in different use cases: primary backup repository, backup copy repository, and Virtual Tape Library (VTL) container. For this reason we recommend to use these devices mainly as secondary targets, where parameters like price per GB are more important than restore performance. However, any random read I/O may suffer from re-hydration processes required during restores. Instead, a synthetic file is merged or "synthesized" by a specialized application program from the original file and one or more modifications to it.Deduplication applied to storage is a technique aimed at reducing the storage space consumption.ĭeduplicated storage systems are often optimized for write operations and can offer rather high ingest rates. Synthetic backup is the process of generating a file from a complete copy of a file created at some past time and one or more incremental copies created at later times. Veeam Backup & Replication accesses the previous full backup file and a chain of subsequent incremental backup files on the backup repository, consolidates VM data from these files and writes consolidated data into a new full backup file. Synthetic full backup produces a VBK file that contains data of the whole VM. Just so, what is synthetic full backup Veeam? However, businesses such as mid-size online retailers will want to increase their incremental backups to 4 hours in addition to producing transaction logs on an hourly basis. Veeam Backup & Replication will start a new backup copy session, copy data from the source backup repository and save it in a full backup file on the target backup repository.īeside above, how often should you do a full backup? The average mid-size company will benefit from performing a full backup every 24 hours, with an incremental backup every 6 hours. In the working area, select the backup copy job and click Active full on the ribbon or right-click the backup copy job and select Active full. Herein, how do I run a full backup on Veeam?
All incremental backup files use the latest active full backup file as a new starting point. The active full backup resets the backup chain.
When Veeam Agent for Microsoft Windows performs active full backup, it produces a full backup file and adds this file to the backup chain.