Ask the Community
Groups
Mynotify change tracking - threshold - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p>Linux change journal reports wrapping or audit of restore points results in missing recovery objectives.</p> <h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p>Recent development efforts have classified a rule of thumb of 100 changes per second as being the threshold to safely track mynotify changes. To view this:<br><br>Using an editor such as VI:<br>/usr/bp/incremental_forever/journal.bak<br><br>If you see more than 100 changes per second (epoch), it may be advisable that mynotify should not be used. Follow the KB to remove mynotify and switch to a full/diff strategy. Seen here: <a href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fsupport.unitrends.com%2FUnitrendsBackup%2Fs%2Farticle%2F000002477">https://support.unitrends.com/UnitrendsBackup/s/article/000002477</a></p> <h2 data-id="cause"><strong>CAUSE</strong></h2> <p>Mynotify fails to keep track of excessive change per second.</p> </article> </main>