If /usr is running out of space and /usr/local/jetapps is large, identify which part of the directory is using the space before making changes. We recommend keeping the JetApps installation at its standard path so updates and support can use the expected layout.
Check disk usage
Run the following commands as root:
df -hT /usr/local/jetapps
du -hx -d 2 /usr/local/jetapps | sort -h | tail -20Confirm that the proposed destination is a persistent filesystem with enough free space and inodes. Before changing a JetBackup directory setting, wait for active backups, restores, and downloads in the Queue to finish. Keep a current server backup and console access available.
Use JetBackup's directory settings
In the JetBackup admin panel, go to Settings → General:
- Workspace Directory: If temporary workspace files account for the usage, follow JetBackup's guidance to move the existing workspace contents to the new location before changing this setting.
- Download Directory: If generated downloads account for the usage, create a new directory on the larger filesystem and set that path in JetBackup. JetBackup recommends creating a new directory instead of moving the old download directory. On Plesk, ensure the
pssaadmuser can access the new path.
See the JetBackup 5 General Settings documentation for details.
These settings affect only the files they manage. If most usage is elsewhere in /usr/local/jetapps, they may not recover enough space. Do not delete JetBackup databases, caches, logs, or backup files without confirming their purpose with support.
Verify the result
After changing a setting, confirm that JetBackup services and the admin panel work. Run a small backup or download that uses the changed directory, check its final status in Queue and Logs, and confirm the expected output appears. Recheck free space on both filesystems.
If the installation itself is using the space
Contact support with the directory size results and the available space on the proposed filesystem. Moving the entire installation to another partition and replacing /usr/local/jetapps with a symlink creates a nonstandard layout and is not our general recommendation.
