Comment 1 for bug 643973

I note that an obvious case where the test restore would throw an error would be where the file has changed in the seconds since the backup (say, if a log file is being backed up). In that case, a simple warning could be given saying that:
- the file restored correctly;
- the file matched its original hash (I believe that this is part of the restore function);
- the restored file differs from the local file; but
- that this was expected, as the "modified time" of the local file shows that the local file has changed since the backup.