The backup is tested against the catalog. If the file was deleted in a newer backup, the catalog was updated and FBackup knows that from the catalog. Thanks for the replies. I think I understand now but I am actually travelling (in Europe) at the moment, so do not have access to the machine that is...

About the test: in catalog, each file has an id. If that file was deleted from source and from destination (by FBackup), the file with that id will be marked in catalog as deleted and it will no longer be tested, no matter in which backup version it was included. But if I am testing an earlier back...

Softland wrote:FBackup can run multiple backups in the same time. If your computer has enough resources to run multiple backups in the same time, you can do that.

Thanks for the answer.

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. If you manually delete a file from the backup destination, it will be reported in a warning at the end of the test...

Maybe I am still not understanding exactly what tests (a) (b) and (c) do.

Is it a good or bad idea to let more than one backup job run at a time?

That is, suppose I have several jobs that I want to run around midnight every day, and that each job typically runs a few minutes. Should I just start them all at midnight, or should I make some effort to stagger them?

The differences between (b) and (c) are: - (b) can be run manually and you can select which version will be tested (you can select all versions too) - (c) can be executed only scheduled and you cannot select which versions to be tested Yes, I understand that. What is bothering me about the type (b)...

I am not talking about the Test button from the toolbar. When you create a scheduled task in Backup Properties->Scheduler, you can select the Test action to be executed. The test after backup will test only the files from that backup, but a complete test you schedule will test all the files from th...

The size in catalog is the size of the file read from Windows. If the size is different, it means FBackup was not able to read the correct size probably because of the Volume Shadow Copy service (it could be in use/locked even if IE is not running). Try to make a copy of that file and run again the...

You can also schedule a backup test, to make sure there are no errors/warnings (also including missing files). This way you will run the complete mirror only when the test returns warnings/errors. You mean use the "Test" button that is on the main window? What does this do exactly? Is it the same a...