Backup over WAN

[dennes]

Hi,
One of our clients is currently backing uo their ESX4 environment to a SATA backup NAS located in an adjacent building, connected via 100Mbit ethernet. Daily incrementals are about 12GB.
Now they are about to move to another location, which doesn't have a LAN attached building nearby, where we could place the backup NAS and thus have an off-site backup as we do now. They don't want a tape solution.
The new location has a 10Mbit/10Mbit fiber connection to the internet, so my plan is to place the backup NAS in a remote colocated datacenter, which would require us to backup over the internet connection (WAN) to the DC.
Is this a supported configuration? And will this work? Is anybosy else using a similar setup?

Thanks,
Dennes

[Gostev]

Hello Dennes, Veeam Backup will work with any link speed, but of course 10Mbit is too slow link for the amount of changed data you have (12GB daily) - so backups will be taking too long.

[b.thoele]

I have been haven't been able to keep the Veeam connection alive across a 3Mb WAN connection. The initial sync will get 10Gb in to a 80Gb replication and fail. Is there a way the restart the ssh connection or start off where I left? I other problem is that the job just hangs and leaves an open delta vdmk. Veeam support please help.

Here is the log.
[04.12.2009 21:46:18] <06> Info Task progress: 9%, 7,247,770,682 of 80,530,636,800 bytes, object 6 of 6
[04.12.2009 21:46:18] <06> Info Job progress: 9%, 7,247,770,682 of 80,530,636,800 bytes, task 1 of 1
[04.12.2009 22:23:56] <06> Info (Client) Service output: 10\n
[04.12.2009 22:23:56] <06> Info Task progress: 10%, 8,053,077,050 of 80,530,636,800 bytes, object 6 of 6
[04.12.2009 22:23:56] <06> Info Job progress: 10%, 8,053,077,050 of 80,530,636,800 bytes, task 1 of 1
[04.12.2009 23:00:55] <06> Info [Ssh] Connection::Error, Error: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond, Message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[04.12.2009 23:01:08] <05> Warning SSH2 WatchDog is stopped: An existing connection was forcibly closed by the remote host
[04.12.2009 23:16:41] <06> Info (Server) Service error: Connection timed out\n--tr:Cannot write data to the socket. Data size: [1048576].\n--tr:Failed to serialize data area. ID: [8418]. Offset: [8826912768].\n--tr:Failed to send next file block. Block identity: [Data block. Start offset: [8826912768], Length: [1048576], Area ID: [8418].].\n--tr:Unable to asynchronously write data block. Block identity: [Data block. Start offset: [8826912768], Length: [1048576], Area ID: [8418].].\n--tr:Processing of asynchronous write requests has failed. Output file: [File blocks transmission channel (sender).].\n--tr:Failed to process conveyored task.\n--tr:FIB uploader: Unable to upload FIB. FIB path: [/vmfs/volumes/49959f36-aa067125-2cce-00221923d955/Exch20/Exch20-flat.vmdk].\nBackup request cannot be processed. Source file path: [/vmfs/volumes/49959f36-aa067125-2cce-00221923d955/Exch20/Exch20-flat.vmdk].
[04.12.2009 23:16:41] <06> Info (Server) Service: closed

[Gostev]

Ben, please note that this is not a support forum, for support please call or email our support at support@veeam.com

Although this looks like SSH connection drop to me. Veeam can replicate over slow connections, but they have to be reliable. Packet loss is fine, but if there is a connection drop, we cannot handle it. There is no way to restart the connection and continue replication where it left.