Hello,
I wanted to describe my backup system and the issues I have run into with Hasleo Backup Suite:
All Backups are triggered manually by me.
Day 01: Create a FULL IMAGE
Day 02: Create Incremental
Day 03: Create Incremental
Day 04: Create Incremental
Day 05: Create Incremental
Day 06: Create Incremental
Day 07: Create Incremental
Day 08: Create DIFFERENTIAL
Day 09: Create Incremental
Day 10: Create Incremental
Day 11: Create Incremental
Day 12: Create Incremental
Day 13: Create Incremental
Day 14: Create Incremental
Day 15: Create DIFFERENTIAL
Day 16: Create Incremental
Day ...
Day 29: Create New Backup (Full)
Problems I noticed:
1. I could not find out if the Incremental on day 9 REQUIRES
a) The Full Image from day 1 AND the Differential Image from day 8
OR
b) The Full Image from day 1 AND the Incremental Images from days 2,3,4,5,6,7 ?
2.
I looked into the folder with the backup files. I created a news folder "Test".
I moved the Incrementals from Day 2,3,4,5,6,7 into the folder "Test".
I then tried to browse the Incremental from Day 9. I was able to browse it (no error message "missing backup files").
I then moved the Incremntals from folder "Test" back to the Backup Folder.
Then I moved the Differental from day 8 into the Folder "Test".
I then tried to browse the Incremental from Day 9 AGAIN. I was AGAIN able to browse it (no error message "missing backup files").
This is unexpected behavior. There should be an error message in one of the two scenarios. I think it is very important that before browsing an image file, it is made sure all files required are accesible/available.
I think INCREMENTALS should always be created like this:
1. Look for the LATEST Backup file in the Backup Folder.
2. Base the incremental on that LASTEST backup file, no matter if it is Inc, Diff, or Full.
The advantage of this system is that the user can delete all incrementals that are older than the last Differential. It is also better for data security / corruption probability. And it leaves more possibilities for the user to thin out (delete) (some of) the backups.
Is this the case?
I wanted to describe my backup system and the issues I have run into with Hasleo Backup Suite:
All Backups are triggered manually by me.
Day 01: Create a FULL IMAGE
Day 02: Create Incremental
Day 03: Create Incremental
Day 04: Create Incremental
Day 05: Create Incremental
Day 06: Create Incremental
Day 07: Create Incremental
Day 08: Create DIFFERENTIAL
Day 09: Create Incremental
Day 10: Create Incremental
Day 11: Create Incremental
Day 12: Create Incremental
Day 13: Create Incremental
Day 14: Create Incremental
Day 15: Create DIFFERENTIAL
Day 16: Create Incremental
Day ...
Day 29: Create New Backup (Full)
Problems I noticed:
1. I could not find out if the Incremental on day 9 REQUIRES
a) The Full Image from day 1 AND the Differential Image from day 8
OR
b) The Full Image from day 1 AND the Incremental Images from days 2,3,4,5,6,7 ?
2.
I looked into the folder with the backup files. I created a news folder "Test".
I moved the Incrementals from Day 2,3,4,5,6,7 into the folder "Test".
I then tried to browse the Incremental from Day 9. I was able to browse it (no error message "missing backup files").
I then moved the Incremntals from folder "Test" back to the Backup Folder.
Then I moved the Differental from day 8 into the Folder "Test".
I then tried to browse the Incremental from Day 9 AGAIN. I was AGAIN able to browse it (no error message "missing backup files").
This is unexpected behavior. There should be an error message in one of the two scenarios. I think it is very important that before browsing an image file, it is made sure all files required are accesible/available.
I think INCREMENTALS should always be created like this:
1. Look for the LATEST Backup file in the Backup Folder.
2. Base the incremental on that LASTEST backup file, no matter if it is Inc, Diff, or Full.
The advantage of this system is that the user can delete all incrementals that are older than the last Differential. It is also better for data security / corruption probability. And it leaves more possibilities for the user to thin out (delete) (some of) the backups.
Is this the case?