Since upgrade to v12.3 getting "Sequence contains no matching element"

[JPMS]

When backing up Windows Agent backups to tape from repo, they all failed with "Sequence contains no matching element".

This is our first tape backup since upgrading to v12.3 and has always worked without issue previously with v12.2.

Anybody else seeing this?

Case #07532632

[JPMS]

Worse than I originally thought. Getting this error backing up any backup job to tape.

Only thing working is file to tape.

[Dima P.]

Hello JPMS,

Thank you for your post. Checking with QA team!

[JPMS]

Got this resolved but following up for anybody who has the same issue. I also think this needs referring back to the developers because the way they have implemented this new feature makes no sense!

My understanding is that v12.3 introduces a new check that checks agent backups for "encrypted vbk and non-encrypted vbk in the same source backup" and generates this error if there is. (I have no idea why this check was introduced, presumably to resolve some issue that users experienced.)

As the problematic agent backup was a backup to repo, it would be unencrypted and always would have been so I don't know why it threw an error. We made no attempt to diagnose this. I just orphaned the existing backups for that agent, did a new backup and then the backup to tape worked.

The backup to tape job we were running consisted of the backup job of all our servers and 6 agent backups. There are two things that have really annoyed me about this and why I think it should be referred back to the developers:

• The error message should be something meaningful with a knowledge base article so people can resolve the problem themselves.

• It makes no sense to fail the whole backup job for a problem with one of the agents, it should just fail the B2T for that one agent backup and complete the rest of the job. What it does at the moment prevented us doing B2T backups for our critical infrastructure for the sake of an issue with a relatively unimportant agent backup.

[Dima P.]

Hello JPMS,

This check has been implemented, indeed, to avoid issues with backup decryption caused by different state stored in the backup metadata. Thank you for the feedback, we will improve the user experience around this issue!