Hello @Hunterly 
Do you have enough free disk space on your Veeam B&R?

 

Hello @Stabz,

yes - there is enough free disk space on the VM and on the backup server.
The VSS service can also be started without any problems 

On the VBR server both the repo drive but also other drives need space for logs, etc.   It is possible that one of those is out of space to write files for the backup like a log file.  Also can post screenshot of the error or more details about the job?

Hi @Hunterly -

Welcome to the Community! For Guest Indexing, you need enough space on the Veeam Backup Server as Chris shared to perform the indexing. Per the User Guide:

See/read below for more info:
https://helpcenter.veeam.com/docs/backup/vsphere/indexing.html?ver=120#requirements-and-limitations-for-vm-guest-os-file-indexing

Make sure you do indeed meet the space requirements stated above.

Hello @Chris.Childerhose and @coolsport00 ,

I have checked the servers - there is enough memory available:

C: 65,7GB free of 89,2 GB
E: 531GB free of 1,49TB
F: 240GB free of 999GB
G: 626GB free of 1,95TB

Backup repository: 40TB free of 65,TB 

I can't find any explicit errors in the log files either. 
Can you describe where I should look more closely?

The jobs still give a warning. 

Hello,
Have you check that all vss writers are without errors ?
Cmd line: vssadmin list providers

Have you tried to reboot the server ?

In parallel you should open a ticket to Veeam Support

Hello @Stabz,

i checked this.

There is no error:

C:\Windows\system32>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Provider name: 'Microsoft File Share Shadow Copy provider'
   Provider type: Fileshare
   Provider Id: {***}
   Version: 1.0.0.1

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {***}
   Version: 1.0.0.7


C:\Windows\system32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
   Writer Id: {***}
   Writer Instance Id: {***}
   State:  1] Stable
   Last error: No error

Writer name: 'VSS Metadata Store Writer'
   Writer Id: {***}
   Writer Instance Id: {***}
   State:  1] Stable
   Last error: No error

Writer name: 'Performance Counters Writer'
   Writer Id: {***}
   Writer Instance Id: {***}
   State:  1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {***}
   Writer Instance Id: {***}
   State:  1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {***}
   Writer Instance Id: {***}
   State:  1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {***}
   Writer Instance Id: {***}
   State:  1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {***}
   Writer Instance Id: {***}
   State:  1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {***}
   Writer Instance Id: {***}
   State:  1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {***}
   Writer Instance Id: {***}
   State:  1] Stable
   Last error: No error

@Hunterly -

At this point it's best to get ahold of Veeam Support. 

The logs are located here for jobs - C:\ProgramData\Veeam\Backup\JobName

Check there but at this point you are better off contacting Support get further assistance since storage space is not an issue.