vinadaa.blogg.se

Check the Microsoft Product Lifecycle for information about how this product, service, technology, or API is supported.

A previously used full backup file remains on disk until it is automatically deleted according to the retention policy.Action Required: StorSimple Data Manager, StorSimple Device Manager, StorSimple 1200, and StorSimple 8000 have reached their end of support. All subsequent incremental backup files use the synthetic full backup file as a new starting point. As well as any other full backup file, the synthetic full backup file resets the backup chain. Veeam Backup & Replication treats synthetic full backups as regular full backups. The synthetic full backup produces less load on the production environment: it is synthesized right on the backup repository.The synthetic full backup does not use network resources: it is created from backup files you already have on disk.The synthetic full backup has a number of advantages: As a result, the created synthetic full backup file contains the same data you have if you create an active full backup. 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. Instead, it synthesizes a full backup from data you already have in the backup repository. When you perform synthetic full backup, Veeam Backup & Replication does not retrieve VM data from the source volume.When you perform active full backup, Veeam Backup & Replication retrieves VM data from the source volume where the VM resides, compresses and deduplicates it and writes it to the VBK file in the backup repository.The difference between active and synthetic full backup lies in the way how VM data is retrieved: Synthetic full backup produces a VBK file that contains data of the whole VM. In terms of data, the synthetic full backup is identical to a regular full backup. As an alternative, you can create synthetic full backups. Active full backups are resource-intensive and consume considerable amount of network bandwidth.

In some situations, running active full backups periodically may not be an option.