JetBackup 5 does not send alert when inotify limit was reached and it cannot backup new users

Zerg shared this idea 3 years ago
Under Consideration

When all inotify watches are used (fs.inotify.max_user_watches) because e.g. Imunify360 is using them, then JB 5 does not backup new users. JB 5 is using inotify to watch for /usr/local/jetapps/var/run/jetbackup5/sync_accounts.queue changes, and without ability to create new inotify watch, it cannot sync new users, and therefore backup them.

JB 5 should create critical alert with information to increase fs.inotify.max_user_watches when it cannot create inotify watch.

Administrators are not aware that users are not backed up, because there are no errors in backup jobs. It was detected by our custom backup verification script.

Replies (1)

photo
1

Hello Zerg,


Thank you for your feedback and for opening the Feature Request. Our developers will review your request and provide updates accordingly. Please note that we use the voting system to gauge demand for additional features. The more votes a request has, the more likely it will be up for consideration by our developers.

Best Regards,

JetApps Team

Leave a Comment
 
Attach a file