replication job name change triggers digest recalculation

[Yuya]

Hello,

I have a feature request.
After renaming an existing replication job, when we run the job twice, the digest is calculated in the second session.
I request to change the feature so that recalculation of digest is not done.

Detailed step
1.Create the replication job.
2.Start the replication job.
A replica VM is created.
3.Start the replication job again.
It has no problems.
4.Change the name of the replication job.
5.Start the replication job.
It has no problems.
6.Start the replication job again.
Calculating digests for Hard Disk

I contacted support (Case # 02686503) and they said that this behavior was a specification.
However, if I change the backup job name, the destination folder will not change, so even if I change the replication job name, I think that Veeam should not change the destination folder.

Regards,
Yuya

[foggy]

Hi Yuya, overall the behavior is expected, what looks strange is that digest re-calculation occurred on the second job run after renaming, while what I would expect is it occurring during the very next replication run. As for the feature request, do you really see this to be a problem? How often do you rename the jobs? In any case this is to ensure that replica is consistent, so you can consider this as an additional health check.