There isn't one. Mirra was unique in its ability to incrementally backup multiple repositories, wherever those might reside, and to be able to allow access to the backup via the Mirra web site. However, as implemented, that flexibility also created some hidden problems for certain kinds of data. Backing up a multi-file accounting database requires that all the files are backed up as a snapshot of the moment, and the Mirra didn't work that way. So, to have a useable accounting backup required regularly saving the single file restore point snapshot from within the app. That was a hard learned lesson when a Peachtree Btrieve DB suddenly started throwing errors. All other picture, audio, video, excel, word, powerpoint, single document and generally stand-alone digital content was perfect stuff for the Mirra, up to 250,000 files, the limit the Mirra could handle (a limit probably set by Seagate when they looked at what the client did to performance on the main computer when it tried to work with more than 250K files as it looped throughout the day).
That limit on the number of files AND the invisible latency in the Mirra backup stream AND the desire to have the comfort of having true snapshots of multi-file databases had already forced me to implement 3 of the USB stand alone backup drives which were scheduled to fire at different times during the day. That solved the 250K file limit problem, and the DB snapshot problem, and the latency issue turned into working on another computer until the backup was done. Not perfect, but it worked, and the Mirra was relegated to keeping the current backup of the constantly changing folders on the primary system, and surrounding boxes that relied on that system as a file server.
What I've decided to do as a next step is to move to RAID, multiple disk continuous duplication, possibly as a NAS, though the cost of the latter has to come down significantly, first. For my purposes (not my clients, yet) I'll be implementing RAID on the remaining two SATA connections on my 8xSATA motherboard, leaving all the existing drives in place. Then, using an inexpensive, NOT-BACKUP, piece of software I've found, that will schedule, and will do incremental synchronizations, I'll use the 2xSATA RAID capability to capture synchronizations from the main box HDD stack, and all the LAN connections (primarily desktop and my docs).
The problems you describe with unexplained freezes, instantaneous unexplained reboots, and a general touchiness of the system as indicated by funny error messages that dont' stop the system, apps that fail on startup, then start on the second try, that's the stuff that was going on after the September MSoft Tuesday push of updates. The tech who worked remotely on the box used a MSoft process reporter/capture app to look at the process hierarchy after the critical app was started, and failed to open, remaining stalled in the TaskManager process list. He zero'd in immediately on "encryption" processes, and there was only one, the Mirra client. Uninstalling the Mirra client, rebooting, and the critical app started normally. Watching him work and asking questions on the phone, I gathered that the Protexis digital licensing software was also involved, and noted that while in the past I'd seen and was familiar with a single protexis process, there was now also a second, protexis2 -- yes, literally with a "2" added to the filename -- running, that I didn't recall ever seeing before. After the Mirra client was removed, I haven't had any of the problems described in the first sentence above. I can be found on the web at c2cpa dot com if you need more information about what is described here.
