Backup Error
Following the (last) error:
2019-05-22T16:54:46:079+02:00 139925350917888 I0135003B: Command has completed successfully. Command=Deleting snapshot; tenantID=00000000-0000-0000-0000-000000000000
2019-05-22T16:54:47:151+00:00 139761539815168 E0135003D: Error 0x135003d: Command has failed. Command=Backup plan 'DC TEST'; tenantID=00000000-0000-0000-0000-000000000000
| trace level: error
| channel: tol-activity#70ACC94E-4EA9-4354-B5E2-B5A848096323
| line: 0x4a8728dc8a1c9584
| file: e:/412/enterprise/common/tol/gating_activity.cpp:222
| function: OnCompleted
| $module: mms_lxa64_13400
|
| error 0x1350016: TOL: Failed to execute the command. Backup plan 'DC TEST'
| line: 0x8d165e86fb819597
| file: e:/412/enterprise/common/tol/command/command.cpp:457
| function: MakeFailResult
| CommandID: D332948D-A7A9-4E07-B76C-253DCF6E17FB
| $module: mms_lxa64_13400
|
| error 0x1350016: TOL: Failed to execute the command. Backup plan 'DC TEST'
| line: 0x8d165e86fb819597
| file: e:/412/enterprise/common/tol/command/command.cpp:457
| function: MakeFailResult
| CommandID: D332948D-A7A9-4E07-B76C-253DCF6E17FB
| $module: agent_protection_addon_lxa64_13400
|
| error 0x1330029: Failed to execute the command.
| line: 0xe6792a5ee190de2a
| file: e:/412/enterprise/managers/gtob/protection/agent_engine/protect_command.cpp:216
| function: SafeExecute
| $module: agent_protection_addon_lxa64_13400
|
| error 0x1350016: TOL: Failed to execute the command. Backup workflow
| line: 0x8d165e86fb819597
| file: e:/412/enterprise/common/tol/command/command.cpp:457
| function: MakeFailResult
| CommandID: F30407D6-601F-11E0-9C67-FF46DFD72085
| $module: mms_lxa64_13400
|
| error 0x1350016: TOL: Failed to execute the command. Backup workflow
| line: 0x8d165e86fb819597
| file: e:/412/enterprise/common/tol/command/command.cpp:457
| function: MakeFailResult
| CommandID: F30407D6-601F-11E0-9C67-FF46DFD72085
| $module: gtob_backup_command_addon_lxa64_13400
|
| error 0x1490002: Step 'Backup' has failed.
| line: 0x8edc81ea38fabad3
| file: e:/412/enterprise/managers/gtob/backupers/backup_command/impl/backup_workflow_command.cpp:711
| function: ProcessWorkflowSteps
| TraceLevel: 0x1
| StepType: 0x2
| $module: gtob_backup_command_addon_lxa64_13400
|
| error 0xa100cb: Failed to get information about the backups.
| line: 0xd5796a33131eecac
| file: e:/412/enterprise/mms/managers/archive/meta_info_cache/meta_info_cache.cpp:438
| function: GetSlicesInfo
| $module: disk_bundle_lxa64_13400
|
| error 0xa10006: Cannot find a backup with key 'smb://192.168.1.33/RDX/#arl:/00000000-0000-0000-0000-000000000000/00000000-0000-0000-0000-000000000000/00000000-0000-0000-0000-000000000000/2669036C-DF73-4A66-9FB9-A189562304A0?archive_name%3dDC-189D24BA-4CC9-4ADC-8A0D-0EA48709BBFD-52E9CBD4-953C-E4E9-EF72-05F3F570AB43A'.
| line: 0xd5796a33131eeca5
| file: e:/412/enterprise/mms/managers/archive/meta_info_cache/meta_info_cache.cpp:431
| function: GetSlicesInfo
| $module: disk_bundle_lxa64_13400
Hi Maria, thank's for reply.
I'm not so sure about the inaccessibility or corruption of smb://192.168.1.33//RDX.
In my backup job there are two vm configured for backup. If i look at file or vm restoration I can find latest backup for the vm1 but not for vm2. So the job was able to write and read vm1 backup in smb.
If I look at devices section on acronis appliance, I can see this error associated to AcronisAppliance-52C0F that is the device where is installed the agent.
In attached, latest log file
Hello Andrea.
This issue could arise if a file://192.168.1.33/RDX/DC-6FE1B80B-7F0B-44FB-9BA4-E58AFB71A374-52E9CBD4-953C-E4E9-EF72-05F3F570AB43A.tibx is of a large size.
In this case, you can either apply splitting or change a backup format to Version 11. You will need to create a new backup plan to apply these new backup options.
Otherwise, you can try moving this archive to another location. In this case, a new backup file will be created in the old location. However, the issue will re-occur after the size of this backup reaches the critical size.