But there are real events where we needed to actually move the Backup Repository from the remote site to another site (it was a test of DR when we "assimilate the move of data center due to some massive event like DC burnt down). But do not ask me how or why.....some files went missing and/or corrupted.That was my assumption as well, basically that the entirety of an incremental backup file needed to be intact in order for even just a part of it to be accessed, but apparently not. So the actual number of blocks on the storage volume needed to recover data in either case remains the same. So, actually not the issue I believed it would be.
Admittedly though I see why this sort of thing was confusing, Gostev understood how it worked so from his perspective there was no difference, but it was never explained to me (and others) that that was how it worked until just a couple posts ago, so we went on trying to explain a problem that we saw because we assumed it worked one way, which was incorrect. Not sure if the ability to reliably access non-corrupted blocks of a file that contains corrupted blocks is actually outlined in any docs somewhere, but I didn't know it was a thing. Actually has gone towards my recently improved viewpoint of Veeam.
So if the NAS had Full backup File (60 days ago), increment backup files of 59th, 58th....45th, 20th, 19th, 18th till yesterday (missing were 44th day till the 21st day). Can we still restore to yesterday backup if using incremental ?
Statistics: Posted by zadrian — Apr 22, 2025 3:00 am
/english-betterindia/media/post_attachments/uploads/2022/05/Sustainable-home-6-1651667217.jpg)
