1st Annual Veeam Community Hackathon
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 errorPOSIX: 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 errorFailed 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 [FileSystem.Exists].I can’t find any info about this specific issue. I’m investigating on repository system logs.Regards
Hello everyone, it’s correct that concurrent tasks limit on the following repositories depend on the hardware (CPU/RAM) of the gateway server (transport server):DataDomain connected in FC to gateway servers with 16 cores and 32GB RAM Immutable on Linux servers with 16 cores and 32GB RAMConcurrent tasks are 32 or 16VMs as reported in the following documentation:Limitation of Concurrent Tasks - User Guide for VMware vSphere (veeam.com) NOTE Task limits set for backup infrastructure components influence the job performance. For example, you add a VM with 4 disks to a job and assign a backup proxy that can process maximum 2 tasks concurrently for the job. In this case, Veeam Backup & Replication will create 4 tasks (1 task per each VM disk) and start processing 2 tasks in parallel. The other 2 tasks will be pending. ThanksFederico
Hi to all,I try to understand the behavior of my lab jobs.I have a backup jobs (of one VM) with the following settings:Scheduled: every days at 22:00Retention: 7 daysSynthetic Full: SaturdayGFS: 12M, 5YRepository: Hardened for 7 daysenabled a secondary copy to backup copy job with following settings:Scheduled: every days at 08:00Retention: 7 daysGFS: 12M, 5YRepository: Deduplicate storageOn backup jobs all work fine but on backup copy jobs appears only the first full (example of today) and then all incremental until the end of June and at 30 June has copied (created) a full backup (MY) not deleting any of the previous backups.Restore point Repository
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
