Solved

Error Unexpected meta file size with nfs datastore

1 year ago
January 4, 2024
7 comments
551 views

flipflip
Comes here often
10 comments

Hello,

With Veeam Backup & Replication Community Edition 11, On one of the backup jobs, when it starts, I encounter the following error:

Failed to perform health check Error: Agent: Failed to process method {NasMaster.TransformMeta}: Unexpected meta file size 348160. Expected size: 356352.

The source is an NFS share stored on a NetApp storage, and the destination is a Synology NAS. I have other jobs that use the same sources and the same destination, and they do not encounter this error.

The job is responsible for backing up user files such as Office documents, PDFs, etc. When it runs, no files are open or currently being modified.

I tried performing a job check as instructed on this page https://helpcenter.veeam.com/archive/backup/110/vsphere/health_check_nas_backup.html, but I encounter the same error.

Thank's for advance.

Philippe

Best answer by Chris.Childerhose

You can also start a new chain as per here too - Starting New Backup Chain - User Guide for VMware vSphere (veeam.com)

View original

Did this topic help you find an answer to your question?

+23

MicoolPaul
2403 comments
1 year ago
January 4, 2024

Hi Philippe, this is actually the health check reporting an issue. Your metadata file isn’t the expected size meaning it’s corrupt. How do you access your Synology NAS? SMB/NFS/iSCSI?

Michael Paul - Opinions are my own and do not necessarily reflect the opinion of Veeam | https://micoolpaul.com | Mastodon: @micoolpaul@masto.nu | Bluesky: @micoolpaul.com

flipflip
Author
Comes here often
10 comments
1 year ago
January 4, 2024

Hello,

access to the Synology NAS is via NFS in v3.

I have other jobs that use the same source (but a different NFS share) and the same destination, and they do not encounter any issues.

+21

Chris.Childerhose
Veeam Legend, Veeam Vanguard
9300 comments
1 year ago
January 4, 2024

But as stated this is the health check showing you corruption. Whatever job this metadata file references I would run an active full backup to create a new chain to see if that fixes the issue.

flipflip
Author
Comes here often
10 comments
1 year ago
January 4, 2024

Unfortunately, this option is only available for VM backup jobs and not for files. Or maybe I haven't found where the option is located :(

+21

Chris.Childerhose
Veeam Legend, Veeam Vanguard
9300 comments
1 year ago
January 4, 2024

Try running the File Repair option from here for your file backups - Performing Health Check and Repair for Unstructured Data Backups - User Guide for VMware vSphere (veeam.com)

This shows the health check and if it finds issues what to do. This might be the way to repair file backups versus running a job.

+21

Chris.Childerhose
Veeam Legend, Veeam Vanguard
9300 comments
Answer
1 year ago
January 4, 2024

You can also start a new chain as per here too - Starting New Backup Chain - User Guide for VMware vSphere (veeam.com)

flipflip
Author
Comes here often
10 comments
1 year ago
January 11, 2024

Hello, it’s ok with this link : Error Unexpected meta file size with nfs datastore

Thank‘s

Hello,

With Veeam Backup & Replication Community Edition 11, On one of the backup jobs, when it starts, I encounter the following error:

Failed to perform health check Error: Agent: Failed to process method {NasMaster.TransformMeta}: Unexpected meta file size 348160. Expected size: 356352.

The job is responsible for backing up user files such as Office documents, PDFs, etc. When it runs, no files are open or currently being modified.

I tried performing a job check as instructed on this page https://helpcenter.veeam.com/archive/backup/110/vsphere/health_check_nas_backup.html, but I encounter the same error.

Thank's for advance.

Philippe

Page 1 / 1

Hi Philippe, this is actually the health check reporting an issue. Your metadata file isn’t the expected size meaning it’s corrupt. How do you access your Synology NAS? SMB/NFS/iSCSI?

Hello,

access to the Synology NAS is via NFS in v3.

I have other jobs that use the same source (but a different NFS share) and the same destination, and they do not encounter any issues.

But as stated this is the health check showing you corruption. Whatever job this metadata file references I would run an active full backup to create a new chain to see if that fixes the issue.

Unfortunately, this option is only available for VM backup jobs and not for files. Or maybe I haven't found where the option is located :(

Try running the File Repair option from here for your file backups - Performing Health Check and Repair for Unstructured Data Backups - User Guide for VMware vSphere (veeam.com)

This shows the health check and if it finds issues what to do. This might be the way to repair file backups versus running a job.

You can also start a new chain as per here too - Starting New Backup Chain - User Guide for VMware vSphere (veeam.com)

Hello, it’s ok with this link : Error Unexpected meta file size with nfs datastore

Thank‘s

Comment

Rich Text Editor, editor1

Comment

Related topics

Proxmox - Failed to reach the hypervisor. Error output: sh: 1: Syntax error: "(" unexpectedicon

Error: Failed to call RPC function 'FcReadFileEx': An unexpected network error occurred. Failed to read data from fileicon

Veeam B&R Suddenly loses connection to NFS repositoryicon

Automate Instant Disk Recovery using the new FCD Restore API

File not found (cannot open storage locationicon

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded