How to investigate on backup errors

Backup agent for Linux servers and workstations on-premises or in the public cloud

How to investigate on backup errors

Veeam Logoby pama » Mon Jul 04, 2016 12:48 pm

Hi,
my backup fails everytime:

Code: Select all
               Backup session on XXX [0] %                                                   Status: Failed




               Summary                                          Data

               Duration:           00:02:43                     Processed:          524.3 KB (0%)
               Processing rate:    746.8 KB/s                   Read:               524.3 KB
               Bottleneck:         Source                       Transferred:        53.4 KB (9.8x)


               Time                Action                                                            Duration

               2016-07-04 14:36:12 Job started at 2016-07-04 14:36:12
               2016-07-04 14:36:13 Starting backup
               2016-07-04 14:36:13 Some backup files are missing in repository.
               2016-07-04 14:36:14 Creating volume snapshot                                          00:02:25
               2016-07-04 14:38:40 Backing up BIOS bootloader on /dev/sda                            00:00:01
               2016-07-04 14:38:41 [error] Backing up /dev/sda 512.0kB at 3.6MB/s (0%)               00:00:00
               2016-07-04 14:38:55 [error] Snapshot overflow.
               2016-07-04 14:38:55 [error] Failed to perform backup


How may I investigate on the errors?
Thank you
pama
Enthusiast
 
Posts: 38
Liked: 1 time
Joined: Wed Apr 20, 2011 1:02 pm
Full Name: Andrea de Lutti

Re: How to investigate on backup errors

Veeam Logoby pama » Mon Jul 04, 2016 1:56 pm

Edit:
I have found logs in /var/log/veeam.
Can you help me to solve it?

My server is running on HP Microserver G7, it has two disk in raid1 (hardware mode)
Backup is mapped on a CIFS share.
When it run, it saves this error, otherwise it hangs and I have to rebbot the server (no more network connection)


