"USN change journal cannot be used"
Posted: Wed Oct 10, 2018 3:56 am
This is a recurring problem I have with FBackup that ultimately makes me lose faith in the integrity of mirror-type backups made by this program. Here is what happens far too regularly:
(1) I create a mirror-type backup that works just fine for a while, spanning dozens of backups.
(2) Then one day, for completely inexplicable reasons (to me at least), I'll notice that my backup finishes with an error warning. In looking at the log I'll see the messages
"USN change journal cannot be used on path "C:". Reason: The journal was deleted\reseted
USN change journal not supported for any of the backup sources"
(3) In the backup destination I'll notice that recent files backed up properly, which are still present in the source drive, have been DELETED. Typically, what seems to happen is that new files created in a source folder appear in the backup, but other files in the backup (still present on the source drive!) are gone.
(4) I am then forced to redo the entire backup from scratch, wasting a lot of time in the process.
WHY does FBackup actually delete files in the destination that are present in the source drive? It's crazy. What is the reason for this? Can somebody provide any explanation for this? Is there a way to avoid it? I've seen others report this problem before. A backup program that deletes files as I've described simply cannot be trusted. Before I give up on FBackup altogether I'll await an explanation and, hopefully, a solution.
(1) I create a mirror-type backup that works just fine for a while, spanning dozens of backups.
(2) Then one day, for completely inexplicable reasons (to me at least), I'll notice that my backup finishes with an error warning. In looking at the log I'll see the messages
"USN change journal cannot be used on path "C:". Reason: The journal was deleted\reseted
USN change journal not supported for any of the backup sources"
(3) In the backup destination I'll notice that recent files backed up properly, which are still present in the source drive, have been DELETED. Typically, what seems to happen is that new files created in a source folder appear in the backup, but other files in the backup (still present on the source drive!) are gone.
(4) I am then forced to redo the entire backup from scratch, wasting a lot of time in the process.
WHY does FBackup actually delete files in the destination that are present in the source drive? It's crazy. What is the reason for this? Can somebody provide any explanation for this? Is there a way to avoid it? I've seen others report this problem before. A backup program that deletes files as I've described simply cannot be trusted. Before I give up on FBackup altogether I'll await an explanation and, hopefully, a solution.