SSR wrote:Currently we have around 4.5TB of VMs that are backed up. The size of the backups directory is 6,5TB. The size of the replicas directory is 7.5TB.
foggy wrote:Unless you remove older restore points from disk (full and related increments), the space will not be released, since retention applies at the end of the successful job run, which you cannot achieve due to insufficient space.
foggy wrote:When you're mentioning the replicas directory, do you mean the Replicas folder keeping replica VMs metadata, which is located in the same repository?
SSR wrote:I'm not sure what data exactly it comprises, but it's the directory that the replication job points to. I see directories for each VM there, and VHDX files. There's one replica that is failing, and for that one I note there are also a number of AVHDX files. Restore points perchance?
SSR wrote:I think I may have spotted the problem though. I detached the old MBR drive from the file server, but I didn't delete it. I think Veeam is both backing up and replicating this detached drive as well, which is another 2TB, because I can see a copy of the VHD in the Replicas directory. I have taken a chance and deleted it, as the new GPT drive seems to be working correctly. I will run the file server backup job again, and if that works correctly I'll try the replication job.
SSR wrote:The backup job doesn't appear to have compressed, despite being set to. The VKB file is currently 6TB, when the servers combined are 4.3TB.
SSR wrote:Would it be wise to delete the file server backup and/or replication job, delete the relevant Backup and Replicas folder, and recreate them? I'm not sure I have any other choice, to free up this space.
foggy wrote:This is not a compression issue, but due to the fact that data blocks are not actually cleaned up but just marked as free.
foggy wrote:If it is acceptable to live some time without any backup at all, then you can do this. At least you can first do backup, then, once it succeeds, replication.
SSR wrote:With Veeam 9 though they seem to have added a maintenance task, which you can enable to "defragment and compact" full backup file. Would this not remove these cleared data blocks and reduce the backup file size?
SSR wrote:For this particular job I had the space, but as per above the VKB file didn't reduce.
SSR wrote:Replica job at 99%, 2.5TB free on the NAS... although unless it recovers the space space at the end there's something odd there also, as 5.5TB of VMs are taking up 8.5TB of space (restore points is still set to zero).
SSR wrote:The two file server jobs within the replicas job have either had "failure to create change tracking time stamp for virtual disk" or "change tracking files are not specified". These show as warnings. Not sure how critical these are.
Users browsing this forum: No registered users and 1 guest