-
- Enthusiast
- Posts: 57
- Liked: 3 times
- Joined: Apr 09, 2009 1:00 am
- Full Name: J I
- Contact:
Calculating Digests really slow - normal?
Hi,
Did a Veeam backup to USB disk, restored at target site. Setup replication jobs to replicate the VM's, the jobs run REALLY slowly - eg; hard disk 1 is 15GB, it took 16 hours to calculate digests then 35 minutes to replicate the changes. The 2nd hard disk is 150GB in size its been calculating digests for 7 hours now and is only 3% of the way through. Is this normal? Is there anyway to speed this process up?
Cheers
Did a Veeam backup to USB disk, restored at target site. Setup replication jobs to replicate the VM's, the jobs run REALLY slowly - eg; hard disk 1 is 15GB, it took 16 hours to calculate digests then 35 minutes to replicate the changes. The 2nd hard disk is 150GB in size its been calculating digests for 7 hours now and is only 3% of the way through. Is this normal? Is there anyway to speed this process up?
Cheers
-
- VP, Product Management
- Posts: 6035
- Liked: 2860 times
- Joined: Jun 05, 2009 12:57 pm
- Full Name: Tom Sightler
- Contact:
Re: Calculating Digests really slow - normal?
Do you have a proxy on the target side? Is it being properly used? Sounds like probably not. You might have to manually select the proxy.
-
- Enthusiast
- Posts: 57
- Liked: 3 times
- Joined: Apr 09, 2009 1:00 am
- Full Name: J I
- Contact:
Re: Calculating Digests really slow - normal?
legend thanks... its always the simple things one overlooks... much faster now with the target proxy configured
-
- Enthusiast
- Posts: 51
- Liked: never
- Joined: Mar 21, 2012 5:43 pm
- Full Name: Carlos Chacon
- Contact:
Re: Calculating Digests really slow - normal?
yeah must faster now with a proxy at the recovery site, one more question guys
the metadate replica must be in the source site right? or in can be stored at the recovery site I mean because my veeam can crash and the metadata can be stored in it?
the metadate replica must be in the source site right? or in can be stored at the recovery site I mean because my veeam can crash and the metadata can be stored in it?
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Calculating Digests really slow - normal?
Hi Carlos,
Replica metadata should be stored on the source site as it is described by the corresponding label next to the repository choice options. Having metadata on the source site allows you to calculate VM digest information in a much quicker way. Be aware that there is no point in hosting metadata files on the remote site, since this data is not required during DR (failover) situations.
Thanks!
Replica metadata should be stored on the source site as it is described by the corresponding label next to the repository choice options. Having metadata on the source site allows you to calculate VM digest information in a much quicker way. Be aware that there is no point in hosting metadata files on the remote site, since this data is not required during DR (failover) situations.
Thanks!
-
- Novice
- Posts: 5
- Liked: never
- Joined: May 02, 2017 2:48 pm
- Full Name: Peter Millard
- Contact:
Re: Calculating Digests really slow - normal?
Hi there,
Just picking up on this again.
We have replication jobs that are also taking hours to generate the digests for the disks.
These jobs have multiple servers within that are potentially on different hosts.
I have specified the proxy servers that reside on each host that could be hosting the VM for both the target and destination, so multiple proxy's are selected.
So for example we have 3 hosts each with a proxy in site1 and 3 hosts each with a proxy in site2.
I have specified each proxy in site1 where the VM resides and selected each proxy in site 2 where the vm is being replicated to.
Is this the best practice?
Many thanks
Just picking up on this again.
We have replication jobs that are also taking hours to generate the digests for the disks.
These jobs have multiple servers within that are potentially on different hosts.
I have specified the proxy servers that reside on each host that could be hosting the VM for both the target and destination, so multiple proxy's are selected.
So for example we have 3 hosts each with a proxy in site1 and 3 hosts each with a proxy in site2.
I have specified each proxy in site1 where the VM resides and selected each proxy in site 2 where the vm is being replicated to.
Is this the best practice?
Many thanks
-
- Veteran
- Posts: 1943
- Liked: 247 times
- Joined: Dec 01, 2016 3:49 pm
- Full Name: Dmitry Grinev
- Location: St.Petersburg
- Contact:
Re: Calculating Digests really slow - normal?
Hi Peter,
Yes, it's recommended approach to have dedicated proxies in both sites.
Please review this article as it contains replication best practices. Thanks!
Yes, it's recommended approach to have dedicated proxies in both sites.
Please review this article as it contains replication best practices. Thanks!
Who is online
Users browsing this forum: Google [Bot] and 64 guests