Hi everybody,
I am encounteering some issues with my backups. My company's is split into two places, and I recently moved my QNAP from one place to another. There's a VPN (20 mbits) between the two sites.
But since I moved the "target", all my VM's backup are randomly slow. For example, one virtual machine takes 24 minutes to read 1.7 Gbits, but the next one (on the same ESX) takes about 54 minutes to read... 928 mbits.
There's two ESX to backup, for approximatively 20 VMs.
Why veeam takes so much time to read this files? Its an incremental backup, btw, running at 4:00 am.
I also note that the source is "bottlenecked" at 99%. I've checked data transfer speed on the primary switch, no problems.
Here are the screenshots:
http://cjoint.com/data/0FdkElCE9Kx.htm
http://cjoint.com/data/0FdkFPx9PP2.htm
Thanks a lot!
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Jun 03, 2014 7:51 am
- Full Name: Vault-Tec
-
- Veeam Software
- Posts: 21138
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Veeam takes too much time to "read"
Could you please clarify, is this QNAP NAS used to store original VMs or it is a backup target (used to store backups)?
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Jun 03, 2014 7:51 am
- Full Name: Vault-Tec
Re: Veeam takes too much time to "read"
Thanks for you answer!
It's a backup target. As I said, original VM's are stored thanks to ESX 1 and 2, QNAP is only used to store backups.
It's a backup target. As I said, original VM's are stored thanks to ESX 1 and 2, QNAP is only used to store backups.
-
- Chief Product Officer
- Posts: 31805
- Liked: 7298 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Veeam takes too much time to "read"
Hi it's not read that is taking time, but something else. Veeam is not slow to read - as the screenshots show, data was read very fast in both cases (speed is about the same in both cases). You should open a support case and have our engineers investigate the debug logs to see what is causing the duration to be so long. Perhaps some finalization process hangs in VDDK, or something like that. Thanks!
Who is online
Users browsing this forum: Bing [Bot], Google [Bot], stevetNOVUS and 151 guests