#ARQ BACKUP DESTINATIONS DRIVER#

Shortly after I ordered a replacement Mac Mini (with a 1TB Fusion drive that feels nearly as fast as my SSD at home) and a bunch of new external drives. As I noted before, these are both solid pieces of software so I’m very much blaming the machine itself and the way it was set up. The Arq agent had hung and I believe SuperDuper had too, just frozen in the middle of a scheduled copy. Understand that there was no monitoring checking required logging in to the machine and looking at the Arq interface and SuperDuper’s schedule.

#ARQ BACKUP DESTINATIONS DRIVER#

(This had happened before I think it might have been connected to the third-party RAID driver we were using, but I don’t know that for sure.)Īs a precaution I checked the server’s backups. What finally prompted me to overhaul the backups was a nerve-wracking hour late last year when the Mac Mini server became unresponsive and would fail to start up with its external drives attached.ĭetaching the drives, booting and then reattaching the drives got us back to normal. So it didn’t happen for about 2.5 years after I got the job. That combined with an already set plan to make the change when the server hardware was changed, a reluctance to spend money that delayed the hardware change, and a near-total lack of time. But ultimately the common case was so rare that the pain it caused wasn’t sufficiently motivating. That alone should have made me act sooner than I did. The tools were solid but used in such a way that the common case (fast file restoration) was likely to fail, even if the rare case (complete disk failure) was covered. To recount from last time, our backup strategy was a mess.

Arq backup destinations