/* * These styles apply ONLY to the header and footer assets. */ * { padding: 0; margin: 0; box-sizing: border-box; } .super-nav { display: flex; justify-content: flex-end; align-items: center; margin: 0 auto; max-width: 1264px; padding-left: 40px; padding-right: 40px; height: 40px; text-align: right; } .super-nav a { color: #34427c; margin-right: 20px; padding: 10px; text-decoration: none; } .super-nav a:hover, .super-nav a:focus { background-color: #f7f9fa; } .footer { background: #f5f5f6; color: #555a62; font-size: 14px; line-height: 1.5; padding: 0; } .footer-image { background-image: url("/themes/kaseya/assets/images/footerImage.png"); height: 500px; background-repeat: no-repeat; background-size: cover; margin-top: -100px; } .footer-wrap { padding-left: 18px; padding-right: 18px; max-width: 1236px; margin: 0 auto; } .footer-main-content { background-color: #000; padding: 100px 0; } .footer .footer-col-title { color: #ffffff; font-weight: 700; font-size: 13px; padding-bottom: 10px; text-transform: uppercase; } .footer .footer-link { color: #9b9ca0; text-decoration: none; } .footer .footer-link:hover, .footer .footer-link:focus, .footer .footer-link:active { text-decoration: underline; } .footer-main-content .footer-link { padding-top: 10px; } .footer-row { display: flex; flex-wrap: wrap; justify-content: space-between; align-items: center; margin: -3px; } .footer-main-content-row { align-items: flex-start; } .footer-bottom-content { padding: 10px; align-items: center; } .footer-col { padding: 0 3px; display: flex; flex-direction: column; } .footer-col-copyRight { justify-content: flex-start; color: #9b9ca0; flex: 1; display: flex; } .footer-last-col { flex-direction: row; } .footer-last-col .footer-link { padding-right: 10px; text-transform: uppercase; } @media screen and (max-width: 768px) { .super-nav { padding-right: 0; } .footer-image { height: 250px; } .footer-main-content { padding: 40px 0; } .footer .footer-col-title { padding-top: 10px; } .footer-row:not(.footer-main-content-row) { display: block; } .footer-col:not(.footer-main-content-col) { width: 100%; text-align: center; padding: 10px 0; } .footer-main-content-col { width: 50%; } .footer-last-col { flex-direction: column; } .footer-last-col .footer-link { padding-bottom: 10px; } } /*# sourceMappingURL=styles.css.map */ Ask the Community Groups

Backup Protect

Resolving the issue: Change Journal appears to have wrapped (Expanding the Windows NTFS Change Journal)

ISSUE

Your experience one of the following errors:

The first record available for reading from the Change Journal for volume '<drive letter>' is higher than the agent backup in previous backup and indicate there is a chance that file or directory changes will be not backed up.
Change Journal for volume <drive letter> appears to have wrapped.
The USN Journal was not registered because it experienced a wrap condition.
Backup job was terminated due to Change Journal registration errors.

CAUSE

Like the Microsoft Event Viewer, the Microsoft Update Sequence Number Journal for NTFS (aka the NTFS Change Journal), has a defined file size for tracking the changes that occur on the computer. When the file is full, it drops the oldest line items allowing for new changes to be logged. If the Unitrends appliance find that the oldest record in the Change Journal is higher than the value expected, it will fail the Child backup (Incremental/Differential), present the error, and demand a new Full backup to ensure consistency and accuracy in the data to be collected.

RESOLUTION

There are two ways to resolve this issue:

Using the Unitrends Client Agent (must have release 10.0.0-3 or newer):

Ensure you have installed the most recent version of the Unitrends Client Agent.
Edit the file C:\PCBP\MASTER.INI file.
Change the value for ChangeJournalSizeMB to be up to 4096 (this value is in MB, thus 4GB up to 4GB of RAM).
Save the file.
Restart the Windows Service named BP Agent.

Using the Microsoft method

Follow the instructions in the article "Windows agent file-level backup failure due to change journal wrap or Journal range exceeded."

NOTE: As of release 10.0.0-3 the master.ini (general configuration) parameter “ChangeJournalSizeMB” is now properly handled by the agent. If the maximum change journal size is smaller than the master.ini parameter, it will be enlarged to match the master.ini parameter. The agent will not decrease the maximum change journal size. On an initial agent install (no agent has been installed before), the default value for “ChangeJournalSizeMB” is 1024 (or 1 GB) or 2048 (or 2GB) depending on the Agent Version. We recommend you do not exceed the value of 4096 (or 4GB) or the amount of available RAM (which ever is smaller) as performance may be adversely affected.