- Posts: 15
- Liked: never
- Joined: Mar 10, 2010 1:01 am
- Full Name: Dan
Enviornment - Veeam backup 4.1.1. replicating from a san attached ESX 3.5 host (Virtual centre managed) to an ESX 4 host through a firewall
Veeam setup - replication job (via network with encryption) both with and without VSS intergration have been tested
Replicating file "[SAN01] bne1/bne1_1-flat.vmdk" BackupDisk failed Client error: File too large POSIX: Failed to write data to the file [/vmfs/volumes/4bb0882b-07983c18-0cfa-002655d0b781/VeeamBackup/bne1(vm-181)/bne1_1-flat.vmdk]. Server error: An existing connection was forcibly closed by the remote host Failed to process VM disk backup. VMDK path: [vddk://<vddkConnSpec><viConn name="10.1.70.2" authdPort="902" vicPort="443" /><vmxPath vmRef="vm-181" datacenterRef="datacenter-2" datacenterInventoryPath="DC01" snapshotRef="snapshot-856" datastoreName="SAN01" path="bne1/bne1.vmx" /><vmdkPath datastoreName="SAN01" path="ckbne1/ckbne1_1.vmdk" /><transports seq="nbdssl" /><readBuffer size="2097152" /></vddkConnSpec>].
thanks in advance
- Product Manager
- Posts: 22697
- Liked: 1498 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
Tracking ticket number is automatically generated as soon as you email us to firstname.lastname@example.org, please check your spam filter. As for the isssue you have, yes it would be helpful to know what is the current VMFS block size on your target datastore.
Users browsing this forum: Baidu [Spider], Google [Bot], Majestic-12 [Bot] and 32 guests