frequency of continuous replication

[coolgod]

please tell me the frequency which is used by veeam for continuous replication.

kindly advise whether it is recommended to use this setting?

Or should we configure "Periodically" and choose e.g 20 mins.

Thanks to give your views and recommendations.

[Vitaliy S.]

If you set "continuous" as a schedule to your replication jobs, then the next job run will be performed right after the previous job run is finished. It is not possible to say what frequency it would be, as it depends on many variables, such as processing rate, amount of changes, datastore performance etc.

What type of servers would you like to protect with this schedule?

[Gostev]

Or should we configure "Periodically" and choose e.g 20 mins

Normally, this would be a better choice. Continuous job schedule may put too much load on your storage due to constant VM snapshot activity.

[coolgod]

VM1 contains MS Exchange, Active Directory and File server
VM2 contains MS SQL Server

[coolgod]

also advise whether "periodically" will have any overlaping schedule?

[Vitaliy S.]

Yes, it will, but as I have explained in another topic Veeam backup server will not try to process the same VM with two different jobs at the same (we don't want to mess things up). Your jobs will be put in a queue and then will wait for an available slot in time (this is controlled by the backup server) to start the VM processing.

[coolgod]

Normally, this would be a better choice. Continuous job schedule may put too much load on your storage due to constant VM snapshot activity.

is 10 mins a reasonable gap ?

[Vitaliy S.]

How long does your incremental job pass take for these VMs?

[veremin]

Also, are you using Application Aware Image Processing for these VMs? Thanks.

[coolgod]

No Am not using Application Aware Image Processing

[coolgod]

How long does your incremental job pass take for these VMs?

about 30 Mins

[Vitaliy S.]

Then it seems like you can only set 30 min and above for your job replication cycle.

[flavor4real]

Hello,
Hope everybody is doing well. I just seen for the first time that there is a option saying "Run the Job periodically, continuously". What or how does Veeam 7.x do the continuously backup process? Does the application-aware image processing check influence the backup process when "continuously" is selected? Is it suitable for servers with DB's?

Thanks,

[foggy]

With continuous schedule, the job starts next cycle right after the previous one is finished. Performing VSS quiescence every few minutes throughout the day indeed can seriously affect VM performance, so consider doing crash-consistent backups in this case.

[flavor4real]

Thanks Foggy, ... got a quick question.
I've checked Enable application-aware image processing, use process setting "Require successful application processing", truncate logs on successful backup only", Index "everything". Do I have to check "Guest quiescence" (Enable VMware Tools quiescence)?

Asking because http://www.veeam.com/blog/how-to-create ... ackup.html mention (on the bottom) to check both.

Thanks...

[foggy]

It also says: "When you turn on both Application-aware image processing and VMware Tools quiescence, Veeam will use AAIP as the default method, and if VSS is not possible, fails over to VMware Tools quiescence."

So it is recommended to select it, if you have VMs in the job for which AAIP cannot be performed (for example, Linux VMs).

[foggy]

However, you need to select "Ignore application processing failures" instead of "Require successful application processing", otherwise, failover to VMware Tools quiescence on VMs that failed to use VSS will not be performed, the job will just fail.

[TrippleTee]

Does the replication only replicate the changes? I would assume so but want to confirm.
If this is the case then continuous replication work load will not be a lot (for servers that doesn't have much changes).

[Vitaliy S.]

Yes, replication job sends incremental data only, however, please keep in mind the snapshot overhead. Every time a replication job runs it creates and deletes a VM snapshot that might affect the performance of the application running inside the VM.