Skip to main content

This weekend happens an Issue on a Copy Job on immutable repository:

XX/XX/XXXX 01:02:07 :: Agent: Failed to process method {Transform.CompileFIB}: Input/output error

POSIX: Seek operation has failed. File: [/XXXX/backups/BACKUP_COPY_JOB_XXXX/BACKUP_JOB_XXXX/BACKUP_JOB_XXXX.vbk]. Distance to move: [504738922496]. Move method: [SEEK_SET].

 

XX/XX/XXXX 01:09:00 :: Unable to apply retention policy: failed to delete backup files Error: Input/output error

Failed to get file system object info: '/XXXX/backups/BACKUP_COPY_JOB_XXXX/BACKUP_JOB_XXXX/'

Agent failed to process method {FileSystem.Exists}.

 

Now I see the repository as Unavailable and if I try to rescan it and I receive the following warnings:

Failed to synchronize REPOXXXX Details: Input/output error Failed to get file system object info: 'XXXX/backups'. Agent failed to process method oFileSystem.Exists].

I can’t find any info about this specific issue. I’m investigating on repository system logs.

Regards

Hello,

Seems to have some problem to apply the retention policy. Do you have the right permissions for the service account? 
https://helpcenter.veeam.com/docs/backup/vsphere/hardened_repository_deploy.html?ver=110#step1

 

Hi Stabz, I’ve read something about the retention policy on the log error, I also thought of something due to retention of hardened repository that cannot delete file because locked, but it worked fine still last friday and why the repository become Unavailable?

Hi @fspadaro , the issue could came from a lot of things. I would recommend to check the server first if you have any hardware issue, after that you could check the Veeam Services. 
In any case if the problem persist you should open a ticket to the Veeam Support https://www.veeam.com/fr/support.html


Hello,
first of all, you are copying to or from immutable storage?

 

I would interpret the error message that the repo cannot be reached or that the filesystem is damaged. Are you able to read from this repo?


Hi @Stabz thanks. We have checked on the server and we have to remount the lun. Now we are analyzing the server’s logs.

Many thanks


 

Hello,
first of all, you are copying to or from immutable storage?

 

I would interpret the error message that the repo cannot be reached or that the filesystem is damaged. Are you able to read from this repo?

Hi I’m copying from and to hardened repo. I need to check the status of filesystem repo, the other repo (dfferent LUNs) seems to work fine; if I execute rescan, of these others, the output it’s ok.


Hello,

Seems to have some problem to apply the retention policy. Do you have the right permissions for the service account? 
https://helpcenter.veeam.com/docs/backup/vsphere/hardened_repository_deploy.html?ver=110#step1

 


Hello,

Seems to have some problem to apply the retention policy. Do you have the right permissions for the service account? 
https://helpcenter.veeam.com/docs/backup/vsphere/hardened_repository_deploy.html?ver=110#step1

 

Hi Stabz, I’ve read something about the retention policy on the log error, I also thought of something due to retention of hardened repository that cannot delete file because locked, but it worked fine still last friday and why the repository become Unavailable?


Hi @Stabz thanks. We have checked on the server and we have to remount the lun. Now we are analyzing the server’s logs.

Many thanks

Hello, no problem. Hoping that your server is up again !


Comment