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.
Guarding against backup loss/damage
-
- Posts: 1993
- Joined: Thu May 23, 2013 7:57 am
Re: Guarding against backup loss/damage
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.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.
-
- Posts: 1993
- Joined: Thu May 23, 2013 7:57 am
Re: Guarding against backup loss/damage
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.
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
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.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.