| I think at that point we may not have cared… We did still run TSM incrementals, basically back-to-back, but those didn’t finish in 24 hours. We needed a better-effort way to get most message for a disaster. I looked for the patch a bit ago (not that it would apply, but I would at least see what I had changed!) but couldn’t find it. I haven’t been employed by that organization for just over 8 years now, so it’s nowhere in my cache. The general point of my comment was: If you’re backing up files, looking for them is expensive. If you can get Cyrus to tell you what it changed, then you don’t have to ask the filesystem — which usually involves asking every file. The other option would be to use a filesystem that supports DMAPI, and write a DMAPI application that kept track of changed files and added them to a backup queue. It seems like having Cyrus log the delivery would have other benefits, though, and would work on any filesystem. I’m not currently a Cyrus admin, though, so it could already do that for all I know. :) Liberty, -- Stephen On Sep 7, 2014, at 10:03 PM, Bron Gondwana <brong@xxxxxxxxxxx> wrote:
|
---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
