I installed UrBackup Server on a Raspberry Pi 3 Model B+ (from source, as described).
The client is a Windows 10 PC, it was backing up fine before (older version of the UrBackup Server, older Raspberry Pi). I updated the client, now it is backing up to the new server as expected.
However, the server status page displays this error message:
There is currently not enough free space in the backup folder. UrBackup tried to delete old image and file backups but is now not allowed to delete more. Please change the settings to store less backups or increase the storage amount to allow UrBackup to continue to perform backups
When I click Ok. Reset this error, the error message disapears. I noticed that the backup process (full image backup) is still (or again) running (according to the activity tab).
The error message reappears after a while.
I am backing up a 335.21 GB Windows partition to an 4 TB external usb drive. Currently, around 70 GB are already backed up. The windows 10 machine is the only PC backing up to the UrBackup server.
The live log (accessed via the activity tab) contains several errors:
|28.03.18 19:15 |INFO |Not enough free space. Cleaning up.|
|—|---|—|
|28.03.18 19:15 |ERROR |Could not free space for image. NOT ENOUGH FREE SPACE.|
|28.03.18 19:17 |INFO |Not enough free space. Cleaning up.|
|28.03.18 19:17 |ERROR |Could not free space for image. NOT ENOUGH FREE SPACE.|
|28.03.18 19:33 |INFO |Not enough free space. Cleaning up.|
|28.03.18 19:33 |ERROR |Could not free space for image. NOT ENOUGH FREE SPACE.|
|28.03.18 19:35 |INFO |Not enough free space. Cleaning up.|
|28.03.18 19:35 |ERROR |Could not free space for image. NOT ENOUGH FREE SPACE.|
|28.03.18 19:53 |INFO |Not enough free space. Cleaning up.|
|28.03.18 19:53 |ERROR |Could not free space for image. NOT ENOUGH FREE SPACE.|
|28.03.18 19:55 |INFO |Not enough free space. Cleaning up.|
|28.03.18 19:55 |ERROR |Could not free space for image. NOT ENOUGH FREE SPACE.|
|28.03.18 20:11 |INFO |Not enough free space. Cleaning up.|
|28.03.18 20:11 |ERROR |Could not free space for image. NOT ENOUGH FREE SPACE.|
|28.03.18 20:13 |INFO |Not enough free space. Cleaning up.|
|28.03.18 20:13 |ERROR |Could not free space for image. NOT ENOUGH FREE SPACE.|
|28.03.18 20:29 |INFO |Not enough free space. Cleaning up.|
|28.03.18 20:29 |ERROR |Could not free space for image. NOT ENOUGH FREE SPACE.|
|28.03.18 20:31 |INFO |Not enough free space. Cleaning up.|
|28.03.18 20:31 |ERROR |Could not free space for image. NOT ENOUGH FREE SPACE.|
|28.03.18 20:47 |INFO |Not enough free space. Cleaning up.|
|28.03.18 20:47 |ERROR |Could not free space for image. NOT ENOUGH FREE SPACE.|
Do you have any ideas? Do you need more logs?
Thanks in advance!
That might be an idea …
The client has two partitions, labelled C: and E:
C: is the system partition that is currently beeing imaged. Windows 10 reports 100 GB free space while the total volume is 464 GB. So I guess, there should be enough space.
E: is a data partition, that was also set to be imaged. On this partition Windows reports 20 GB free space, total volume 465 GB. So there might be an issue. However, this parition is currently not beeing imaged!
Just to be sure, I changed the settings, so that this partition will not be imaged.
Update: The errors keep coming, both in the status tab and the log from the activity tab.
However, the log in the log tab shows only two errors (from yesterday, right after starting the UrBackup Server):
Errors
28.03.18 15:16
Backing up System Reserved (SYSVOL) partition failed. Image backup failed
Maybe the snapshot thing of windows. (shadowcopy/vss/system protection)
If you right click on drive then property, maybe it has the tab "snapshot/shadow copy
Or , you right click on the drive and there s a “configure snapshot/configure shadow copy” option
Both are the same thing, it depends on the windows version.
And in the parameter are, there should be a maximum size. Its either on the tab itself or there s a configure button.
It should show the current used space for the vss somewhere around that.
If it s full you can disable/enable it and it will be 100% free , but you ll lose the snapshot that exists (won t be able to use windows built-in recovery).
You can also increase max size, but you ll get less usable storage.
If I understand you correctly, UrBackup somehow uses the free space of the protection (in my case 46 GB - 15 GB = 31 GB).
So is this 31 GB to small for UrBackup?
The 15 GB current usage of the system protection did not change during the last hours. When UrBackup is using that space, this should be changing, shouldn’t it?
The space needed by urbackup should is the shadow copy one.
Typically, it’s configured by the setting that you access from the drive letter, but maybe on windows 10 you can t do that , and the setting is only availlable in server versions.
.
But as i understand it, the recovery space use the same type of mechanism and disk space that the shadow copy space.
I am not expert enought to be 100% sureof that and it’s kinda hard for me to double check that on windows 10, i use mostly linux servers/clients, and windows servers.
Yes, urbackup need some of that place, because thats how snapshots works.
All the file modifications made during the backups are written to this space.
Then when the backup is finished this space should be freed (kinda hard to explain).
This issue is no longer important … I needed to do a fresh install of that Raspberry Pi, now everything is working as expected.
I think the error might have been caused by compiling from sources and not using the deb file. I think that the temp might not be set correctly. I noticed on the fresh install, that there is a temp dir inside urbackups backupfolder - I am not sure if it was there before.
I compiled urbackup from source for a Sheevaplug computer (armv5tel) running Debian (marvel). I believe this is a 32-bit system. I encountered the error message in the web-gui stating that there was little disc space with 1.9TB remaining.
Applying the patch @uroni posted above seems to have solved the problem for me Thank you!