4 ms·
> later, when I tried to extract some large files from the backup, I saw that they had been replaced with some text files, containing a message that the downloa
by ansible 3y ago
> later, when I tried to extract some large files from the backup, I saw that they had been replaced with some text files, containing a message that the download of those files failed.
That's a really asinine failure mechanism. At the very least, it should create "filename-FAILED_TO_RESTORE" or something like that.
Something that I was instructed to do nearly 30 years ago when at Motorola was: never overwrite the original files. Standard procedure was to make a directory called "BACKUP" (or "RESTORE"?) and put the files in there instead. The requesting person was then responsible for moving the files back to their original location, so any screwups were on them, not us (IT).
- justsomehnguy 3y agoThe dogfooding was a thing 30 years afo.
- ThePowerOfFuet 3y agoSun did it much more recently than that.
- bobbylarrybobby 3y agoI think the only correct way to handle failures is to have a single file called ONE_DRIVE_RESTORE_FAILURES.txt at the restore destination root, and in it list the path to every file that failed to download, one path per line. Much harder to miss than individual files with conspicuous names.