copy job question

[lowlander]

Hi,

we accidently checked "Read the entire restore point from source instead of synthesizing it from increments" for a copy job retaining archive restore points.

When we uncheck this checkmark, the copy job still uses increments on the source site. How can we enforce this setting to become active ?

thanks !

[PTide]

Hi,

When we uncheck this checkmark, the copy job still uses increments on the source site.

may I ask you how did you know that the copy job still uses increments from the source repo? Did "Active Full" sign appeared during the session?

How can we enforce this setting to become active ?

Did you mean "inactive"? When you uncheck that option the next backup copy session should do synthetic instead of active.

Thank you.

[lowlander]

Hi,

we now can see in the performance monitor that on the backup repository, -.vbk and -.vib files are being read by veeam. What you should expect is that on the target copy repository the incrementals and full backup is used to create a new full archived backup.

Can we enforce the next backup copy session by just disabling and enabling the copy job ?

Reason of this question is that we want to understand the creation of a archived full backup job on the copy repository side, by a copy job. Between the backup repository and the copy repository we have a leased line of 5MBps. When an archived full backup is being created on the copy repository : are al incremental backups read on the source or on the target side ? We have the idea for now the complete source backup chain is "read/transferred" accros the 5MBps line.

We would expect that by the creation of an archived full backup only the increment is transferred accross the line and the creation of the archived backup copy is taking place on the server with the backup copy target repository.

Thanks !

[lowlander]

Jeee....

missed this one

https://helpcenter.veeam.com/backup/vsp ... witch.html

assume that only the last changes in the backup are copied to the copy repository ?

thanks !

[veremin]

Not sure whether I got your question correctly, but active full backup won't happen immediately after switch, instead it will be created when time for GFS restore point comes. Thanks.

[lowlander]

Hi,

When using syntetic full with the copy job (checkbox unchecked), it is clear indeed that the next archived syntethic full will be created based on the schedule. When using syntethic full only the last incremental backup is copied from source to target, and processing is done on the target side > correct ?

[veremin]

When using syntetic full with the copy job (checkbox unchecked), it is clear indeed that the next archived syntethic full will be created based on the schedule

It won't be the so-called synthetic full, as the entire GFS restore point will be read from source backup - active full analogue recommended for dedupe devices.

When using syntethic full only the last incremental backup is copied from source to target, and processing is done on the target side > correct ?

Only changes happened since the last interval will be transferred in this case. If retention is reached, the oldest point in chain (.vbk) will be moved forward - forward forever incremental mode.

As to GFS restore point, it will be created when current retention settings are reached, and the oldest restore point will be moved to the day specified for GFS restore point creation

Thanks.