VEEAM 12.1 Error: Cannot find parent backup for child

[rpiercey]

Hi Veeam R&D Forum,

I recently upgraded a VEEAM install to V12.1 and ran into an issue that caused me to lose manageability of ~50% of my backups.

Process followed:
• Deployed 12.1 Upgrade
• Upgraded backup chains for all backups.
• Create new Backup Copy Job as required for one set of VMs.
• All Backup and copy jobs ran fine.
• Deployed a new hardened repository for Backup Jobs.
• Moved backup jobs to new repository - validated they all worked after moving.
• Validated backups are listed on new repository in VEEAM.
• Disabled and removed old repository.
• ~ 50 percent of my jobs failed: Error: Cannot find parent backup for child.
• The data for the failed backup job is no longer listed under Backups:Disk so I cannot restore from the files that exist on my repository.
• I also tried to import the backups from the repository and have received the same error.

Opened a Case #07070155

Response “ This is a known issues with how Veeam version 12.1 works with per-vm backups. We currently have two workaround to solve this issue.

1. Rename the metadata file for the job (.vbm) to .vbm_old. Only the extension of the file should be changed, After this is done, you will want to run an active full backup.
2. The other option is to clone the existing backup job and then be sure to not map the backup.”

In my case suggestion “1” didn’t resolve the issue and “2” is basically to re-create all the jobs which is what I wanted to avoid and it leaves the old backups not manageable.

I updated the support case, and the response was “Those are the current work arounds to this issue. I know that our R&D team is currently working on a fix for this issue, but it has not been released yet. If you like, I can put this case on hold until a solution from R&D is provided.”

I have recreated all my backup jobs and will have to manually remove the old backups after they expire.

VEEAM 12.1 Users may want to hold off on moving backups until VEEAM has a fix for this issue.

[PetrM]

Hi Reid,

Many thanks for sharing this information with us, I will discuss it with the team and will update the topic once I have more information about the private fix.

Thanks!

[PetrM]

@rpiercey The private fix is ready. Please ask your engineer to make sure that the issue that you're experiencing matches the one which is solved by the private fix and if it does, you may apply the fix.

Thanks!

[rpiercey]

Fix was installed and the issue has been corrected.

[squebel]

Getting this as well. Guess I'll be opening a case tomorrow and referencing this thread

[miti68]

Getting this as well
Where can i get the fix of is the fix in de last patch version
we are now on version 12.1.0.2131
i see there is a new version 12.1.1.56

[PetrM]

Hi Frank and Welcome to Veeam R&D Forums!

Please contact our support team and provide a support case ID as requested when you make a post about a technical issue. We cannot troubleshoot technical issues effectively over the forum posts. As mentioned above, the support team will check whether the issue that you're experiencing matches the one which is solved by the private fix and if it's true, they will give you the fix.

Also, please be aware that all posts about technical issues without case ID will be eventually deleted by the forum moderator. You can also upload debug logs for our support as per the instructions of this KB.

Thanks!

[kevlahau]

Can anyone confirm if the fix is incorporated into 12.1.1.56?

[PetrM]

Hi Kevin,

Yes, the fix is included in 12.1.1.56 code but please double-check with your support engineer that your issue matches the one discussed in this topic. The error message itself is quite generic and may occur for various reasons.

Thanks!

[kevlahau]

Thanks for the confirmation... I'm on 12.1.1.56 so I must have a different issue "Error: Invalid parent backup"