Veeam Backup & Replication issue

[eyetea]

Hi all,

 

Another thing I've never had any real experience with!

 

We use Veeam as our backup solution here, and up until now I have only used it to restore kids work, any probs my old boss would sort it out! Unfortunately for me he's gone and I'm probably on my own till at least the new year now

 

Within the last week, Veeam has failed to back 3 of our VM's up, each of these 3 failing with the message Error: Client Error: Incorrect Function. Failed to read data from the file [PATH]. I'm also now unable to restore anything from these 3 VM's, including a backup points that I knew was working last week when I had to use it to get some work back! Gives the error MountRestorePoint failed, mountId 'id' FlrManagementService: Failed to mount restore point (MountId:id) Mount failed Client error: Incorrect function.

 

Pic attached of error screenshot when trying to open a restore point from affected VM's

 

 

All of the other VM's have backed up successfully and I am able to access files from them all.

 

Any help would be gratefully received!

 

J

[eyetea]

Another VM has joined the above list!

[PotNoodleTech]

I would be looking initially at the storage repository you are using to store these backups. I've never seen that error before but it looks as it if it hints at the fact that it cant actually read/write properly from the backup files.

 

Are you backing up to local storage on the veeam server, or USB, or NAS/SAN?

[synaesthesia]

Also worth checking the storage on the VM's themselves (the host) to make sure they've not run out of space for snapshots.

[eyetea]

Backs up to SAN, the hosts seem to have enough space! Tried to access one VM's restore points today and was able to..

 

Have logged a ticket with Veeam now our support contract has been renewed, will update as and when.

[Ergo_Computing_IS_Support]

Hello,

I can see in the error message is refers to the directories of your backup files e.g. NEW2014-11-13T20024.vib

 

Do these files still exist when you navigate to this location? It might be that the Veeam database is looking for files that do not exist any more (perhaps fell out of retention or deleted manually) or that they moved or they've even been renamed.

Also, from within Veeam, have you tried 'Import Backup', selecting the backup files from the windows directory (D:\Veeam Backups\) and then restoring from these?