I'm new to using Veeam for VM backups and have a question about the way space is being handled on my backup destination NAS.
I'm new to a position where Veeam has been used for many years, but I am struggling to understand why Veeam seems to be taking up twice the amount of disk space than it should. Backup notifications hadn't been working for a while before I got here, and once I got them going again I noticed that we were getting loads of out of space errors on our destination NAS, leading me to believe that things hadn't been working properly for a while.
I upped the disk space on the destination NAS by adding larger drives, but within a couple of days we were back to getting warnings.
Here's how things look when I ssh into the NAS (sanitized with xxxxx):
Code: Select all
xxxxx@NAS003:/volume1$ sudo df -h .
Password:
Filesystem Size Used Avail Use% Mounted on
/dev/vg1/volume_1 21T 21T 240G 99% /volume1
xxxxx@NAS003:/volume1$ sudo du -h -d 1 VEEAM/
11T VEEAM/@eaDir
0 VEEAM/TEMP SOFTWARE
11T VEEAM/xxxxx-Backup
56M VEEAM/VeeamConfigBackup
125G VEEAM/xxxxx_xxxxx
21T VEEAM/
xxxxxx@NAS003:/volume1$ sudo du -h -d 1 VEEAM/"@eaDir"/"@tmp"
7.7T VEEAM/@eaDir/@tmp/cloud-syncd.work.dir
7.7T VEEAM/@eaDir/@tmp
xxxxxx@NAS003:/volume1$ sudo du -h -d 1 VEEAM/"@eaDir"/"@tmp.12668"
2.6T VEEAM/@eaDir/@tmp.12668/cloud-syncd.work.dir
2.6T VEEAM/@eaDir/@tmp.12668
When I look in the Veeam GUI, I can see that the data being used in the repository is reporting as 9.9TB.
Am I safe to delete things in the "@eaDir" directories to gain some more space?
Where should I be looking to figure out what's actually being used?
Again, sorry for the noob questions, any help would be greatly appreciated!