I'm setting up two PBS servers to support a PVE cluster in Washington (WA). The PBS servers are in two different states (PBS-WA, Washington) (PBS-OR, Oregon). PBS-OR is the off-site backup for PBS-WA. Therefore, PBS-OR has a sync job to copy PBS-WA to PBS-OR.
When the sync on PBS-OR completes, I'm surprised to see that the "Verify State" column of the Datastore: primary / Content view shows many green checkmarks. It appears that PBS-OR is inheriting the verification status of PBS-WA. Is this correct? If so, why is that safe?
Since PBS-OR and PBS-WA are physically separate storage their bit rot (1) is independent of each other. It seems to me that PBS-OR's Verify State should indicate the result of verification tasks on PBS-OR's drives, not PBS-WA's drives.
It is recommended that you reverify all backups at least monthly, even if a previous verification was successful. This is because physical drives are susceptible to damage over time, which can cause an old, working backup to become corrupted in a process known as bit rot/data degradation. -- https://pbs.proxmox.com/docs/maintenance.html#verification
When the sync on PBS-OR completes, I'm surprised to see that the "Verify State" column of the Datastore: primary / Content view shows many green checkmarks. It appears that PBS-OR is inheriting the verification status of PBS-WA. Is this correct? If so, why is that safe?
Since PBS-OR and PBS-WA are physically separate storage their bit rot (1) is independent of each other. It seems to me that PBS-OR's Verify State should indicate the result of verification tasks on PBS-OR's drives, not PBS-WA's drives.
It is recommended that you reverify all backups at least monthly, even if a previous verification was successful. This is because physical drives are susceptible to damage over time, which can cause an old, working backup to become corrupted in a process known as bit rot/data degradation. -- https://pbs.proxmox.com/docs/maintenance.html#verification