Problem with job options

[Erick]

Hello,
sorry for my bad english, but i'm french.

In our company, we have:
- A Backup Server with Veeam Backup&Replication v7.0
- 2 vmWare ESX 4.1.0 with a virtual center
- 40 VM with various OS an aplication than:
* Windows Server 2003 R2 with Oracle Database 10g
* Windows Server 2003 R2 with HyperFile DB (Windev)
* Windows Server 2003 R2 without any database
* Windows Server 2008 R2 64bits with Oracle Database 11g R2 64 bits
* Windows Server 2008 R2 64bits with Microsoft SQL Server
* Windows Server 2008 R2 64bits with HyperFile DB (Windev)
* Windows Server 2008 R2 64bits with ActiveDirectory
* Windows Server 2008 R2 64bits without any database
* Linux with Mysql
* Linux with Oracle Database 10g
* Linux without any database

Tools are installed on each VM.

I have "VmWare Tools quiescence" activted.
I've read that it's better to activate "Application-aware image processing" for ensure that backup are consistent.
Since I had activeted this option, my backup jobs are extremely slower (around 2 hours before, and 5 hours now)

Two questions:
- it is right that my jobs are so long?
- For each case of these VM, witch options are necessary ("VmWare Tools quiescence", "Application-aware image processing", etc.)

If possible, I wish backup my VM without stop databases.
Thanks for help.

[Vitaliy S.]

Hello Erick,

What are the bottlenecks stats for these two backup job runs (with and without application-aware image processing enabled)?

Thank you!

[Erick]

Hello,

I dont understand waht is "bottlenecks stats" or how can I verify this.
Can you tell me how to read this stats?

Thanks.

[foggy]

Bottleneck stats are available by right-clicking the job and selecting the Statistics command.

Also, I would like to know whether you have a single job including all the listed VMs or split them in several jobs in some manner and what are the application-aware image processing settings for these jobs.

[Erick]

This is stats with "Application-aware processing".
I'll desactivate it, run job and send you result in a few hours.

05/06/2014 07:55:47 :: Load: Source 27% > Proxy 12% > Network 5% > Target 90%
05/06/2014 07:55:47 :: Primary bottleneck: Target

I remember that without this option, the job take above 2 hours.

[foggy]

According to the bottleneck stats, the bottleneck for this job is write speed to the target storage, which does not have any common with enabling application-aware image processing. Anyway, debug logs should clearly tell which operations take most of the time during backup, so I suggest contacting support for reviewing them.

[Vitaliy S.]

BTW, what backup mode are you using? Reversed or forward?

[veremin]

Additionally, can you tell what particular AAIP options are set? For instance, is the indexing enabled or not? Also, was it full or incremental run that took longer than usual? Thanks.