Explain why backups are going to /usr/bp/bin
The backups are failing with message target /usr/bp is full
For more detailed information on backup failures and performance issues see Unitrends KB 5062 - Backup Failures and Performance Issues
Warning: Serious problems may occur if these commands are executed incorrectly. These problems may require redeployment of the appliance, result in a loss of data, and/or cause system downtime. Unitrends cannot guarantee these problems can be solved and customers should proceed at their own risk.
The following process will verify the /usr/bp partition is full, check the system log level, move the logs.dir directory to a different partition with more free space (such as /backups), and create a symbolic link to that partition.
Validate the Free Space on Each Partition
- Open the UI of the appliance.
- Select "Configure" on the left.
- Select the "Edit" button at the top.
- On the "Advanced" tab, select "Support Toolbox" at the bottom.
- Select "Disk Free Space" and the following dialog will be displayed:
- In this example, our /usr/bp partition is 100% utilized and our /backups partition has a significant amount of space free.
Validate Log Settings
Older log files in /usr/bp/logs.dir may be removed. Verify debug log levels are not set above 3. For more information on log levels and how to configure them, see: Log Level Definitions
In rare instances, a system process may be hung. Rebooting the appliance should resolve the issue.
Move logs.dir To a New Partition
- Connect to the appliance via SSH.
- Stop the database and tasker:
- Move the logs.dir directory to a partition with more free space, such as /backups:
mv /usr/bp/logs.dir /backups/logs.dir
- Create a symbolic link:
ln -s /backups/logs.dir /usr/bp/logs.dir
- Restart the database and tasker:
The most probable cause is that a log has filled up the /usr/bp/logs.dir directory.