Code: Select all
[04.07.2016 14:38:40] <140691568428800>        | WARN|Unable to preallocate disk using vmkfstools v4.
[04.07.2016 14:38:40] <140691568428800>        | WARN|Unable to preallocate disk space using ioctl.
[04.07.2016 14:38:40] <140691568428800>        |     [1,048,576] bytes were preallocated for the file [/tmp/{a9624750-9f98-43f1-a901-c93a011f069e}/bootloader_dev_sda].
[04.07.2016 14:38:40] <140691568428800> lpbcore|     [9d35] >> : srcBackupFile
[04.07.2016 14:38:40] <140691568428800> lpbcore|     [9d35] >> : veeamfs:5:/7230af24-fc7d-4c4b-8c8b-298bccc283a0 ({80a62c27-d21d-b211-8000-28924a305d6d})/bootloader_dev_sda@/tmp/veeam/artuOCbackup$/OCbackup/OCbackup_2016-07-04T143839.vbk
[04.07.2016 14:38:40] <140691568428800> lpbcore|     [9d35] >> :
[04.07.2016 14:38:40] <140691568428800> lpbcore|     [9d35] >> : /tmp/{a9624750-9f98-43f1-a901-c93a011f069e}/bootloader_dev_sda
[04.07.2016 14:38:40] <140691568428800> lpbcore|     [9d35] >> : true
[04.07.2016 14:38:40] <140691568428800> lpbcore|     [9d35] >> : false
[04.07.2016 14:38:41] <140691540268800> lpbcore|     [9d35] out: --size: 1048576
[04.07.2016 14:38:41] <140691540268800> lpbcore|     [9d35] out:
[04.07.2016 14:38:41] <140691540268800> lpbcore|     [9d35] out: --pex:0;524288;0;0;524288;53380;98;100;69;0;0;0;131121095213118990
[04.07.2016 14:38:41] <140691540268800> lpbcore|     [9d35] out: --pex:50;1048576;524288;0;1048576;53412;98;100;69;0;0;0;131121095213120210
[04.07.2016 14:38:41] <140691540268800> lpbcore|     [9d35] out: --pex:100;1048576;524288;0;1048576;53412;98;100;69;99;100;69;131121095213315980
[04.07.2016 14:38:41] <140691540268800> lpbcore|     [9d35] out: >
[04.07.2016 14:38:41] <140691568428800> lpbcore|   Backing up BIOS bootloader [Grub2]. ok.
[04.07.2016 14:38:41] <140691568428800> lpbcore|   Backing up disk object: [/dev/sda].
[04.07.2016 14:38:41] <140691568428800> lpbcore|     Starting backup client for agent with UID [{eee93e7b-0b12-4b64-8e50-f23192baee7d}]. Client id: [5dcb]
[04.07.2016 14:38:41] <140691568428800> lpbcore|       IP endpoints: [127.0.0.1:2501].
[04.07.2016 14:38:41] <140691568428800>        |       Trying to connect to the endpoint [127.0.0.1:2501]
[04.07.2016 14:38:41] <140691568428800>        |   Connection status: system:0 ( Success ).
[04.07.2016 14:38:41] <140691568428800> net    |       Sending reconnect options: [disabled].
[04.07.2016 14:38:41] <140691568428800> lpbcore|     Starting server on proxy agent with UID [{8848c8d3-f76b-4414-8548-5e552ffdf0a1}].
[04.07.2016 14:38:41] <140691568428800>        |       Trying to connect to the endpoint [127.0.0.1:3500]
[04.07.2016 14:38:41] <140691568428800>        |   Connection status: system:0 ( Success ).
[04.07.2016 14:38:41] <140691531876096>        | Thread started. Thread id: 140691531876096, parent id: 140691568428800, role: Client receiver
[04.07.2016 14:38:41] <140691568428800> net    |       Sending reconnect options: [disabled].
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: >
[04.07.2016 14:38:41] <140691568428800> lpbcore|       Getting results.
[04.07.2016 14:38:41] <140691568428800> lpbcore|       Disconnecting.
[04.07.2016 14:38:41] <140691568428800> lpbcore|     Server on proxy agent with UID [{8848c8d3-f76b-4414-8548-5e552ffdf0a1}] has started.
[04.07.2016 14:38:41] <140691568428800> lpbcore|     [5dcb] >> : connectByIPs
[04.07.2016 14:38:41] <140691568428800> lpbcore|     [5dcb] >> : 127.0.0.1:2500
[04.07.2016 14:38:41] <140691568428800> lpbcore|     [5dcb] >> : .
[04.07.2016 14:38:41] <140691568428800> lpbcore|     [5dcb] >> : 0
[04.07.2016 14:38:41] <140691568428800> lpbcore|     [5dcb] >> : {f2d6fa55-5d5f-4667-9f28-24074e043c45}
[04.07.2016 14:38:41] <140691568428800> lpbcore|     [5dcb] >> : {952125e3-e3af-48aa-8d5c-9c68624f0c4e}
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: >
[04.07.2016 14:38:41] <140691568428800> lpbcore|     [5dcb] >> : Invoke
[04.07.2016 14:38:41] <140691568428800> lpbcore|     [5dcb] >> : <VCPCommand class="DataTransfer" method="SyncDisk" />
[04.07.2016 14:38:41] <140691568428800> lpbcore|     [5dcb] >> : <VCPCommandArgs><Item key="Option.Remote" type="EBoolean" value="false" /><Item key="Source.CtkSpec" type="EString" value="&lt;ctk_lpb /&gt;" /><Item key="Source.DiskPath" type="EString" value="emulated://&lt;EmulatedDiskSpec&gt;&lt;Layout&gt;&lt;Mbr DiskId=~=979741~= DiskLength=~=250059350016~=&gt;&lt;Bootloader Device=~=/dev/sda~= Offset=~=0~= Length=~=1048576~= /&gt;&lt;Partition Bootable=~=false~= Type=~=131~= Offset=~=1048576~= Length=~=245905752064~=&gt;&lt;UnderlyingDevice&gt;&lt;VeeamSnap DevMajor=~=8~= DevMinor=~=1~= /&gt;&lt;/UnderlyingDevice&gt;&lt;/Partition&gt;&lt;Partition Bootable=~=false~= Type=~=5~= Offset=~=245907848192~= Length=~=4151313408~= /&gt;&lt;Partition Bootable=~=false~= Type=~=0~= Offset=~=0~= Length=~=0~= /&gt;&lt;Partition Bootable=~=false~= Type=~=0~= Offset=~=0~= Length=~=0~= /&gt;&lt;Partition Bootable=~=false~= Type=~=130~= Offset=~=245907849216~= Length=~=4151312384~=&gt;&lt;UnderlyingDevice&gt;&lt;SwapDeviceFile Path=~=/dev/sda5~= /&gt;&lt;/UnderlyingDevice&gt;&lt;/Partition&gt;&lt;Partition Bootable=~=false~= Type=~=0~= Offset=~=0~= Length=~=0~= /&gt;&lt;Partition Bootable=~=false~= Type=~=0~= Offset=~=0~= Length=~=0~= /&gt;&lt;Partition Bootable=~=false~= Type=~=0~= Offset=~=0~= Length=~=0~= /&gt;&lt;/Mbr&gt;&lt;/Layout&gt;&lt;/EmulatedDiskSpec&gt;" /><Item key="Source.Type" type="EString" value="{disk}" /><Item key="Target.BackupType" type="EString" value="{full}" /><Item key="Target.CurrentLink" type="EString" value="veeamfs:5:/7230af24-fc7d-4c4b-8c8b-298bccc283a0 ({80a62c27-d21d-b211-8000-28924a305d6d})/000ef31d@/tmp/veeam/artuOCbackup$/OCbackup/OCbackup_2016-07-04T143839.vbk" /><Item key="Target.DedupEnabled" type="EBoolean" value="true" /><Item key="Target.PeriodicFlush.Enabled" type="EBoolean" value="false" /><Item key="Target.Type" type="EString" value="{backup}" /></VCPCommandArgs>
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --asyncNtf:disk_capacity: '250059350016'
[04.07.2016 14:38:41] <140691540268800> lpbcore|     [9d35] out: --asyncNtf:disk_capacity: '250059350016'
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --size: 250059350016
[04.07.2016 14:38:41] <140691531876096> lpbcore| Session progress: 0%; processed size: 0 processing speed: 0
[04.07.2016 14:38:41] <140691531876096> lpbcore| Accurate disk size: 250059350016
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out:
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --pex:0;524288;524288;0;524288;53376;92;100;92;0;0;0;131121095215022200
[04.07.2016 14:38:41] <140691531876096> lpbcore| Session progress: 0.000104833%; processed size: 524288 processing speed: 746849
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: <VCPCommandResult result="false" exception="Snapshot overflow.&#x0A;--tr:Failed to read the next block from the disk. Disk: [Disk Emulator]. Current offset: [1,048,576]. Disk size: [250,059,350,016]. CBT tracker: [bitmap_tracker://].&#x0A;--tr:Next asynchronous read request cannot be processed.&#x0A;--tr:Asynchronous data reader has failed.&#x0A;--tr:Failed to process conveyored task.&#x0A;Failed to upload disk.&#x0A;--tr:Disk upload failed.&#x0A;Agent failed to process method {DataTransfer.SyncDisk}.&#x0A;Exception from server: Snapshot overflow.&#x0A;--tr:Failed to read the next block from the disk. Disk: [Disk Emulator]. Current offset: [1,048,576]. Disk size: [250,059,350,016]. CBT tracker: [bitmap_tracker://].&#x0A;--tr:Next asynchronous read request cannot be processed.&#x0A;--tr:Asynchronous data reader has failed.&#x0A;Unable to retrieve next block transmission command. Number of already processed blocks: [2].&#x0A;--tr:Next asynchronous read request cannot be processed.&#x0A;--tr:Asynchronous data reader has failed.&#x0A;--tr:Failed to process conveyored task.&#x0A;Failed to download disk.&#x0A;--tr:Disk download failed.&#x0A;--tr:Unable to run ProtoEx server session.&#x0A;--tr:Failed to handle ProtoEx session.&#x0A;--tr:event:3:&#x0A;" />
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: >
[04.07.2016 14:38:41] <140691568428800> lpbcore|     [5dcb] >> : disconnect
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --err:
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: Snapshot overflow.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Failed to read the next block from the disk. Disk: [Disk Emulator]. Current offset: [1,048,576]. Disk size: [250,059,350,016]. CBT tracker: [bitmap_tracker://].
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Next asynchronous read request cannot be processed.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Asynchronous data reader has failed.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: Unable to retrieve next block transmission command. Number of already processed blocks: [2].
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Next asynchronous read request cannot be processed.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Asynchronous data reader has failed.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Failed to process conveyored task.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: Failed to download disk.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Disk download failed.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Unable to run ProtoEx server session.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Failed to handle ProtoEx session.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: Exception from server: Snapshot overflow.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Failed to read the next block from the disk. Disk: [Disk Emulator]. Current offset: [1,048,576]. Disk size: [250,059,350,016]. CBT tracker: [bitmap_tracker://].
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Next asynchronous read request cannot be processed.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Asynchronous data reader has failed.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: Unable to retrieve next block transmission command. Number of already processed blocks: [2].
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Next asynchronous read request cannot be processed.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Asynchronous data reader has failed.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Failed to process conveyored task.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: Failed to download disk.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Disk download failed.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Unable to run ProtoEx server session.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:Failed to handle ProtoEx session.
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: --tr:event:3:
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out:
[04.07.2016 14:38:41] <140691531876096> lpbcore|     [5dcb] out: :err--
[04.07.2016 14:38:41] <140691531876096> lpbcore| ERR |Client protocol receiver thread has failed.
[04.07.2016 14:38:41] <140691531876096> lpbcore| >>  |read: End of file
[04.07.2016 14:38:41] <140691531876096> lpbcore| >>  |--tr:Cannot read data from the socket. Requested data size: [1].
[04.07.2016 14:38:41] <140691531876096> lpbcore| >>  |--tr:Failed to read data from throttled device.
[04.07.2016 14:38:41] <140691531876096> lpbcore| >>  |--tr:Failed to read null-terminated string from stream.
[04.07.2016 14:38:41] <140691531876096> lpbcore| >>  |An exception was thrown from thread [1288161024].
[04.07.2016 14:38:41] <140691531876096>        | Thread finished. Role: 'Client receiver'.
[04.07.2016 14:38:41] <140691568428800> lpbcore| ERR |Failed to disconnect from proxy server.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |Snapshot overflow.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Failed to read the next block from the disk. Disk: [Disk Emulator]. Current offset: [1,048,576]. Disk size: [250,059,350,016]. CBT tracker: [bitmap_tracker://].
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Next asynchronous read request cannot be processed.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Asynchronous data reader has failed.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |Unable to retrieve next block transmission command. Number of already processed blocks: [2].
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Next asynchronous read request cannot be processed.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Asynchronous data reader has failed.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Failed to process conveyored task.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |Failed to download disk.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Disk download failed.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Unable to run ProtoEx server session.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Failed to handle ProtoEx session.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |Exception from server: Snapshot overflow.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Failed to read the next block from the disk. Disk: [Disk Emulator]. Current offset: [1,048,576]. Disk size: [250,059,350,016]. CBT tracker: [bitmap_tracker://].
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Next asynchronous read request cannot be processed.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Asynchronous data reader has failed.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |Unable to retrieve next block transmission command. Number of already processed blocks: [2].
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Next asynchronous read request cannot be processed.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Asynchronous data reader has failed.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Failed to process conveyored task.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |Failed to download disk.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Disk download failed.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Unable to run ProtoEx server session.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Failed to handle ProtoEx session.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:event:3:
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Backup client has failed to execute command.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |--tr:Failed to disconnect from proxy server.
[04.07.2016 14:38:41] <140691568428800> lpbcore| >>  |An exception was thrown from thread [1324713728].
[04.07.2016 14:38:41] <140691568428800> lpbcore|     [5dcb] >> : quit
[04.07.2016 14:38:41] <140691568428800> lpbcore|   Backing up disk object: [/dev/sda]. Failed.
[04.07.2016 14:38:41] <140691568428800> lpbcore|     [9d35] >> : disconnect
[04.07.2016 14:38:41] <140691540268800> lpbcore|     [9d35] out: >
[04.07.2016 14:38:41] <140691568428800> lpbcore|     [9d35] >> : quit
[04.07.2016 14:38:41] <140691540268800>        | Thread finished. Role: 'Client receiver'.
[04.07.2016 14:38:41] <140691568428800> lpbcore|   Stopping proxy agent process. Agent UID: [{eee93e7b-0b12-4b64-8e50-f23192baee7d}].
[04.07.2016 14:38:41] <140691568428800>        |     Trying to connect to the endpoint [127.0.0.1:3500]
[04.07.2016 14:38:41] <140691568428800>        |   Connection status: system:0 ( Success ).
[04.07.2016 14:38:41] <140691568428800> net    |     Sending reconnect options: [disabled].
[04.07.2016 14:38:41] <140691568428800> lpbcore|     Waiting for acknowledge.
[04.07.2016 14:38:43] <140691568428800> lpbcore|   Stopping proxy agent process. Agent UID: [{eee93e7b-0b12-4b64-8e50-f23192baee7d}]. ok.
[04.07.2016 14:38:43] <140691568428800> lpbcore|     [e7fb] >> : quit
[04.07.2016 14:38:43] <140691548661504>        | Thread finished. Role: 'Client receiver'.
[04.07.2016 14:38:43] <140691568428800> lpbcore|     [bbe4] >> : quit
[04.07.2016 14:38:43] <140691557054208>        | Thread finished. Role: 'Client receiver'.
[04.07.2016 14:38:43] <140691568428800> lpbcore|   Stopping proxy agent process. Agent UID: [{8848c8d3-f76b-4414-8548-5e552ffdf0a1}].
[04.07.2016 14:38:43] <140691568428800>        |     Trying to connect to the endpoint [127.0.0.1:3500]
[04.07.2016 14:38:43] <140691568428800>        |   Connection status: system:0 ( Success ).
[04.07.2016 14:38:43] <140691568428800> net    |     Sending reconnect options: [disabled].
[04.07.2016 14:38:43] <140691568428800> lpbcore|     Waiting for acknowledge.
[04.07.2016 14:38:44] <140691568428800> lpbcore|   Stopping proxy agent process. Agent UID: [{8848c8d3-f76b-4414-8548-5e552ffdf0a1}]. ok.
[04.07.2016 14:38:44] <140691568428800> lpbcore|   BackupJobPerformer: Releasing snapshot.
[04.07.2016 14:38:55] <140691568428800> lpbcore|   BackupJobPerformer: Releasing snapshot. ok.
[04.07.2016 14:38:55] <140691568428800> lpbcore| BackupJobPerformer: Creating backup. Failed.
[04.07.2016 14:38:55] <140691568428800>        | Trying to connect to the endpoint [127.0.0.1:3500]
[04.07.2016 14:38:55] <140691568428800>        |   Connection status: system:0 ( Success ).
[04.07.2016 14:38:55] <140691568428800> net    | Sending reconnect options: [disabled].
[04.07.2016 14:38:55] <140691568428800> lpbcore| Disconnecting.
[04.07.2016 14:38:55] <140691610052480> lpbcore| LpbManSession: Processing commands. ok.
[04.07.2016 14:38:55] <140691568428800> lpbcore| ERR |Job has failed.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |Snapshot overflow.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:Failed to read the next block from the disk. Disk: [Disk Emulator]. Current offset: [1,048,576]. Disk size: [250,059,350,016]. CBT tracker: [bitmap_tracker://].
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:Next asynchronous read request cannot be processed.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:Asynchronous data reader has failed.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:Failed to process conveyored task.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |Failed to upload disk.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:Disk upload failed.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |Agent failed to process method {DataTransfer.SyncDisk}.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |Exception from server: Snapshot overflow.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:Failed to read the next block from the disk. Disk: [Disk Emulator]. Current offset: [1,048,576]. Disk size: [250,059,350,016]. CBT tracker: [bitmap_tracker://].
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:Next asynchronous read request cannot be processed.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:Asynchronous data reader has failed.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |Unable to retrieve next block transmission command. Number of already processed blocks: [2].
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:Next asynchronous read request cannot be processed.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:Asynchronous data reader has failed.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:Failed to process conveyored task.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |Failed to download disk.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:Disk download failed.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:Unable to run ProtoEx server session.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:Failed to handle ProtoEx session.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:event:3:
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:Backup client has failed to execute command.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:Failed to transfer disk.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |--tr:Failed to backup disk object. Disk: [/dev/sda].
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |Backup job has failed.
[04.07.2016 14:38:55] <140691568428800> lpbcore| >>  |An exception was thrown from thread [1324713728].
[04.07.2016 14:38:55] <140691568428800>        | Thread finished. Role: 'Volume backup job execution'.
[04.07.2016 14:38:55] <140691610052480> lpbcore| Closing DB accessor [0x1d5efc0].
[04.07.2016 14:38:55] <140691610052480> lpbcore| Closing DB accessor [0x1d61a50].
[04.07.2016 14:38:55] <140691610052480> lpbcore| Closing DB accessor [0x1d5f350].
[04.07.2016 14:38:55] <140691610052480> lpbcore| [DEV] Destroyed [0x1d5bfd0]
[04.07.2016 14:38:55] <140691610052480> lpbman | Application session has been finished.
pama
Enthusiast
 
Posts: 38
Liked: 1 time
Joined: Wed Apr 20, 2011 1:02 pm
Full Name: Andrea de Lutti

Re: How to investigate on backup errors

Veeam Logoby vmniels » Mon Jul 04, 2016 2:02 pm 1 person likes this post

It's best to contact support here in regards to this issue. Also please follow the forum rules and try to prevent pasting long snippets of logs as usually support is needed to resolve it.
VCP-DCV
Veeam Certified Engineer
http://foonet.be
vmniels
Veeam Software
 
Posts: 1440
Liked: 318 times
Joined: Mon Jul 15, 2013 11:09 am
Full Name: Niels Engelen

Re: How to investigate on backup errors

Veeam Logoby pama » Mon Jul 04, 2016 2:28 pm

Thank you, but support is not yet active for linux agent..
pama
Enthusiast
 
Posts: 38
Liked: 1 time
Joined: Wed Apr 20, 2011 1:02 pm
Full Name: Andrea de Lutti

Re: How to investigate on backup errors

Veeam Logoby PTide » Mon Jul 04, 2016 2:51 pm

Please describe the way you've configured the backup - objects to backup and backup location.

Thanks
PTide
Veeam Software
 
Posts: 2884
Liked: 236 times
Joined: Tue May 19, 2015 1:46 pm

Re: How to investigate on backup errors

Veeam Logoby Gostev » Mon Jul 04, 2016 2:59 pm 1 person likes this post

@Niels beta users have been told to post all issues on this forum.
Gostev
Veeam Software
 
Posts: 21239
Liked: 2316 times
Joined: Sun Jan 01, 2006 1:01 am
Full Name: Anton Gostev

Re: How to investigate on backup errors

Veeam Logoby pama » Mon Jul 04, 2016 7:50 pm

Thanks a lot support,
I have installed on my Ubuntu installation.
I have set to backup the entire pc on a CIFS folder (Windows 2008 R2)
This is my last test:

2016-07-04 21:41:36 Job started at 2016-07-04 21:41:36
2016-07-04 21:41:36 Starting backup
2016-07-04 21:41:37 Creating volume snapshot 00:02:30
2016-07-04 21:44:08 Backing up BIOS bootloader on /dev/sda 00:00:01
2016-07-04 21:44:09 Backing up BIOS bootloader on /dev/sdb 00:00:00
2016-07-04 21:44:09 [error] Backing up /dev/sdb 00:00:00
2016-07-04 21:44:18 [error] Snapshot overflow.
2016-07-04 21:44:18 [error] Failed to perform backup


I have a file called "veeamsnapshotdata.0" in the root folder which is protected from deletion, now it is about 3,4MB.
Soemtimes failing backup means freezing the server....
pama
Enthusiast
 
Posts: 38
Liked: 1 time
Joined: Wed Apr 20, 2011 1:02 pm
Full Name: Andrea de Lutti

Re: How to investigate on backup errors

Veeam Logoby vmniels » Mon Jul 04, 2016 7:52 pm 1 person likes this post

Could you explain us the configuration in terms of which settings you use like volume backup/entire computer?
VCP-DCV
Veeam Certified Engineer
http://foonet.be
vmniels
Veeam Software
 
Posts: 1440
Liked: 318 times
Joined: Mon Jul 15, 2013 11:09 am
Full Name: Niels Engelen

Re: How to investigate on backup errors

Veeam Logoby pama » Tue Jul 05, 2016 6:22 am

vmniels wrote:Could you explain us the configuration in terms of which settings you use like volume backup/entire computer?

It is a simple job:

Code: Select all
  Backup mode    Job name:
     Destination    BackupJob

 Backup mode 
          Destination   (X) Entire machine (recommended)

 Name         
          Backup mode   ( ) Local
        > Destination     (X) Shared Folder
          Location          ( ) VBR (not in beta)

   Name                        ( ) NFS
          Backup mode x  (X) CIFS
          Destination 
        > Location      Server/Directory: server/shared/veeam
          Schedule     
          Summary      Domain:           domain.local
                       
                         Username:         veeam
                       
                         Password:         ******
                       
                         Restore points:   6

  Backup mode  [X] Run the job automatically
          Destination 
          Location          Daily at: 6:0
        > Schedule     
          Summary          [X] Sunday
                                 [X] Monday
                                 [X] Tuesday
                                 [X] Wednesday
                                 [X] Thursday
                                 [X] Friday
                                 [X] Saturday



The test on the shared folder access is ok. Username and password is verified.
Today the scheduled backup has freeze my machine.
pama
Enthusiast
 
Posts: 38
Liked: 1 time
Joined: Wed Apr 20, 2011 1:02 pm
Full Name: Andrea de Lutti

Re: How to investigate on backup errors

Veeam Logoby PTide » Tue Jul 05, 2016 10:08 am

May I ask you to archive and upload /var/log/veeam directory to a fileshare so we can review the logs? Also what kind of activity was the server performing during backup job? Any I/O intensive applications?

Thanks
PTide
Veeam Software
 
Posts: 2884
Liked: 236 times
Joined: Tue May 19, 2015 1:46 pm

Re: How to investigate on backup errors

Veeam Logoby pama » Tue Jul 05, 2016 10:19 am

PTide wrote:May I ask you to archive and upload /var/log/veeam directory to a fileshare so we can review the logs? Also what kind of activity was the server performing during backup job? Any I/O intensive applications?

Thanks


Thanks a lot, here there are my logs
The serever is an Owncloud server used only by me, so not too much work on database and/or filesystem.
pama
Enthusiast
 
Posts: 38
Liked: 1 time
Joined: Wed Apr 20, 2011 1:02 pm
Full Name: Andrea de Lutti

Re: How to investigate on backup errors

Veeam Logoby PTide » Tue Jul 05, 2016 11:19 am 1 person likes this post

Please run dmesg -T and share the output.

Thanks
PTide
Veeam Software
 
Posts: 2884
Liked: 236 times
Joined: Tue May 19, 2015 1:46 pm

Re: How to investigate on backup errors

Veeam Logoby pama » Tue Jul 05, 2016 12:13 pm

here it is.
Thank you! :D
pama
Enthusiast
 
Posts: 38
Liked: 1 time
Joined: Wed Apr 20, 2011 1:02 pm
Full Name: Andrea de Lutti

Re: How to investigate on backup errors

Veeam Logoby pama » Wed Jul 06, 2016 7:50 am

Replied by PM.
pama
Enthusiast
 
Posts: 38
Liked: 1 time
Joined: Wed Apr 20, 2011 1:02 pm
Full Name: Andrea de Lutti

Re: How to investigate on backup errors

Veeam Logoby pama » Thu Jul 07, 2016 6:35 am

How mates, how is going?
Thank you :)
pama
Enthusiast
 
Posts: 38
Liked: 1 time
Joined: Wed Apr 20, 2011 1:02 pm
Full Name: Andrea de Lutti

Next

Return to Veeam Agent for Linux



Who is online

Users browsing this forum: No registered users and 2 guests