Page 2 of 2

Re: Guarding against backup loss/damage

Posted: Thu Sep 06, 2018 9:19 am
by Softland
Hi,

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.

About your last question:
In Scheduler, when Test is selected, the Backup Numbers box is displayed. You can type in there the backup numbers you want to test. Use the * character to test all backup numbers, or the # character to test only the last backup.

Re: Guarding against backup loss/damage

Posted: Sun Sep 09, 2018 7:28 am
by davewilk
Softland wrote: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 backup, that backup does not know that a file was later deleted from the source and destination. So this backup cannot be tested in isolation. This is what is puzzling me.

Re: Guarding against backup loss/damage

Posted: Mon Sep 10, 2018 8:01 am
by Softland
Hi,

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.

Re: Guarding against backup loss/damage

Posted: Fri Sep 14, 2018 7:59 am
by davewilk
Softland wrote: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 doing the backups. I will check this out when I get home.