Jetindexd fills up the /usr folder

On JetBackup 5 v5.2.x and below, FTP and S3-Compatible destinations utilizes the jetindexd (WiredTiger-based) service to track account changes and allow JetBackup 5 to push data incrementally.

Each snapshot creates its own indexing database, and a high backup retain setting for your Backup Job(s) coupled with a high number of accounts hosted on a server may cause the jetindexd directory (/usr/local/jetapps/var/lib/jetindexd/) to have a high disk usage and fill up the /usr folder due to the number of snapshots per account that the Jetindexd database needs to keep track and index.

The recommended way to reduce the disk usage caused by Jetindexd is to consider reducing the number of backup retention configured on your Backup Job(s) which lowers the number of snapshots that JetBackup will need to track. Once the backup retention has been reduced, it may take up to 24 hours for the automatic cleanup process to execute and begin reducing the jetindexd disk usage.

  • 1 Users Found This Useful
Was this answer helpful?

Related Articles

Why are my Directories showing Invalid Dates when browsing?

Object-based storage such as AWS S3 destinations does not include any modified dates for...

Email Notifications Are Not Being Sent

JetBackup 5 uses Notification Integrations to send Notifications based on the configured...

What are the level of Alerts in JetBackup 5?

JetBackup 5 now has only 3 Alert levels compared to JetBackp 4. All 3 levels will appear on the...

Create Destination Error: This destination path is already owned by other destination

On JetBackup 5, you may notice the following error when creating a destination that uses the same...

Common Backup Job Exclude List for DirectAdmin Accounts

Information regarding how to exclude certain files/folders from a backup in JetBackup 5 can be...