Active full can be used when plenty of repository space is available, the backup window allows enough time and network bandwidth is sufficient to support reading the source data in full. Incremental backups are still processed using Changed Block Tracking (CBT). Active full usageįorward incremental backup provides good performance with almost any storage and the highest level of backup chain consistency since each new chain is populated by re-reading VM source data. When a new full backup is created, a new chain is started, and the old backups can be removed once the new chain meets the retention requirements. Older full backups cannot be removed from the retention chain until a newer backup chain is created. This is necessary because the incremental backups are dependent on the initial full backup. It generally works well with all storage devices although it requires more storage space than other backup methods due to the fact that it requires the creation of periodic full backups (either using active or synthetic backups), typically scheduled weekly. The forward incremental backup method is the simplest and easiest to understand. This site uses Just the Docs, a documentation theme for Jekyll. Restoring VMs to an HPE 3PAR with thin disks.Backup Repository HA using Windows Storage Replica.
0 kommentar(er)
