Backup plan failing with "The disk is full" error (it's not)
Hello,
I have a situation here I don't know how to fix. There's a "special" backup plan for one of our PCs - special in a way, that it regularly backs up only a specific folder (with data that changes every hour), nothing else.
This backup plan was working well for quite a few months, but recently stopped working.
Error message:
| error 0x40019: Unknown error occurred while backing up.
| line: 0xba19e88dc5fea1af
| file: e:\235\processor\backup\backup_file.cpp:1110
| function: DaProcessor::Backup::_DoFileOperation
| $module: disk_bundle_vsa64_10330
|
| error 0x40019: Error occurred while backing up.
| line: 0x5f25c37074a5445e
| file: e:\235\processor\backup\archive3_file_backup.cpp:781
| function: `anonymous-namespace'::Archive3FileBackupBuilder::Write
| Archive3Code: 0x138e
| Name: arl:/C3175356-0474-4A1A-B958-C76EF93A4CCE/66D0AAB6-5D5E-418E-AA22-A29563C0E099/F59E86C9-4EBE-4C2F-AA77-BC253146DBBD
| $module: archive3_adapter_vsa64_10330
|
| error 0x40004: The disk is full.
| line: 0xc8d8731ce106f9c7
| file: e:\216\archive\ver3\adapter\error.cpp:57
| function: `anonymous-namespace'::ConvertArchive3Error
| $module: archive3_adapter_vsa64_10330
2020-06-29T10:02:18:330-03:00 304 E01350016: Error 0x1350016: TOL: Failed to execute the command. Backup workflow
| trace level: error
| channel: tol-activity#A5BC90D7-C2F1-424F-9633-3DFB5611C465
| line: 0x8d165e86fb81959b
| file: e:\235\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: F30407D6-601F-11E0-9C67-FF46DFD72085
| $module: mms_vsa64_10330
|
| error 0x1350016: TOL: Failed to execute the command. Backup workflow
| line: 0x8d165e86fb81959b
| file: e:\235\enterprise\common\tol\command\command.cpp:461
| function: Tol::`anonymous-namespace'::MakeFailResult
| CommandID: F30407D6-601F-11E0-9C67-FF46DFD72085
| $module: gtob_backup_command_addon_vsa64_10330
I don't understand why it's happening, because "The disk is full" would point to insufficient disk space, but that can't be the case here, because on the source PC there's around 400GB of free space and on the target server (Windows server 2016 based storage node) there's almost 700GB of free space and individual backups of this folder are only ~100MB.
Other backup plans (Full backups of entire machines) are working fine and storing backups on the very same server without any issues.
Does anyone have an idea what might be the problem here?
Thank you
Lukas
Hello Lukas,
thank you for posting on Acronis forums.
The Disk is full error is a standard Windows error that you receive when writing to a disk that does not have enough free space.
Please check a Backup location which is a target for this specific backup. There could be different Backup locations for weekly full PC backup and this folder backup.
Hello Maria,
thank you for your answer, but that can't be the case - there's more than enough free space in the backup location (over 600GB of free space vs 100MB folder that should be backed up by the backup job).
I'm starting to think that the archive is either somehow broken (even though validation finds nothing and I'm able to browse backups contents with no issues) or it reached some kind of limit, but don't know which. There's only 69 backups in this archive, which can't be a limit, right? And to be sure, I deleted one of the older backups, but that hasn't changed anything.
I created identical backup plan (used the clone function, actually) with slightly different name and that one works fine.
So I disabled the previous one and hopefully it won't happen again with the new one.
Two literally identical backup plans (same source, same folder, same backup location..), but one is failing with "Disk is full" error and second one is working just fine, weird.
Lukas
Hello Lukas.
Thank you for describing the issue in details.
Glad that you found a simple workaround.
If you wish to investigate what caused this error, I recommend that you open a case with Acronis Support Team. You will need to collect ProcMon logs after reproducing an issue and Acronis System Information from the Agent which backup fails with the error.