Discussions specific to the VMware vSphere hypervisor
Post Reply
rmai
Lurker
Posts: 2
Liked: 2 times
Joined: Jul 25, 2019 1:40 pm
Contact:

VCSA Replication to DR Host is Failing

Post by rmai » Jul 25, 2019 2:05 pm 1 person likes this post

I having ongoing issues with a Veeam Replication job to a DR host that includes a single VMware VCSA VM that constantly fails. The VCSA VM has 13 disks. Every other Veeam Replication job goes through just fine. The failing VCSA Replication job output below is from the Action pane in Veeam Backup and Replication 9.5u4.

Case No.
03681615

Code: Select all

7/25/2019 9:10:46 AM :: Queued for processing at 7/25/2019 9:10:46 AM  
7/25/2019 9:10:46 AM :: Required backup infrastructure resources have been assigned  
7/25/2019 9:10:51 AM :: VM processing started at 7/25/2019 9:10:51 AM  
7/25/2019 9:10:51 AM :: VM size: 279.8 GB  
7/25/2019 9:10:54 AM :: Discovering replica VM  
7/25/2019 9:10:58 AM :: Getting VM info from vSphere  
7/25/2019 9:11:04 AM :: Creating VM snapshot  
7/25/2019 9:11:25 AM :: Preparing for transfer resume  
7/25/2019 9:11:40 AM :: Preparing replica VM  
7/25/2019 9:11:41 AM :: Processing configuration  
7/25/2019 9:11:50 AM :: Cannot find dirty block information in the previous restore point, CBT will not be used  
7/25/2019 9:11:54 AM :: Creating helper snapshot  
7/25/2019 9:12:04 AM :: Using source proxy 192.168.1.20 for disk Hard disk 2 [nbd]  
7/25/2019 9:12:04 AM :: Using source proxy 192.168.1.36 for disk Hard disk 1 [nbd]  
7/25/2019 9:12:04 AM :: Using source proxy 192.168.1.36 for disk Hard disk 7 [nbd]  
7/25/2019 9:12:04 AM :: Using source proxy VMware Backup Proxy for disk Hard disk 3 [nbd]  
7/25/2019 9:12:04 AM :: Using source proxy 192.168.1.20 for disk Hard disk 9 [nbd]  
7/25/2019 9:12:04 AM :: Using source proxy 192.168.1.36 for disk Hard disk 8 [nbd]  
7/25/2019 9:12:04 AM :: Using source proxy 192.168.1.20 for disk Hard disk 13 [nbd]  
7/25/2019 9:12:04 AM :: Using source proxy 192.168.1.36 for disk Hard disk 11 [nbd]  
7/25/2019 9:12:04 AM :: Using source proxy 192.168.1.36 for disk Hard disk 4 [nbd]  
7/25/2019 9:12:04 AM :: Using source proxy 192.168.1.36 for disk Hard disk 12 [nbd]  
7/25/2019 9:12:04 AM :: Using target proxy 192.168.1.36 for disk Hard disk 1 [nbd]  
7/25/2019 9:12:04 AM :: Using target proxy 192.168.1.36 for disk Hard disk 8 [nbd]  
7/25/2019 9:12:04 AM :: Using target proxy 192.168.1.20 for disk Hard disk 2 [nbd]  
7/25/2019 9:12:04 AM :: Using source proxy 192.168.1.36 for disk Hard disk 5 [nbd]  
7/25/2019 9:12:04 AM :: Using source proxy VMware Backup Proxy for disk Hard disk 10 [nbd]  
7/25/2019 9:12:04 AM :: Using target proxy 192.168.1.36 for disk Hard disk 4 [nbd]  
7/25/2019 9:12:04 AM :: Using target proxy 192.168.1.20 for disk Hard disk 9 [nbd]  
7/25/2019 9:12:04 AM :: Using target proxy VMware Backup Proxy for disk Hard disk 3 [nbd]  
7/25/2019 9:12:04 AM :: Using target proxy 192.168.1.20 for disk Hard disk 13 [nbd]  
7/25/2019 9:12:04 AM :: Using source proxy 192.168.1.20 for disk Hard disk 6 [nbd]  
7/25/2019 9:12:04 AM :: Using target proxy 192.168.1.36 for disk Hard disk 11 [nbd]  
7/25/2019 9:12:04 AM :: Using target proxy 192.168.1.36 for disk Hard disk 5 [nbd]  
7/25/2019 9:12:04 AM :: Using target proxy 192.168.1.36 for disk Hard disk 12 [nbd]  
7/25/2019 9:12:04 AM :: Using target proxy VMware Backup Proxy for disk Hard disk 10 [nbd]  
7/25/2019 9:12:04 AM :: Using target proxy 192.168.1.20 for disk Hard disk 6 [nbd]  
7/25/2019 9:12:04 AM :: Using target proxy 192.168.1.36 for disk Hard disk 7 [nbd]
7/25/2019 9:12:05 AM :: Calculating digests for Hard disk 3 (25.0 GB)  
7/25/2019 9:12:05 AM :: Calculating digests for Hard disk 10 (10.0 GB)  
7/25/2019 9:12:07 AM :: Calculating digests for Hard disk 1 (12.0 GB)  
7/25/2019 9:12:07 AM :: Calculating digests for Hard disk 8 (10.0 GB)  
7/25/2019 9:12:07 AM :: Calculating digests for Hard disk 4 (25.0 GB)  
7/25/2019 9:12:07 AM :: Calculating digests for Hard disk 5 (10.0 GB)  
7/25/2019 9:12:07 AM :: Calculating digests for Hard disk 2 (1.8 GB)  
7/25/2019 9:12:07 AM :: Calculating digests for Hard disk 9 (1024.0 MB)  
7/25/2019 9:12:07 AM :: Calculating digests for Hard disk 12 (100.0 GB)  
7/25/2019 9:12:07 AM :: Calculating digests for Hard disk 6 (10.0 GB)  
7/25/2019 9:12:07 AM :: Calculating digests for Hard disk 13 (50.0 GB)  
7/25/2019 9:12:08 AM :: Hard disk 11 (10.0 GB) 1.5 GB read at 37 MB/s 
7/25/2019 9:12:08 AM :: Hard disk 7 (15.0 GB) 1.4 GB read at 37 MB/s
7/25/2019 9:13:28 AM :: Removing VM snapshot
7/25/2019 9:13:47 AM :: Error: Unable to perform parallel VM disk processing
7/25/2019 9:13:47 AM :: Busy: Source 99% > Proxy 7% > Network 0% > Target 45%  
7/25/2019 9:13:47 AM :: Primary bottleneck: Source  
7/25/2019 9:13:47 AM :: Network traffic verification detected no corrupted blocks
7/25/2019 9:13:47 AM :: Processing finished with errors at 7/25/2019 9:13:47 AM
Which logs should I be looking in for more for more information?

rmai
Lurker
Posts: 2
Liked: 2 times
Joined: Jul 25, 2019 1:40 pm
Contact:

Re: VCSA Replication to DR Host is Failing

Post by rmai » Jul 25, 2019 8:01 pm 1 person likes this post

This was solved by:
1. Disabling automatic selection on the source and target proxies in the failing Replication job.
2. Lowering the max concurrent tasks on the source proxy.

Post Reply

Who is online

Users browsing this forum: No registered users and 10 guests