![]() Typically this means that this specific point-in-time backup can't be used in a recovery process. Consider that for some reason a single backup image file is corrupt in your backup chain. This is probably why people look at a reverse incremental scheme, because it merges those recovery points into a current image allowing you to quickly recover data or systems.īut keep in mind the second issue-integrity-as you look at these processes. ![]() The less recovery points you keep, the less storage you need and the faster the recovery process as you use those points to recover. For example you may only keep 1 month worth of daily and/or intra-daily backup files. Your retention policy can affect this by reducing the number of points you keep in your backup chain. Regarding the first two issues-integrity and speed-it's important to realize that over time your recovery chain gets longer which implies that there are more points to use during a recovery process. Ok, a third would be the amount of storage the backup chain uses and this is where deduplication, or any other form of compression, would have an effect. The first is the backup chain integrity and the second is the speed to recovery. ![]() There are typically two (often more) issues at play here when considering best practices for backup chains and enforced retention policies. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |