Backup fails by message unknown status
Hello
The backup job fails and gives just the error message "Unknown status." That's really too less information to find out what's wrong and what needs to be fixed.
I've checked all obvious reasons like availability of selected volumes. All of them are available and accessible. And I could not find a more detailed log file. I expect better and valuable error reporting of such an expensive tool.
I've subsribed Acronis Cyber Protect Home Office and installed build 40338 on Windows 11.
Who can help me here to fix it?
Thanks, Andreas

- Log in to post comments

Andreas,
Download a copy of the MVP Assistant log viewer tool and use this to look at the logs to see if they show any issues during the operation process?
The latest version of the new log viewer tool is at the link below.
MVP Assistant - New 2.0 with Rescue Media Builder (New Version 2.7.3)
If you have Disks & Partitions backups created on ATI 2020 or later using .tibx files, then look in the Backup Worker logs.
If you have Files & Folders backups using .tib files (or Disk backups from earlier versions using .tib files) or using Cloning then look in the Demon logs.
Other logs are shown by the MVP Assistant under the 'Active Logs' heading of the Log Viewer page of the Assistant, i.e. Media Builder.
The Schedule2 log contains information related to scheduled task but is one of the more difficult logs to read / work through.
The log files should be zipped to preserve their original file names if sharing in the forums and would need to be less than 3MB in size, otherwise you would need to share the zip file via a Cloud share service such as OneDrive, Dropbox etc.
- Log in to post comments

Hello Andreas.
I have raised a ticket with our support so we can help you with the issue ( 06015883 ).
That error code is very generic. Please collect the system report of the machine and upload it in the FTP we are going to provide you in the email.
Feel free to update this thread after with the solution provided by our support.
Thanks in advance!
- Log in to post comments

Hi Steve
Thank you for your advise. I've found the log viewer and found each of them several times:
- 06.08.2023 01:14:05:687 PM +02:00 18704 E00070021: Error 0x70021: Failed to create volume snapshot.
- 06.08.2023 01:21:20:026 PM +02:00 16708 E000B042E: Error 0xb042e: Target not available
The external drive was never disconnected. So I've no idea why 2nd error was reported.
The errors appeared only for the job for the system backup (Drive C: and EFI System Volume). The jobs for the other 3 data volumes (D:, E: and F:) run fine. All backup files has the extension .tibx. Usually I run them manually after connecting the external drive.
Do you have an idea why it failed to create volume and why a cold reboot (Switch off and on) solved it?
Thanks, Andreas
- Log in to post comments

Andreas Manz wrote:Hi Steve
Thank you for your advise. I've found the log viewer and found each of them several times:
- 06.08.2023 01:14:05:687 PM +02:00 18704 E00070021: Error 0x70021: Failed to create volume snapshot.
- 06.08.2023 01:21:20:026 PM +02:00 16708 E000B042E: Error 0xb042e: Target not available
The external drive was never disconnected. So I've no idea why 2nd error was reported.
The errors appeared only for the job for the system backup (Drive C: and EFI System Volume). The jobs for the other 3 data volumes (D:, E: and F:) run fine. All backup files has the extension .tibx. Usually I run them manually after connecting the external drive.
Do you have an idea why it failed to create volume and why a cold reboot (Switch off and on) solved it?
Thanks, Andreas
Hello Andreas. The reboot restarts the snapshot tools in the OS and sometimes it solves some issues they may have.
- Log in to post comments

Hello
Today I've started the same backup jobs in the same environment under the same conditions using the same Acronis Cyber Protect Home Office build and it run just fine at the 1st try.
Maybe an update from Microsoft solved the misbehavior.
- Log in to post comments

AndreasM wrote:Hello
Today I've started the same backup jobs in the same environment under the same conditions using the same Acronis Cyber Protect Home Office build and it run just fine at the 1st try.
Maybe an update from Microsoft solved the misbehavior.
Hello Andreas.
Thanks for updating the thread and sharing what helped to solve the issue.
Cheers!
- Log in to post comments