Backup job (incorrectly?) reporting not enough disk space

[timofcourse]

Hi there
One of our backup jobs recently started failing to backup a specific VM with the following error code:

Processing XXX: Failed to call RPC function 'Vss.GetFileFromGADir': Error code: 0x80070070. Failed to invoke func [GetFileFromGADir]: There is not enough space on the disk.. Cannot copy file. Source file: [\\XXX\ADMIN$\VeeamVssSupport\metadata\VSS\BackupComponents.xml]. Target file: [C:\Windows\{d8170b78-6e1d-4d7c-8c99-9a0159380e1c}\BackupComponents.xml]. CopyFile() failed. Win32 error:There is not enough space on the disk. Code: 112.

The thing is, this server has more than 15GB free. If it matters, this is also our vCenter server VM. Finally, I think this error started occurring after we changed the job's Backup Mode from Reverse to Incremental earlier this week, but can't be 100%.

Any thoughts from the community before we open a ticket with Veeam support?

Thanks!

[dst]

Hi,
I have exactly the same issue since le last microsoft update !!! (friday)
Some servers (not all) have the issue but disk have many free space...I have made no change in bakup, only MS update on friday...

If anyone have an idea ?

Thanks.

[dst]

Hi,

I have open a case, i'm waiting for the response.

Best regards.

[foggy]

Yes, opening a case is always recommended in such cases. Thanks.

[timofcourse]

Glad to hear I'm not the only one. Ill do the same.

Thanks.

[dspjones]

any resolution to this? I have the same issue too on 1 job. Both the server being backed up and the veeam server, the proxies, and the repository have plenty of space.

[veremin]

What's your support ticket ID? Thanks.

[mboucher87]

What was the resolution to this? Having same issue

[NightBird]

Backup to cifs share ? (Qnap or syno ?)

[csydas]

Hi all,

We had this, and it was the Guest Interaction Proxy we were using that filled up. I can't remember what did it, but for us we checked the sysvol and it was fullup.

[foggy]

Anyway, there's no single case ID in the thread, so we cannot check the solution. Feel free to contact support directly to verify your installation.

[mboucher87]

Hi all,

We had this, and it was the Guest Interaction Proxy we were using that filled up. I can't remember what did it, but for us we checked the sysvol and it was fullup.

Thanks, that's what it was! Would be great if they could include in the error message that it's the proxy that's out of space!

[veremin]

And what machine was mentioned in the error log?

[\\MachineName\ADMIN$\VeeamVssSupport\metadata\VSS\BackupComponents.xml]

Thanks!

[mboucher87]

The Source File section has the machine being backed up and the Target File just says C:\ ... no machine name shown.