Replica Metadata Behavior and Verification after Terminated Jobs

[matsusan]

I have a few questions regarding replica metadata (digests) behavior when a replication job is terminated prematurely.

My Understanding:

• Metadata Generation: Replica metadata is generated and updated dynamically during a replication job.

• Valid Metadata: If the metadata is consistent and valid, the next run will perform a CBT-based incremental read.

• Invalid/Corrupted Metadata: If the metadata is invalid, the next run forces a fallback to a full read/scan.

Questions:

• If a job is terminated prematurely (canceled or stopped), is the metadata generated during that session flagged as invalid?
  Or can it be partially saved as valid depending on when it was stopped?

• Is there a way (via logs, GUI, or PowerShell) for users to verify:
  - If the metadata was successfully saved after a terminated session?
  - Whether the next run will be an incremental or a full read based on the metadata state?

Thanks,
Ryoma

[david.domask]

Hi Ryoma,

Your understanding is mostly correct; typically an aborting error on the Replica job will not trigger Digests Calculation. The usual culprits for this are when the target replica has been altered externally and Veeam needs to verify what blocks already exist for the target replica or when the replica metadata on the selected repository has been corrupted.

To answer your questions directly:

1. Typically no, but this will heavily depend on the nature of the error. (e.g., if there is issue writing digests to the metadata / the existing metadata has become corrupted, that will trigger Digests Calculation. Network errors or hypervisor errors typically will not)
2. No method exists. If you experience an unexpected Digests Calculation, open a Support Case and allow Veeam Support to review the debug logs to understand the root cause of the Digests Calculation.