In order to restore this VM, the VBR server is going to have to merge both the full backup and all the increments between that full backup and the point where you need to restore to in order to present you with a complete picture of the data, an operation that takes time. You have a VM blue screen overnight and it is determined that you need to restore from backup.
For example, if you have a 7-day retention policy that starts on Wednesday and your synthetic full backup occurs on Saturday a week from Friday, you will have 9 restore points, and only after the synthetic operation occurs on Saturday will you return to the 7 restore points dictated by policy.Īnother issue is in the case of an immediate need restore. Because a traditional forward incremental job with periodic full backups requires there to always be a full backup prior to the increment that needs to be restored, a restore point will not be dropped from the backup chain until there is a supporting full backup behind it. The biggest is in regards to adherence to retention policy. There are a couple of downsides to a forward incremental job. A synthetic full backup is a pretty neat concept: a period of incremental backups are synthetically meshed to form the equivalent of a full backup, just without the full hit on the network and storage. In a typical forward incremental job, either an active full or what’s called a synthetic full backup is performed weekly to keep the number of active increments to a manageable level.
0 kommentar(er)
