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?When we uncheck this checkmark, the copy job still uses increments on the source site.
Did you mean "inactive"? When you uncheck that option the next backup copy session should do synthetic instead of active.How can we enforce this setting to become active ?
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 ?
Users browsing this forum: No registered users and 1 guest