RPTan wrote:what I meant is that can we redo the job from the last good replication point before the error occurred, and not the full incremental again?
RPTan wrote:On a side note, what causes slow performance for digest calculation, especially for large VMs (multi-disks of mutli-TBs each)? What performance can we expect anyway?
We use hot-add mode, with a source and target proxy, and have placed the metadata repository at the production side.
why does veeam calulate the digests if production and dr-site have a fast connection to each other?
is there a way to suppress the calculation of digests for specific jobs and replication the whole disks instead?
DGrinev wrote:You can manually run Active Full through UI by right clicking on the VM, this could be much faster than digest calculation.
DGrinev wrote: in order to run active full, you should delete the target replica VM.
That's why it's not recommended way due to potential risk of losing replicas.
Users browsing this forum: No registered users and 11 guests