Mynotify change tracking - threshold

ISSUE

Linux change journal reports wrapping or audit of restore points results in missing recovery objectives.

RESOLUTION

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:

Using an editor such as VI:
/usr/bp/incremental_forever/journal.bak

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: https://support.unitrends.com/UnitrendsBackup/s/article/000002477

CAUSE

Mynotify fails to keep track of excessive change per second.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Contact us