Skip to main content
  • EN

Hello folks,
Attempting a bare metal recovery on similar new hardware as a server was hijacked.

Backups are encrypted (password known) and I can see the restore points in Veeam Community Edition 12.
Sadly everytime I try to access/unpack/recover the files it gives me
(A) an error message that alway include the text “Not supported for read-only access. 
(B) currently a CHMOD value ranging from 80-190

 

Example Restore job failed Error:

Storage version e830813235] is not supported for read-only access.

Failed to open storage for read access. Storage: oServer1 BUD2024-08-01T230026_070F.vib].

Failed to restore file from local backup. VFS link: summary.xml]. Target file: MemFs://frontend::CDataTransferCommandSet::RestoreText_{0ba8e79c-f75a-4323-bdeb-ae273994eeed}]. CHMOD mask:  137].

Restore job failed Error: Agent failed to process method {DataTransfer.RestoreText}.

 

Anybody have any pointers how I can extract the files from the backups? Would appreciate your input.

 

Other threads read:

Drive incompatible/corrupt

https://forums.veeam.com/veeam-agent-for-windows-f33/storage-version-is-not-supported-for-read-only-access-t55578.html

Corrupt Backup

https://pariswells.com/blog/random/veeam-storage-version-3701403-is-not-supported-for-read-only-access

Wrong Veeam version
https://forums.veeam.com/veeam-agent-for-windows-f33/restore-failed-storage-version-13-is-not-supported-for-read-only-access-t75191.html

Welcome to the Community @Eddy.NH 

Couple of questions, is this a Windows Server?

Also does the location where you are recovering to have read-write access?

Additionally, there is this tool that you can use:

https://helpcenter.veeam.com/docs/backup/vsphere/extract_utility.html?ver=120

The following will be helpful -

  1. As Dips pointed out what OS are you using for VBR?
  2. Are you recovering a Linux guest?
  3. What specific version of Veeam are you using?  12.X?
  4. Any other specific information that might help.

It seems like this one may come down to a support ticket but let’s see if we can help you here first, keeping in mind this is the Community and not Support.

Also you might want to search the Forums as well to see if any posts of similar nature we put there with possible answers - http://forums.veeam.com

 

The Hypervisor as bare as possible.

  • Windows Server 2016 Standard. Standalone
  • HyperV
  • Veeam Community Edition 12x

 

Attempting to open one of the files with Backup Extractor just give the initial error message

Storage version 830813235] is not supported for read-only access.

 

Since I have a bunch of backups i´ve the feeling it´s a version incompatibility or I need to format the drives again. But I´m not sure.

The Hypervisor as bare as possible.

  • Windows Server 2016 Standard. Standalone
  • HyperV
  • Veeam Community Edition 12x

 

Attempting to open one of the files with Backup Extractor just give the initial error message

Storage version 830813235] is not supported for read-only access.

 

Since I have a bunch of backups i´ve the feeling it´s a version incompatibility or I need to format the drives again. But I´m not sure.

Are you using something like Storage Spaces?  The storage version message is the clue here.  Are you able to copy a VBK file from the current location to a secondary location to try extracting?

At this point since it involves Hyper-V I would suggest a Support ticket to get assistance as you can still do this with CE edition just it is best effort support.

I´ve put/copied everything on local hard drives. 

Thanks for the suggestion of the Support Ticket!

I´ve put/copied everything on local hard drives. 

Thanks for the suggestion of the Support Ticket!

Not a problem.  Let us know how it goes with Support and if you get a resolution.

 
 
 

Question: 

The Veeam version on the old server was an older version the currently installed. 
I think 12.1 Could that pose a problem?

Question: 

The Veeam version on the old server was an older version the currently installed. 
I think 12.1 Could that pose a problem?

Not sure if it would or not but best to work with Support to see if that is the root cause or not.

 
 
 

Question: 

The Veeam version on the old server was an older version the currently installed. 
I think 12.1 Could that pose a problem?

Usually, they are backwards compatible but as @Chris.Childerhose mentioned, it is worth working with Support.

Question: 

The Veeam version on the old server was an older version the currently installed. 
I think 12.1 Could that pose a problem?

Usually, they are backwards compatible but as @Chris.Childerhose mentioned, it is worth working with Support.

Thanks. We are waiting for any response. Considering to move to a support subscription. We just contacted their sales team.

Question: 

The Veeam version on the old server was an older version the currently installed. 
I think 12.1 Could that pose a problem?

Usually, they are backwards compatible but as @Chris.Childerhose mentioned, it is worth working with Support.

Thanks. We are waiting for any response. Considering to move to a support subscription. We just contacted their sales team.

Please let us know how you get on. :)

Question: 

The Veeam version on the old server was an older version the currently installed. 
I think 12.1 Could that pose a problem?

Usually, they are backwards compatible but as @Chris.Childerhose mentioned, it is worth working with Support.

Thanks. We are waiting for any response. Considering to move to a support subscription. We just contacted their sales team.

Support should get it sorted for you.  Keep us posted.

Comment


Terms & Conditions