Error: Failed to synchronize encrypted entities

[lukasz]

Hi,

I've just configured backup on tape as a secondary destination
Yesterday inicial Full Backup was completed without any problems. After that, during the night, incremental backup was made without any problems too.
Today I see error on this job, from 4:00 am on every hour:
Error: Failed to synchronize encrypted entities

I have shedule for GFS daily scan at 4am so I think this is it but I don't understand the error and I can't even google it.

[Egor Yakovlev]

Hi there, Lukasz

Try cloning the tape job and disabling original one. See if that helps.

/Thanks!

[lukasz]

I've made a clone and it's working but i think the problem will come back at 4am when gfs daily scan will start again.
Full and incremental is working on the old one too

[Egor Yakovlev]

Good to hear it is working.
Please do update this thread with results tomorrow after GFS proccessing - I am eager to hear if issue persists or not.
/Thanks!

[jma89]

Just thought I'd pop in to say that we saw the same error on one of our tape jobs. It started on the 17th of this month, and I was able to resolve it by cloning the job and running the clone. (We run tape jobs weekly on Saturday night, and we are not using GFS retention policies.)

More details: The primary log would show "Failed to synchronize encrypted entities", but the servers within the job would just show "Task failed unexpectedly". The job would only run for 5-7 seconds before failing. This particular server is running on 10.0.0.4461 P2, and it's the only one in our environment to have this problem. (We have 6 Veeam B&R servers, and 4 of them use the same model tape library and setup as this server.)

[Dima P.]

Hello folks,

The issue is being investigated by our QA team. Please if you see the same error - raise a support case and share the id with us, as we need more debug logs to understand the root cause. Thank you!

[gideon pelser]

Good afternoon everyone,

I have just encountered the same issue and the cloned job worked successfully. A case has been logged with reference #04506696. I have uploaded all the relevant logs and hopefully it will assist in having this resolved.

[Dima P.]

Hello Gideon,

Thanks for updating the thread and sharing your case ID. Passed it to QA folks. Cheers!

[dsegel]

Hi - I just got this error this morning and cloning seems to have helped. Do you still want people to submit a case for it?

[Dima P.]

Hello Daniel,

Yes, please, and do not forget to share the case ID! The issue is still under investigation by our QA team. Thanks!