Storage version is not supported for read-only access

[AlexLeadingEdge]

Hi guys, I'm getting this error message. I have retried the backup three times and had three failures. Unfortunately I'm unable to create a ticket as I'm getting "PermissionDeny" when it attempts to upload the logs.

Code: Select all

29/11/2018 10:44:40 p.m. :: Error: Storage version [1667318332] is not supported for read-only access. 
Failed to restore file from local backup. VFS link: [summary.xml]. 
Target file: [MemFs://frontend::CDataTransferCommandSet::RestoreText_{a00b36c5-8442-433d-ba40-a383b0da29af}]. CHMOD mask: [0].
Agent failed to process method {DataTransfer.RestoreText}. Agent failed to process method {DataTransfer.RestoreText}.

//Edit: Reading online people have commented that it appears that the .VBK file became corrupted? Just formatted the drive and the backup has completed successfully.

[Dima P.]

Hi Alex,

Asked our support team to reach you. Stay tuned.

[AlexLeadingEdge]

Thanks Dima. I have just had the same problem again.

[AlexLeadingEdge]

... and I've got the "PermissionDeny" issue again when submitting a ticket.

[AlexLeadingEdge]

I'm wondering if this is an issue with having 4TB USB drives on a Server 2008 R2. I see these drives are formatted as MBR rather than GPT. The odd thing is that it shouldn't be showing a 4TB partition as MBR should cap them to 2TB max.

https://support.microsoft.com/en-nz/hel ... -than-2-tb

The question is, why did the first full backup work, while the second or third backup on each drive has failed?

[AlexLeadingEdge]

I've just swapped the drives over to the next one (there are five) and it seems they've all been formatted as MBR but are showing at 4TB drives. I just don't understand how that is possible?

[Dima P.]

Hi Alex,

I'm wondering if this is an issue with having 4TB USB drives on a Server 2008 R2. I see these drives are formatted as MBR rather than GPT. The odd thing is that it shouldn't be showing a 4TB partition as MBR should cap them to 2TB max.

Might be a 'vendor' trick, check this thread and I'd strongly recommend to covert those volumes to GPT.

[AlexLeadingEdge]

I converted them all to GPT last week but this week I've got a new error:

Code: Select all

[b]10/12/2018 10:50:30 p.m. :: Error: There is no FIB [summary.xml] in the specified restore point. Failed to restore file from local backup. VFS link: [summary.xml]. Target file: [MemFs://frontend::CDataTransferCommandSet::RestoreText_{eb093097-52aa-416c-8304-faebdd83d901}]. CHMOD mask: [0]. Agent failed to process method {DataTransfer.RestoreText}. Agent failed to process method {DataTransfer.RestoreText}.[/b]

[Dima P.]

Alex,

Did you move the backup files to the same disk after the conversion has been made? Thanks!

[AlexLeadingEdge]

No, just formatted the drive and ran a new full backup.

[Dima P.]

It looks like backup job is trying to find the existing backup file and fails. Can you open the backup job and change the backup location to any other folder?

[AlexLeadingEdge]

Changing the folder works. I also note that there is a Full Backup that is only 30MB.

[Dima P.]

I also note that there is a Full Backup that is only 30MB.

This might a bland restore point created at the begging of the failed job run. To be exactly sure all works as expected - start file level recovery from newly created restore point to check it's content. Cheers!

[AlexLeadingEdge]

The hard drive has backed up over the weekend, Friday and Saturday succeeded and then Sunday failed with the same error as before.

[AlexLeadingEdge]

I got this message yesterday:

Code: Select all

[b]19/12/2018 10:43:15 p.m. :: Error: There is no FIB [summary.xml] in the specified restore point. Failed to restore file from local backup. VFS link: [summary.xml]. Target file: [MemFs://frontend::CDataTransferCommandSet::RestoreText_{a0265995-e0d4-4c06-92d1-aad1cf49446a}]. CHMOD mask: [0]. Agent failed to process method {DataTransfer.RestoreText}. Agent failed to process method {DataTransfer.RestoreText}.  [/b]

And today I'm seeing this:

Code: Select all

[b]20/12/2018 10:43:12 p.m. :: Error: All instances of the storage metadata are corrupted. Failed to restore file from local backup. VFS link: [summary.xml]. Target file: [MemFs://frontend::CDataTransferCommandSet::RestoreText_{65c7a92e-58fb-47ca-aa61-d8141a95d60a}]. CHMOD mask: [0]. Agent failed to process method {DataTransfer.RestoreText}. Agent failed to process method {DataTransfer.RestoreText}.[/b]

[Vitaliy S.]

Alex, please avoid posting log snippets in these forums (as per our rules), as any technical issue should be investigated with our support team. Thank you!

[AlexLeadingEdge]

Hi guys,

Just had this same issue again. Formatting the USB drive fixed the issue.

[Vitaliy S.]

Since formatting is just a workaround, I'd suggest looking into this with our support team, especially when you can reproduce it.

[maranda]

Hi,

Recently our system was infected with a ramsomware (both server and backups). After payment we got back all data but when we tried to recover the server using recovery media appear this message:

Code: Select all

Additional Details: Storage version [471632261] is not supported for read-only access. Error: Storage version [471632261] is not supported for read-only access.
Failed to open storage for read access. Storage: [Copia Diaria - 192.168.0.197D2020-08-13T204044_025E.vbk].
Failed to upload disk.
Shared memory connection was closed.
Failed to download disk 'vddkConnSpec>'.
Agent faild to process method {DataTransfer.SynsDisk}.

I tried to recovery a single file and got this:

Code: Select all

Storage version [-1111637298] is not supported for read-only access.
Failed to open storage for read access. Storage: [Copia Semanal - 192.168.0.197D2020-05-03T114247_88DE.vbk].
Failed to restore file from local backup. VFS link: [summary.xml]. Targe file: [MemFs://frontend::CDataTransferCommandSet::RestoreText_{7b0f0d49-4913.4414.a8b5-23a3524b47f9}] CHMOD mask: [0].
Agent faild to process method {DataTransfer.RestoreText}.

Also we try importing all backups directly to Veeam Backup & Replication, with same results. Also we tried directly with Veeam.Backup.Extractor.exe without luck.

There is any way to recover the system?

Our case number is: #04377231

Hope to find a solution. Thanks

[Andreas Neufert]

My guess is that the user do not have the rights on the file (windows rights) or the file is marked read only in the File extensions.

If this is urgent matter please change the support case severity to 1 so that our fast response team can help you.

[Natalia Lupacheva]

Hi Miguel,

I've moved your post to the thread with the discussions on the similar issue.
Please take a look at the suggestions here, might give you a hint.

Thanks!