Skip to main content

Compacting deduplicating location too slow

Thread needs solution

Hello.

I have two deduplicating locations and the previous week I deleted many old backup sets. Compacting job started on Sunday and still runs (60 hours +) and the progress is 2%. Is this process too slow or there is a problem? About a month ago, I deleted about 5 Gb old backup sets and the compacting job finished after 5 days. I should mention that during the compacting process in c:\programdata\acronis\backupandrecovery\asn\logs I can see that the size of the files 2017-09-27-12-52-54.log and asn-2017-09-27-12-52-54-2952.log  is continuously increasing and if I open it a can see the following text repeated almost  twice a second.

2017-10-10T13:42:14:207+02:00 1160 C0000001B: Assertion failed: ok, file k:\7641\enterprise\storage_server\datastore\data_store_impl.h, line 857^M
2017-10-10T13:42:14:345+02:00 1160 C0000001B: 0x000000013FBADDD6 StorageServer.exe+0x20DDD6
0x000000013FEEE425 TaskManager::v1::Message::Message+0x2229D5
0x000000013FEE4FF2 TaskManager::v1::Message::Message+0x2195A2
0x000000013FEC0F4B TaskManager::v1::Message::Message+0x1F54FB
0x000000013FF59D26 TaskManager::v1::Message::Message+0x28E2D6
0x000000013FF2F7C1 TaskManager::v1::Message::Message+0x263D71
0x000007FEDB3A9981 asn_commands.dll+0x59981
0x000007FEDB39CAC8 asn_commands.dll+0x4CAC8
0x000007FEDB3CE035 asn_commands.dll+0x7E035
0x000007FEDB3CACDE asn_commands.dll+0x7ACDE
0x000000014005D57E TaskManager::v1::Message::operator=+0xBCBFE
0x0000000140016B3E TaskManager::v1::Message::operator=+0x761BE
0x0000000140E779EB TaskManager::v1::Message::~Message+0xB3900B
0x0000000140E779EB TaskManager::v1::Message::~Message+0xB3900B
0x000000014005745C TaskManager::v1::Message::operator=+0xB6ADC
0x0000000140057264 TaskManager::v1::Message::operator=+0xB68E4
0x00000001405F1CFB TaskManager::v1::Message::~Message+0x2B331B
0x00000001405F1950 TaskManager::v1::Message::~Message+0x2B2F70
0x000007FEF6E21CED thread_pool.dll+0x1CED
0x000007FEF6E21D41 thread_pool.dll+0x1D41
0x000007FEF6E221BC thread_pool.dll+0x21BC
0x000007FEF6E23086 ThreadPoolWaitForThreadExit+0x886
0x000007FEF90E4F7F beginthreadex+0x107
0x000007FEF90E5126 endthreadex+0x192
0x0000000076DB59CD BaseThreadInitThunk+0xD
0x0000000076EEA561 RtlUserThreadStart+0x21^

 This text never stop being written unless the compacting job finishes.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Athanasios,

The "assertion failed" messages appearance is a known issue in the current Update 1 release of Acronis Backup 12.5 (internal bug id: ABR-138299) and they indeed impact performance of the compacting task. This problem is already fixed in the upcoming next update (Update 2) which is planned for the end of the year. Until then you should let the compacting run and ignore these messages.

Thank you.