Skip to main content

Existing Backups Missing - Database corrupt

Thread needs solution

Win 10 popped up a message indicating it was about to carry out a major feature update.

After having disastrous experiences with these updates in the past, I decided it would be prudent to do a full backup of my C: drive.

I ran ATI 2017. My existing backups did not appear in the menu. I was unable to add them back in manually.

Eventually after hunting around for a solution, I renamed the database folder to force ATI to re-create it.

My backups then re-appeared.

This appears to be a common, known bug. Has it beeen fixed?

I would like to know why this happens and how to prevent it happening in the future.

The last full backup I carried out some weeks ago appeared to succeed with no errors. Why should it suddenly go wrong in this way?

The log indicated some sort of sql error - I think it indicated a missing table.

The last thing I need is unreliable backup software.

0 Users found this helpful

Brian, the Acronis database can get damaged or corrupted for various reasons which are difficult to identify, especially as this could be caused by actions outside of the ATI application or result from such as a hardware issue etc.

As such there is no specific bug that can be fixed unless someone is able to reproduce a scenario that causes such damage to the database.  The database is using SQL as would be expected but this in itself shouldn't cause any problems.

Fortunately, as you have found, the database can be rebuilt fairly easily and this in turn resolves most of the issues that arise out of such database problems.

Database issues are pretty rare in these forums and in my own experience too - I cannot remember when or if I have ever had such a problem myself over many years of using ATI.

I agree with Steve about such errors being rare. I have only had this happen once, and it was many years ago. Possibly with ATI 2015 (could have also been beta testing but just cannot remember). I have multiple machines running ATI over an extended period, thus reducing the rate at which this occurs.

That doesn't sound very reassuring.

It need to be confident that I will be able to restore my data after a software or hardware problem.

Backup software only needs to fail once to lose important data.

ATI Home 11 never had these problems. It didn't use a database or SQL. It was simple, had an easy to understand user interface, it worked and it was reliable.

I think I may have to go back to using Windows Backup.

 

From the log file it looks like there are several missing tables.

OnlineArchive_, ArchiveHead_, Slice_

 

