Comprehensive data protection for all workloads
Post Reply
cicero
Enthusiast
Posts: 39
Liked: never
Joined: Mar 18, 2009 9:48 am
Full Name: David Winkler
Contact:

Problems taking a Backup to lokal disk

Post by cicero »

Hi,

writing a Backup of an ESX Host/Guest to a local disk on the veeam server (physical),
exits after snapshoting with following error:

Code: Select all

Backing file "/vmfs/volumes/49ca6c0b-68dde988-6282-00215e52a7f6/srv012oracle/vmware-14.log" 
Backup failed Client error: Ein Socketvorgang konnte nicht ausgefuehrt werden, da dem 
System Pufferspeicher fehlte oder eine Warteschlange voll war 
Unable to retrieve next block transmission command. 
Number of already processed blocks: [0]. 
Server error: Connection reset by peer Backup request cannot be processed. 
Source file path: [/vmfs/volumes/49ca6c0b-68dde988-6282-00215e52a7f6/srv012oracle/vmware-14.log]. 
maybe intesting lines of the local log:

Code: Select all

[25.07.2009 22:22:27] <01> Info  Agent command: "backupFile\nveeamfs:4:079d9fed-f7da-4b98-bbaa-ed2e84d7c8d3 (16)/vmware-14.log@D:\srv246esx\b_srv246esx.vbk\nveeamfs:4:079d9fed-f7da-4b98-bbaa-ed2e84d7c8d3 (16)/vmware-14.log@\n/vmfs/volumes/49ca6c0b-68dde988-6282-00215e52a7f6/srv012oracle/vmware-14.log\n"
[25.07.2009 22:22:27] <13> Info    (Client) Service output: --size: 2213549\n
[25.07.2009 22:22:28] <09> Info    (Server) Service error: Connection reset by peer\n--tr:Cannot write data to the socket. Data size: [1063828].\n--tr:Serialization of the buffer with data has failed.\n--tr:Failed to serialize file block. Block identity: [Ordinal number: 0, offset: 0, size: 1048576].\n--tr:Failed to send next file block. Block identity: [Ordinal number: 0, offset: 0, size: 1048576].\n--tr:Unable to asynchronously write data block. Block identity: [Ordinal number: 0, offset: 0, size: 1048576].\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/49ca6c0b-68dde988-6282-00215e52a7f6/srv012oracle/vmware-14.log].\nBackup request cannot be processed. Source file path: [/vmfs/volumes/49ca6c0b-68dde988-6282-00215e52a7f6/srv012oracle/vmware-14.log].
[25.07.2009 22:22:28] <12> Info    (Client) Service error: Ein Socketvorgang konnte nicht ausgef³hrt werden, da dem System Pufferspeicher fehlte oder eine Warteschlange voll war
[25.07.2009 22:22:28] <12> Info    (Client) Service error: --tr:Cannot read data from the socket. Requested data size: [1063828].
[25.07.2009 22:22:28] <12> Info    (Client) Service error: --tr:Unserialization of the buffer with data has failed.
[25.07.2009 22:22:28] <12> Info    (Client) Service error: --tr:Failed to unserialize file block. Block identity: [Ordinal number: 0, offset: 0, size: 1048576].
[25.07.2009 22:22:28] <12> Info    (Client) Service error: Unable to retrieve next block transmission command. Number of already processed blocks: [0].
[25.07.2009 22:22:28] <12> Info    (Client) Service error: --tr:Next asynchronous read request cannot be processed.
[25.07.2009 22:22:28] <12> Info    (Client) Service error: --tr:Asynchronous data reader has failed.
[25.07.2009 22:22:28] <12> Info    (Client) Service error: --tr:Failed to process conveyored task.
[25.07.2009 22:22:28] <12> Info    (Client) Service error: --tr:Cannot download FIB. FIB: [079d9fed-f7da-4b98-bbaa-ed2e84d7c8d3 (16)\vmware-14.log]. Declared FIB size: [2213549]. Is extent: [false].
[25.07.2009 22:22:28] <09> Info    (Client) Service: closed
[25.07.2009 22:22:28] <12> Info    (Client) Service error: --tr:Unable to receive FIB from network. FIB: [079d9fed-f7da-4b98-bbaa-ed2e84d7c8d3 (16)\vmware-14.log].
[25.07.2009 22:22:28] <12> Info    (Client) Service error: --tr:Unable to handle archiver commands.
[25.07.2009 22:22:28] <13> Info    (Client) Service error: --tr:Remote file backup has failed. File: [/vmfs/volumes/49ca6c0b-68dde988-6282-00215e52a7f6/srv012oracle/vmware-14.log]. VBK: [vmware-14.log]. RBK: [vmware-14.log].
[25.07.2009 22:22:28] <13> Info    (Client) Service error: Cannot backup file in the service console mode. File: [/vmfs/volumes/49ca6c0b-68dde988-6282-00215e52a7f6/srv012oracle/vmware-14.log]. VBK: [veeamfs:4:079d9fed-f7da-4b98-bbaa-ed2e84d7c8d3 (16)/vmware-14.log@D:\srv246esx\b_srv246esx.vbk]. RBK: [veeamfs:4:079d9fed-f7da-4b98-bbaa-ed2e84d7c8d3 (16)/vmware-14.log@].
[25.07.2009 22:22:28] <13> Info    (Client) Service error: --tr:Client failed to process the command. Command: [backupFile].
[25.07.2009 22:22:28] <09> Info    (Server) Service: closed
replication works like a charme ...

any idea?

Thanks, David

cicero
Enthusiast
Posts: 39
Liked: never
Joined: Mar 18, 2009 9:48 am
Full Name: David Winkler
Contact:

Re: Problems taking a Backup to lokal disk

Post by cicero »

to force the agentless mode did it for me.

Thanks, David

Gostev
SVP, Product Management
Posts: 26883
Liked: 4359 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Problems taking a Backup to lokal disk

Post by Gostev »

David, agent mode provides better perfromance, so in case of full ESX it is best to use agent mode, not agentless. I recommend that you contact our support so that we could investigate and try to address the problem above, so that you can use agent mode and get better performance. Thank you.

Post Reply

Who is online

Users browsing this forum: Egor Yakovlev, tjurgens, tom.locklin and 61 guests