Frustrating Unitrends error
-
Is this the exact error?
“FATAL: NO MORE SPACE ON DEVICE (DESPITE RECOVERY ATTEMPTS).
No purgable backups were found.”
-
I was dealing with a new customer with that error recently that accidentally had included their old backup solution's folders in the Unitrends backup, resulting in a backup that was a few TB larger than the appliance capacity... thus the no space error.
-
@art_of_shred said:
Is this the exact error?
“FATAL: NO MORE SPACE ON DEVICE (DESPITE RECOVERY ATTEMPTS).
No purgable backups were found.”
Yes, that's what I was seeing.
-
@art_of_shred said:
I was dealing with a new customer with that error recently that accidentally had included their old backup solution's folders in the Unitrends backup, resulting in a backup that was a few TB larger than the appliance capacity... thus the no space error.
Hmmm... definitely something to check, then.
-
Here's the first article to refer to, although I am sure you already looked at it.
http://support.unitrends.com/ikm/questions.php?questionid=781
-
@art_of_shred Yep, checked that - settings are as recommended.
-
Have you talked to support? What version are you running? Any core dumps? Could be a lot of different things, you may just be over your capacity.
-
Any word on the df output?
df -h -
Ended up being something different altogether, having to do with D2D space allocation.
Fixed.
-
@Katie said:
Ended up being something different altogether, having to do with D2D space allocation.
Fixed.Glad you got it working!
-
@ajstringham said:
@Katie said:
Ended up being something different altogether, having to do with D2D space allocation.
Fixed.Glad you got it working!
Thanks, me too!
-
How did I miss that one? I thought I mentioned to look at the capacity setting in Settings/Storage & Retention/Backup Devices. Since the release of 7.5, I've seen a few systems that have it set to 200GB by default (glitch). It should be a custom size, equal to the actual allocated backup space in the D2D storage (something like 4898GB on an 824, for example). But, I'm glad you found it and got it fixed. Hopefully that will go away in the next updates, but it's been happening fairly regularly for the past few weeks.
