![]() |
Register /
Login
|
Desktop view
|
Johannes wrote:Maybe I miss something very obvious, but somehow my verify actions don?t do what I want them to do.
For each of my archives I have created a verify action based on an interval that fits the archive's capture frequency. For example, my short time archive that captures certain folders every hour has its verify action set to every 7 days starting from Jun 16th 2012 1:00 (the date I defined it, I guess). Now the status window shows a yellow LED complaining that it had not been verified for 13 weeks. The archive file is available all the time. Why does the scheduled action not run?
What would be the best way to schedule a verify after each capture? (This would be useful for my off-site backups to make sure the are healthy before I bring them out of the house).
Any news when the command-line tool (or any other means to trigger an action by script) might come up? (That's really the only thing I miss at the moment)
So once you've captured something with the new version, you can no longer use the old version to access your archives.
Johannes wrote:Can both versions be used at the same time (not on the same archive of course)?
That would be crucial for testing.
Nobody would risk a longtime archive for a beta test.