Forum Discussion

rshehab's avatar
rshehab
Level 3
8 years ago

not using change journal data for DFSR

Hello everyone, 

i need your help resolving my issue with netbackup accelerator and dfs. the job completes successfully but i get a warning that journal was not used so i will not benefit from the accelerator. 

 

1/03/2017 12:11:28 - Info bpbkar32 (pid=21724) not using change journal data for <Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\TestFolder>: not supported for non-local volumes / file systems

 

I have netbackup 7.7.3. 

1 media/master server

1dfsr client.

 

thank you, 

8 Replies

    • rshehab's avatar
      rshehab
      Level 3

      Hello Nicolai,

      yes i followed the below guide. i created 2 schedules and one of them has "force rescan..." but still i get :

      01/03/2017 13:51:14 - Info bpbkar32 (pid=7100) Backup started
      01/03/2017 13:51:14 - Info bpbkar32 (pid=7100) change time comparison:<enabled>
      01/03/2017 13:51:14 - Info bpbkar32 (pid=7100) accelerator enabled backup, archive bit processing:<disabled>
      01/03/2017 13:51:14 - Info bptm (pid=1636) start
      01/03/2017 13:51:23 - Info bptm (pid=1636) using 262144 data buffer size
      01/03/2017 13:51:23 - Info bptm (pid=1636) setting receive network buffer to 1049600 bytes
      01/03/2017 13:51:23 - Info bptm (pid=1636) using 30 data buffers
      01/03/2017 13:51:27 - Info bptm (pid=1636) start backup
      01/03/2017 13:51:28 - Info bptm (pid=1636) backup child process is pid 2288.8844
      01/03/2017 13:51:28 - Info bptm (pid=2288) start
      01/03/2017 13:51:28 - begin writing
      01/03/2017 13:52:21 - Info bpbkar32 (pid=7100) not using change journal data for <Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\TestFolder>: not supported for non-local volumes / file systems

       

      thank you,

       

      • sdo's avatar
        sdo
        Moderator

        See Marianne's reply...  NetBackup Accelerator is not NTFS Change Journal, they are two different things.  They can work in concert together for even more optimal backups, but they do not have to.  In fact, we can thank Veritas for not tying the two "technologies" too closely together, i.e. they remain independent of each other but can work together but do not have to.

        Tip:  Do not be tempted to disable NTFS Change Journal on a system utilising DFS/DFSR... because the NTFS Change Journal is integral to DFS/DFSR.