It is possible I did not make clear what I was trying to convey about RAID.ĪNOTHER NOTE: I have redesigned the site and for some reason, the comments are not showing. Won't such a test fail? Or does the test of an older backup pass if a file in the catalog is no longer in the source, or is in the current state of the exclusion list? Perhaps that is what I am missing.īut anyway, I just don't see the point of doing a test of an older backup.NOTE: Over the past few years, I have received a lot of messages and comments about this post. The backup catalog of such a backup may contain files that were removed from the destination is later backups (because they were deleted from the source, or added to the exclusion list). Yes, but in a type (b) test FBackup allows (even encourages) the user to test previous backups. If you manually delete a file from the backup destination, it will be reported in a warning at the end of the test. Softland wrote:When a file in destination is deleted by FBackup because the file was removed from sources, that file will be also removed from catalog, so it will be not searched when running a test. So I am puzzled by the design decision not to allow this more useful test to be made on demand.īut in any case, I think that all tests (a), (b)) and (c) need to be more carefully described in the manual. So I do not see the purpose of a type (b) test (at least in the case where deleted files are always removed from the backup).įor me, the type (c) test is far more useful because it tests whether all the files that are currently supposed to be in the backup set are actually there, and still match the one in the source tree. If I now do a type (b) test of Backup1, then it will fail because SomeFile.txt is missing from the backup. Then on Day 2 I delete SomeFile.txt and the backup job Backup2 removes SomeFile.txt from the backup. I create a File SomeFile.txt and backup job Backup1 completes without errors, so that SomeTile.txt is in the backup. What is bothering me about the type (b) test is what happens when I am removing deleted and excluded items from the backup. (c) can be executed only scheduled and you cannot select which versions to be tested (b) can be run manually and you can select which version will be tested (you can select all versions too) Softland wrote:The differences between (b) and (c) are: I tried touching the file (using git bash) and re-running the backup, but FBackup did not recopy the file. Indeed, checking with fc.exe revealed an error in one byte. The test revealed a CRC error on just one (binary) file. It took about 5 hours, and the test took about 2 hours. Why can this full type (c) test only be scheduled, and not run immediately, just as the Backup task can be either run immediately or scheduled?Īlso what should the user do when a test fails? For example, I just did an initial backup of about 300 GB of data on my Windows 10 workstation to a shared drive attached to a different Windows 10 machine (which acts as a kind of HomeServer). In my opinion, it ought to be possible to perform a type (c) test from this window, perhaps as an extra "Current status" line in the table. Test (b) I not quite sure what it does, because I do not understand how it treats files that were legitimately removed form the source (and hence the backup) subsequent to the backup in question. Worth doing occasionally, in my opinion, to check that the backup has not been accidentally (or maliciously) removed or damaged. Test (c) tests all the files that are currently in the backup. This is obviously worth doing (even essential) in my opinion. Test (a) checks that files copied in the current backup were copied correctly. All of these need to be more fully explained in the manual. In fact there are three kinds of test: (a) the test performed after each backup, (b) the test available on the main window, and (c) the scheduled test. But this needs to be explained in the manual. The test after backup will test only the files from that backup, but a complete test you schedule will test all the files from the catalog. When you create a scheduled task in Backup Properties->Scheduler, you can select the Test action to be executed. Softland wrote:I am not talking about the Test button from the toolbar.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |