Ask the Community
Groups
Backups Failing, /usr/bp full (moving logs.dir) - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Explain why backups are going to /usr/bp/bin</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <p>The backups are failing with message target /usr/bp is full</p> <p>For more detailed information on backup failures and performance issues see <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Funitrends-support.zendesk.com%2Fhc%2Fen-us%2Farticles%2F360013174757">Unitrends KB 5062 - Backup Failures and Performance Issues</a></p> <h3 data-id="n-a"> </h3> <h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p></p> <p><b>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.</b></p> <p>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.</p> <h3 data-id="validate-the-free-space-on-each-partition">Validate the Free Space on Each Partition</h3> <ol><li>Open the UI of the appliance.</li> <li>Select "Configure" on the left.</li> <li>Select the "Edit" button at the top.</li> <li>On the "Advanced" tab, select "Support Toolbox" at the bottom.</li> <li>Select "Disk Free Space" and the following dialog will be displayed:<br><img alt="Disk Free Space dialog" height="140" src="https://us.v-cdn.net/6032361/uploads/migrated/SKPC4BW3AP3Z/eid-ka01w000000tcf5-feoid-00n40000003czqx-refid-0em40000000qtxs." width="500" class="embedImage-img importedEmbed-img"></img></li> <li>In this example, our /usr/bp partition is 100% utilized and our /backups partition has a significant amount of space free.</li> </ol><p> </p> <h3 data-id="validate-log-settings">Validate Log Settings</h3> <p>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: <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Funitrends-support.zendesk.com%2Fhc%2Fen-us%2Farticles%2F360013269118">Log Level Definitions</a></p> In rare instances, a system process may be hung. Rebooting the appliance should resolve the issue. <p> </p> <h3 data-id="move-logs-dir-to-a-new-partition">Move logs.dir To a New Partition</h3> <ol><li>Connect to the appliance via SSH.</li> <li>Stop the database and tasker: <pre class="code codeBlock" spellcheck="false" tabindex="0"> /etc/init.d/bp_rcscript stop</pre> </li> <li>Move the logs.dir directory to a partition with more free space, such as /backups: <pre class="code codeBlock" spellcheck="false" tabindex="0"> mv /usr/bp/logs.dir /backups/logs.dir</pre> </li> <li>Create a symbolic link: <pre class="code codeBlock" spellcheck="false" tabindex="0"> ln -s /backups/logs.dir /usr/bp/logs.dir</pre> </li> <li>Restart the database and tasker: <pre class="code codeBlock" spellcheck="false" tabindex="0"> /etc/init.d/bp_rcscript start</pre> </li> </ol><br> <h2 data-id="cause"><strong>CAUSE</strong></h2> <p>The most probable cause is that a log has filled up the /usr/bp/logs.dir directory. </p> </article> </main>