Article ID: 54465
Article Type: Troubleshooting
Last Modified:
For VMware backups that use Indexing Version 2 and an incremental storage policy, backups for some VMs fail during the archive indexing stage.
For VMware incremental backups and differential backups that use Indexing Version 2 and an incremental storage policy, backups of subclients that include newly discovered VMs fail during the archive indexing stage.
For incremental and differential backups, this issue can occur from Service Pack 14 through Feature Release 11.22.
Newly discovered VMs are skipped for incremental and differential backups, and then the backups are converted to full backups for those VMs. The child jobs for those VMs fail during the archive indexing stage, and both the parent and child jobs are left in a Waiting state.
The vsbkp.log file contains this error:
Error while backing up VM [vm_name], skipping the VM for this attempt
The LogManager.log file contains this error:
Error while Handling ArchiveMessage
ErrNo.22.(Invalid argument)-Backup Object failed to initialize
This issue occurs for a virtualization client with Indexing Version 2 enabled when you perform an incremental or differential backup operation for a subclient that uses an incremental storage policy. The incremental storage policy is used for the parent backup job and for the child backup jobs for each VM.
If the backup discovers new VMs that have not yet been backed up, those VMs are initially skipped, and then the backups for those VMs are converted to full backups. However, when the backup operation attempts to perform an archive index operation for the full backups, the operation cannot find the correct storage policy, and the archive index operation fails.