-
- Enthusiast
- Posts: 93
- Liked: never
- Joined: Sep 23, 2013 3:56 pm
- Contact:
Veeam Backup Copy Running Slow after interval expired
Hi, we have a backup copy job which had an interval time of 7 days (starting at 13:30), it was 3 and half days into the interval and we had some new backups we wanted to copy.
So at 9:00 we pressed on Sync now to copy the new backups to another location.
It was running great until 13:30 when Veeam decided that the copy interval had expired and the job restarted. I'm not sure why though we had changed the number of days and it hadn't got to 7 days since the last interval.
The backup copy job has 10 VMs in it and it had successfully copied the first two over quite quickly.
The log of the two VMs it copied show that it read 5-7% of the size of the disks.
- VM1 it read 30GB of a 430GB disk
- VM2 it read 25GB of a 500GB disk
But since the interval randomly expired, it has been going very slowly and reading more compared to the size of the disk.
- VM3 it read 100GB of a 280GB disk
- VM4 it read 26GB of a 40GB disk
Why is it going so slow, and is there anything I can do?
Thanks
So at 9:00 we pressed on Sync now to copy the new backups to another location.
It was running great until 13:30 when Veeam decided that the copy interval had expired and the job restarted. I'm not sure why though we had changed the number of days and it hadn't got to 7 days since the last interval.
The backup copy job has 10 VMs in it and it had successfully copied the first two over quite quickly.
The log of the two VMs it copied show that it read 5-7% of the size of the disks.
- VM1 it read 30GB of a 430GB disk
- VM2 it read 25GB of a 500GB disk
But since the interval randomly expired, it has been going very slowly and reading more compared to the size of the disk.
- VM3 it read 100GB of a 280GB disk
- VM4 it read 26GB of a 40GB disk
Why is it going so slow, and is there anything I can do?
Thanks
-
- Enthusiast
- Posts: 93
- Liked: never
- Joined: Sep 23, 2013 3:56 pm
- Contact:
Re: Veeam Backup Copy Running Slow after interval expired
The amount that it read for VM3 and VM4 is roughly about the same as the size of the vbk file.
I cant match the amount it read for VM1 and VM2 to anything.
Thanks
I cant match the amount it read for VM1 and VM2 to anything.
Thanks
-
- Product Manager
- Posts: 20400
- Liked: 2298 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Veeam Backup Copy Running Slow after interval expired
Looks like something has gone wrong with re-uploading mechanism. You can either wait till this "long" copying cycle is finished and call support, if the subsequent runs are crawling as well, or open a ticket now. Thanks.
-
- Enthusiast
- Posts: 93
- Liked: never
- Joined: Sep 23, 2013 3:56 pm
- Contact:
[MERGED] : Backup Copy Failing after retries
Hi, a backup copy job was taking longer than usual and the interval expired before it completed.
The VM it was processing was 90% complete.
After the interval expired it processed the VM again, taking alot longer to process it.
In the next 24 hours the job has failed 3 times, with each time it failing at the point where the interval expired.
The error messages which appear when the job fails at 90% are:
Wan connection failed to get trg backup corrupted segments.
Failed to validate target backup.
Sync task failed to process disk.
What should I do?
Many thanks
The VM it was processing was 90% complete.
After the interval expired it processed the VM again, taking alot longer to process it.
In the next 24 hours the job has failed 3 times, with each time it failing at the point where the interval expired.
The error messages which appear when the job fails at 90% are:
Wan connection failed to get trg backup corrupted segments.
Failed to validate target backup.
Sync task failed to process disk.
What should I do?
Many thanks
-
- Product Manager
- Posts: 20400
- Liked: 2298 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Veeam Backup Copy Running Slow after interval expired
Kindly, avoid creating multiple topics regarding same issue. Have you already contacted support team, as I've recommended above? Thanks.
-
- Enthusiast
- Posts: 93
- Liked: never
- Joined: Sep 23, 2013 3:56 pm
- Contact:
Re: Veeam Backup Copy Running Slow after interval expired
Hi, thanks for your reply.
This is a new issue, but no problem to merge the two together.
Support suggested that the speed was normal, and on another re-run of the job it was the same.
The backup copy job I posted about failed at 90% when the interval expired, and subsequent reruns have failed that the same point the interval expired
The reason for posting in the forum is that it is the weekend, and I thought I may be able to get some help from the forum.
This is a new issue, but no problem to merge the two together.
Support suggested that the speed was normal, and on another re-run of the job it was the same.
The backup copy job I posted about failed at 90% when the interval expired, and subsequent reruns have failed that the same point the interval expired
The reason for posting in the forum is that it is the weekend, and I thought I may be able to get some help from the forum.
-
- Enthusiast
- Posts: 93
- Liked: never
- Joined: Sep 23, 2013 3:56 pm
- Contact:
Re: Veeam Backup Copy Running Slow after interval expired
Hi, I've tried a few things and the job has now finished successfully. I'm not sure which cured the problem or if it just corrected itself on the 4th try, but these are the things I did.
- Removed the backups imported on the target server
- Resynced the repository on the target server
- Restarted the WAN Accelerator service on the target server
- Ran the backup copy job again
Thanks
- Removed the backups imported on the target server
- Resynced the repository on the target server
- Restarted the WAN Accelerator service on the target server
- Ran the backup copy job again
Thanks
-
- Product Manager
- Posts: 20400
- Liked: 2298 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Veeam Backup Copy Running Slow after interval expired
I'm also not sure what might be the cause of experienced problem. My wild guess was that something broke re-uploading mechanism, leading either to longer than usual copying cycle or complete failure.
Anyway, let's observe a job for a little while, and re-open a case in case the issue persists.
Thanks.
Anyway, let's observe a job for a little while, and re-open a case in case the issue persists.
Thanks.
Who is online
Users browsing this forum: No registered users and 61 guests