A large multi-gig backup on a large dicey disk (e.g. prone to bsod) may not complete. It would then be helpful to restore have you got, and keep moving from there on the next pass (perhaps skipping over a folder if there is an indication of disk problems, or trying to copy the folder, but let's assume the bsod is something like memory or driver related).
What software programs take this into account well ? e.g. Would be easy to restore what was done. I noticed that Backup4All wants to put everything into a .zip file and then that file will likely be corrupted on the bsod, and their restore system is looking for files that are written at the end as well.
So is this a factor that should be carefully considered in delicate backups ? One obvious solution is a non-compress mode, yet apparently that is not in all of these packages.
What is best in this regard ? And am I right in thinking that this is a largely overlooked part of backup comparisons.
Perhaps they could journal a type of restore/continue point, that probably is in some packages, so if you know of that, share. However that would not be as bulletproof as saving files in the same structure and layout (no compression, maybe 10 times larger) as on the disk.