<story><title>Arq 5.8.5 for Mac Fixes a Bad Bug</title><url>https://www.arqbackup.com/blog/arq-5-8-5-for-mac-fixes-a-bad-bug/</url></story><parent_chain></parent_chain><comment><author>k1t</author><text>While I agree with others that honesty is best, even if it hurts in the short term - there was a corresponding (perhaps even far worse) bug in the Windows version recently with no corresponding blog post or announcement.&lt;p&gt;I think it was the 5.7.8 (Windows) release that introduced a bug that caused Arq to believe a budget of 0 should be enforced. This meant if you backed up to AWS (probably others too) it would delete ALL backup records except the most recent one (and then immediately cleanup the now unreferenced objects, so even the reflog feature can&amp;#x27;t help you)&lt;p&gt;I had only been using Arq for a few months so I didn&amp;#x27;t lose anything major, but if I had been keeping years of historical records, I would be furious.&lt;p&gt;This was fixed in the next release 5.7.13 (&amp;quot;Fixed an issue that could cause Arq to enforce a budget when no budget was configured.&amp;quot;) but still - I thought a bigger deal should have been made of this.</text></comment>
<story><title>Arq 5.8.5 for Mac Fixes a Bad Bug</title><url>https://www.arqbackup.com/blog/arq-5-8-5-for-mac-fixes-a-bad-bug/</url></story><parent_chain></parent_chain><comment><author>heavymark</author><text>Adding to the sentiment of others, I&amp;#x27;ve been a long time Arq user and grateful for Stefan&amp;#x27;s openness and honesty.&lt;p&gt;I imagine most or all of us with that sentiment did not suffer any data loss or rather did not need to do a retrieval and discovered data loss during that time. So much easier for us to write it off as a non issue. Where is if it affected us I imagine we&amp;#x27;d all be quite a bit more upset.&lt;p&gt;Though most people use common alternatives such as Time Machine which every few months runs into data issues and far less transparency. Stefan could have quietly updated with a fix, and waited to see if anyone discovered the issue and then only announced the issue if that occurred. But instead he proactive announced it. So bravo. And I&amp;#x27;m sure he will instill new procedures to hopefully avoid that in the future, but of course with any software there is always room for error no matter how much testing you do.</text></comment>