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