2019-01-18T16:38:14.646 | 4 | 0x101 | 0x44d | 0x717645b92575f56a | Exception in litesql: 'SQLError: 1=status code : no such table: OnlineArchive_' | AU0EAQFq9XUluUV2cUV4Y2VwdGlvbiBpbiBsaXRlc3FsOiAnU1FMRXJyb3I6IDE9c3RhdHVzIGNvZGUgOiBubyBzdWNoIHRhYmxlOiBPbmxpbmVBcmNoaXZlXycAJG1vZHVsZQBBdGlfbWFuYWdlcnNfdnNfODA1OAAkZmlsZQBBazpcODA1OFxwcm9kdWN0c1xpbWFnZXJcYXJjaGl2ZWRiXGltcGxcZGF0YWJhc2Vfc3FsX2FyY2hpdmUuY3BwACRmdW5jAEFBcmNoaXZlRGI6OlNxbEFyY2hpdmVEYkltcGw6OkdldE9ubGluZUFyY2hpdmVzQnkAJGxpbmUATmUGAAAAAAAAAA==
2019-01-18T16:38:14.802 | 4 | 0x101 | 0x44d | 0x717645b92575f0e2 | Exception in litesql: 'SQLError: 1=status code : no such table: ArchiveHead_' | AU0EAQHi8HUluUV2cUV4Y2VwdGlvbiBpbiBsaXRlc3FsOiAnU1FMRXJyb3I6IDE9c3RhdHVzIGNvZGUgOiBubyBzdWNoIHRhYmxlOiBBcmNoaXZlSGVhZF8nACRtb2R1bGUAQXRpX21hbmFnZXJzX3ZzXzgwNTgAJGZpbGUAQWs6XDgwNThccHJvZHVjdHNcaW1hZ2VyXGFyY2hpdmVkYlxpbXBsXGRhdGFiYXNlX3NxbF9hcmNoaXZlLmNwcAAkZnVuYwBBQXJjaGl2ZURiOjpTcWxBcmNoaXZlRGJJbXBsOjpHZXRBcmNoaXZlcwAkbGluZQBO3QEAAAAAAAAA
2019-01-18T16:38:16.677 | 4 | 0x101 | 0x44d | 0x717645b92575f56a | Exception in litesql: 'SQLError: 1=status code : no such table: OnlineArchive_' | AU0EAQFq9XUluUV2cUV4Y2VwdGlvbiBpbiBsaXRlc3FsOiAnU1FMRXJyb3I6IDE9c3RhdHVzIGNvZGUgOiBubyBzdWNoIHRhYmxlOiBPbmxpbmVBcmNoaXZlXycAJG1vZHVsZQBBdGlfbWFuYWdlcnNfdnNfODA1OAAkZmlsZQBBazpcODA1OFxwcm9kdWN0c1xpbWFnZXJcYXJjaGl2ZWRiXGltcGxcZGF0YWJhc2Vfc3FsX2FyY2hpdmUuY3BwACRmdW5jAEFBcmNoaXZlRGI6OlNxbEFyY2hpdmVEYkltcGw6OkdldE9ubGluZUFyY2hpdmVzQnkAJGxpbmUATmUGAAAAAAAAAA==
2019-01-18T16:38:53.123 | 4 | 0x101 | 0x44d | 0x717645b92575f1a9 | Exception in litesql: 'SQLError: 1=status code : no such table: ArchiveHead_' | AU0EAQGp8XUluUV2cUV4Y2VwdGlvbiBpbiBsaXRlc3FsOiAnU1FMRXJyb3I6IDE9c3RhdHVzIGNvZGUgOiBubyBzdWNoIHRhYmxlOiBBcmNoaXZlSGVhZF8nACRtb2R1bGUAQXRpX21hbmFnZXJzX3ZzXzgwNTgAJGZpbGUAQWs6XDgwNThccHJvZHVjdHNcaW1hZ2VyXGFyY2hpdmVkYlxpbXBsXGRhdGFiYXNlX3NxbF9hcmNoaXZlLmNwcAAkZnVuYwBBQXJjaGl2ZURiOjpTcWxBcmNoaXZlRGJJbXBsOjpHZXRBcmNoaXZlc0J5VXJpACRsaW5lAE6kAgAAAAAAAAA=
2019-01-18T16:38:53.139 | 4 | 0x101 | 0x44d | 0x717645b92575f11a | Exception in litesql: 'SQLError: 1=status code : no such table: ArchiveHead_' | AU0EAQEa8XUluUV2cUV4Y2VwdGlvbiBpbiBsaXRlc3FsOiAnU1FMRXJyb3I6IDE9c3RhdHVzIGNvZGUgOiBubyBzdWNoIHRhYmxlOiBBcmNoaXZlSGVhZF8nACRtb2R1bGUAQXRpX21hbmFnZXJzX3ZzXzgwNTgAJGZpbGUAQWs6XDgwNThccHJvZHVjdHNcaW1hZ2VyXGFyY2hpdmVkYlxpbXBsXGRhdGFiYXNlX3NxbF9hcmNoaXZlLmNwcAAkZnVuYwBBQXJjaGl2ZURiOjpTcWxBcmNoaXZlRGJJbXBsOjpHZXRBcmNoaXZlc0J5SWQAJGxpbmUAThUCAAAAAAAAAA==
2019-01-18T16:38:53.154 | 4 | 0x101 | 0x44d | 0x717645b92575f175 | Exception in litesql: 'SQLError: 1=status code : no such table: Slice_' | AU0EAQF18XUluUV2cUV4Y2VwdGlvbiBpbiBsaXRlc3FsOiAnU1FMRXJyb3I6IDE9c3RhdHVzIGNvZGUgOiBubyBzdWNoIHRhYmxlOiBTbGljZV8nACRtb2R1bGUAQXRpX21hbmFnZXJzX3ZzXzgwNTgAJGZpbGUAQWs6XDgwNThccHJvZHVjdHNcaW1hZ2VyXGFyY2hpdmVkYlxpbXBsXGRhdGFiYXNlX3NxbF9hcmNoaXZlLmNwcAAkZnVuYwBBQXJjaGl2ZURiOjpTcWxBcmNoaXZlRGJJbXBsOjpHZXRTbGljZXNCeVVyaQAkbGluZQBOcAIAAAAAAAAA
2019-01-18T16:38:53.154 | 4 | 0x101 | 0x44d | 0x717645b92575f43d | Exception in litesql: 'SQLError: 1=status code : no such table: ArchiveHead_' | AU0EAQE99HUluUV2cUV4Y2VwdGlvbiBpbiBsaXRlc3FsOiAnU1FMRXJyb3I6IDE9c3RhdHVzIGNvZGUgOiBubyBzdWNoIHRhYmxlOiBBcmNoaXZlSGVhZF8nACRtb2R1bGUAQXRpX21hbmFnZXJzX3ZzXzgwNTgAJGZpbGUAQWs6XDgwNThccHJvZHVjdHNcaW1hZ2VyXGFyY2hpdmVkYlxpbXBsXGRhdGFiYXNlX3NxbF9hcmNoaXZlLmNwcAAkZnVuYwBBQXJjaGl2ZURiOjpTcWxBcmNoaXZlRGJJbXBsOjpJbnNlcnRWb2x1bWVzACRsaW5lAE44BQAAAAAAAAA=
2019-01-18T16:38:53.154 | 4 | 0x101 | 0x44d | 0x717645b92575f11a | Exception in litesql: 'SQLError: 1=status code : no such table: ArchiveHead_' | AU0EAQEa8XUluUV2cUV4Y2VwdGlvbiBpbiBsaXRlc3FsOiAnU1FMRXJyb3I6IDE9c3RhdHVzIGNvZGUgOiBubyBzdWNoIHRhYmxlOiBBcmNoaXZlSGVhZF8nACRtb2R1bGUAQXRpX21hbmFnZXJzX3ZzXzgwNTgAJGZpbGUAQWs6XDgwNThccHJvZHVjdHNcaW1hZ2VyXGFyY2hpdmVkYlxpbXBsXGRhdGFiYXNlX3NxbF9hcmNoaXZlLmNwcAAkZnVuYwBBQXJjaGl2ZURiOjpTcWxBcmNoaXZlRGJJbXBsOjpHZXRBcmNoaXZlc0J5SWQAJGxpbmUAThUCAAAAAAAAAA==
2019-01-18T16:38:53.154 | 4 | 0x101 | 0x44d | 0x717645b92575f1a9 | Exception in litesql: 'SQLError: 1=status code : no such table: ArchiveHead_' | AU0EAQGp8XUluUV2cUV4Y2VwdGlvbiBpbiBsaXRlc3FsOiAnU1FMRXJyb3I6IDE9c3RhdHVzIGNvZGUgOiBubyBzdWNoIHRhYmxlOiBBcmNoaXZlSGVhZF8nACRtb2R1bGUAQXRpX21hbmFnZXJzX3ZzXzgwNTgAJGZpbGUAQWs6XDgwNThccHJvZHVjdHNcaW1hZ2VyXGFyY2hpdmVkYlxpbXBsXGRhdGFiYXNlX3NxbF9hcmNoaXZlLmNwcAAkZnVuYwBBQXJjaGl2ZURiOjpTcWxBcmNoaXZlRGJJbXBsOjpHZXRBcmNoaXZlc0J5VXJpACRsaW5lAE6kAgAAAAAAAAA=

 

I would have thought it should be possible to analyse the failed Database files to discover exactly what went wrong.

 

Brian, I would strongly recommend using the bootable Acronis Rescue Media when doing any restore / recovery that involves your Windows OS - that media is a lot more similar to your old ATI 11.0 application and does not need or use the database information.

The rescue media would always be needed in a bare-metal recovery scenario, i.e. a total disk failure and recovery to a new raw replacement drive.

Perhaps the Acronis developers could interpret the error messages in your log but your ATI 2017 product is long out of support, so regardless of what was found, no fix would be produced for it unless the same issue could be proven to exist on the current ATI 2019 product version.