Knowledgebase: Troubleshooting
Backup failed with "... WARNING: database or disk is full"
Posted by Andre Kuehnemund, Last modified by Andre Kuehnemund on 24 September 2015 10:55

Customer was running P5 version 5.1.4 at the time.

Depending on the size of a backup, P5 would sometimes generate enormous temporary lookup files - sometimes several GB in size. That, in turn, could cause a server's root file system to fill up temporarily. Whenever that happened, the backup job would fail, the temporary lookup files would be deleted, and afterwards it looked as if there was plenty of available disk space.

Starting with version 5.1.7, we implemented a different way of generating those lookup files that avoids creating those enormous files. Therefore, anyone running into this issue should upgrade to version 5.1.9 ( or higher (

(2 vote(s))
Not helpful

Comments (2)
John Pearse
18 September 2018 13:24
We are having this error every day on a particular volume. 10 other volumes all work ok.

from the log : FAILED! (0 - (ourservername: file check/collection: /P/RESOURCES: restore failed: database or disk is full))

But our system is already at version 5.5.5 so not sure what to do next...
Andre Kuehnemund
30 October 2018 16:22
@John: Whenever you have a specific issue like this one, please open a support ticket. Please download and include the P5 support data package from your server when you create the support ticket. The P5 support data will provide us with the most recent P5 logs from your server and a copy of your P5 configuration.
Based on what you wrote, it looks like the restore target (/P/RESOURCES) may have been full, but I can't tell for sure without having seen the logs.
Post a new comment
Full Name:
CAPTCHA Verification 
Please enter the text you see in the image into the textbox below (we use this to prevent automated submissions).