If use of the change journal is not desired, it can be disabled by modifying the following entry in the agent’s master.ini file. The file is located on the Windows client in the <agentInstallPath>\PCBP directory (typically C:\PCBP).
UseChangeJournal=False
The minimum change journal size maintained by the Unitrends’ agent is 500MB. This size is configurable by adding an entry into the agent’s master.ini file. The size should be indicated in MB.
ChangeJournalSizeMB=500
The size of the change journal can be enlarged by creating the above entry and setting the value to a number larger than 500.
Caution: The Microsoft best practices for use of change journal recommends that, once created, the change journal size should not be reduced; nor should the change journal be deleted. Likewise, the Unitrends’ agent cannot guarantee successful backup and restore operations in an environment where the size of the change journal has been reduced. Please understand that reducing the size of the change journal may result in corrupt backup operations, possibly causing failure to restore.
Each time that a master backup completes, the change journal for each volume is inspected and enlarged if the size indicated in the master.ini file is larger than the size of the actual journal.
The change journal wrap condition causes a delay in the time it takes for incremental backups to complete. If incremental backups begin to take longer than expected, this may be a result of the change journal wrap condition. When backing up servers that are configured as domain controllers, the change journal wrap condition may occur more frequently.
The change journal wrap condition is not an error and will not interfere with capturing a successful backup. However, because the system must do a full filesystem scan, this does increase the likelihood of a timeout occurring that fails the backup. In the event that the change journal wrap condition occurs, expect to see the following message in the backup summary for the specific backup operation:
Change journal for volume C: appears to have wrapped since the last master backup and will not be used for this backup.
This is not an error condition and does not interfere with the backup.
If this server is a domain controller, then this condition is expected to occur more frequently. To enable use of the change journal for the next incremental backup, perform a master backup to resynchronize with the journal. If the change journal wrap condition occurs too frequently, you must enlarge the current journal size, as described below.