Hello,
Thank you sazz. From what I understand, after i manually deletethe change journal for a drive, launch full and then incremental backup for that drive, the change journal should be activated automatically and not manually by using fsutil in cmd.
However my NBU does not sense any change. I still get bpbkar (NOT using change journal data for <Z:\>: unable to locate journal data, after i have manually deleted the change journal and re run a full and incremental job
See below a fraction of the bpbkar log in verbosity 5:
tar_backup_tfi::setupFileDirectives: TAR - backup filename = Z:\
tar_base::keepaliveThread: INF - keepalive thread is active with an interval of 60 seconds
NBJournalDataCollection::NBJournalDataCollection: INF - volume guid:<\\?\Volume{6f91bef9-6101-11e2-818c-806e6f6e6963}\>
NBJournalDataCollection::NBJournalDataCollection: INF - mounted at:<C:\>:<\\?\Volume{6f91bef9-6101-11e2-818c-806e6f6e6963}\>
NBJournalDataCollection::NBJournalDataCollection: INF - adding to collection, volume:<\\?\Volume{6f91bef9-6101-11e2-818c-806e6f6e6963}\>:<C:\>
NBJournalData::NBJournalData: ERR - journal service is not running for volume:<\\?\Volume{6f91bef9-6101-11e2-818c-806e6f6e6963}>
P:S: it is a local drive. I get the same error for two of the drives , not for the rest of them, same type.
Thank you!