Ask the Community
Groups
Novell OES: But backups never complete or backup performance is considerably slow - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p>The following symptoms are experienced when backing up a Novel OES server using the Unitrends Client Agent: </p> <ul><li>But backups never complete</li> <li>Backup performance is considerably slow</li> </ul><h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p></p> <h2 data-id="resolution-1">Resolution 1</h2> <br>The logs for the OES backup are located on the OES server in the directory path of /usr/bp/logs.dir/ <ol><li>If you have not done so, please reinstall the Unitrends Client Agent for OES using the root user of the OES system.</li> <li>Run the backup job Full backup (you might need to run the differential as well).</li> <li>Run the following search queries on the OES server to isolate the item and path that is causing the failures: <ul><li>grep 'traverse\|>400' /usr/bp/logs.dir/LAST_BACKUP</li> <li>grep 'traverse\|>400' /usr/bp/logs.dir/client.stderr</li> <li>grep 'traverse\|>400' /usr/bp/catalog.dir/*</li> </ul></li> <li>Once you have found the items, rename them</li> </ol><br>Example of output: <table border="1"><tbody><tr><td colspan="1" rowspan="1"> <div>[root@UB107 logs.dir]# grep 'travers\|>400' /usr/bp/logs.dir/LAST_BACKUP /media/nss/DATAVOL/DATA/RESTRICT/FDD/PROGRAM FOLDERS/ABCDE/! INACTIVE - BUILT-OUT/2AG -TP6/INFORMATION/WHEATER12345/FROM ABC/6_2AG/A25/FR-3AC9--3AA2--30AC--30E9--F0B9--6607--9A4D--8010--4E44-/2-56AE--76AE-/TP6-FF08-2NX-FA09--3000-FR-FA84--FF9E--FF71--FF76--FA9E--FF97--FF7D--6607--964D--8010--4E45--7ABA--8A8D--7D50--679C- 2008-11-06 2052 -8C4A--5CF6--526F--5E3B--4EFB--FA08--55B6--696D--6280--8853--FA09-.MLF [>400]</div> </td></tr></tbody></table><h2 data-id="resolution-2"> <br>Resolution 2</h2> <div> </div> Add an exclusion list to your backup by navigating to Jobs > Job Manager, select the job and click Edit, then under Job Inventory Settings click on the Edit pencil icon next to the OES18 server and add an Exclude list<h2 data-id="cause"><strong>CAUSE</strong></h2> <p>This is generally caused by the Novel TSA model reaching a limitation such as use of non-UTF8 characters or the length of the file exceeding a threshold (e.g.: 400 characters).<br><br>In OES18 (OES 2018) the backup may never start if there is not an exclude list, even if a single file is excluded this can cause the backup to start transferring data where before it would not.</p> </article> </main>