Replication job change deletes my replication

[ady_td]

I have a job that has 6 servers in it and they have conpleted a full replication, I wanted to take one of the server out and put in its own replication job, so i removed it and set a new job using the same ESX server and storage and using the same naming convension ( _ replica) the job ram but it deleted the current replication and started again.

Is this the normal action or have I don something wrong. ?

Anyone had this same scenario before ?

[Vitaliy S.]

Hello Ady,

As far as creating a new replication job always causes a full job run, I believe that this made you think your previous replica was deleted. There is no possibility to run a full run with one job and incremental pass with another, as VM's ChangeID cannot be shared with multiple jobs. So yes, this is an expected behavior.

Thanks!

[thatvmwareguy]

Is it possible to have a single job that does a full replication once a week and incrementals the rest of the week?

Thanks
Stu

[Vitaliy S.]

Hello Stuart,

As we use Synthetic way of backup there is no need to perform full job runs, as on each incremental job your replicated VM image is updated to the most current state.

However, functionality of creating full backups on specified days is available for backup jobs only. Hope this helps!

[Gostev]

Stuart is talking about replication though, which does not support periodic active fulls.