Source backup job has encryption enabled, warnig

[Marten_med_e]

This is a new one for me. This happens when I add this VM to a new backup copy job. Support case ID# 00941923



But the source isn't encrypted never has.



Cheers

[foggy]

Any chance this VM is also backed up by some other backup job that has encryption enabled?

[Marten_med_e]

Any chance this VM is also backed up by some other backup job that has encryption enabled?

This VM is in several other backup jobs, one that takes a backup of the whole server with all six disks, and in five backup jobs that only has one disk selected, but none of the jobs have or has had encryption enabled.

I did a small test, I have some backup jobs with encryption enabled on, so first one job with encryption enabled
1. Disable backup job
2. Delete backup files from backup
3. Rescan repository
4. Backup files appears in the folder "Encrypted" and I have to enter the password for the files to "move" to the "Disk (imported)" folder
5. Edit/map backup job to the backup files

And when I do this with the files/job from the picture this is the result
1. Disable backup job
2. Delete backup files from backup
3. Rescan repository
4. Backup files appears in the folder "Disk (imported)"
5. Edit/map backup job to the backup files

Yes I did forget to map the backup job once and the job started a full backup in a new folder "1-Backup Job STOFS02_Tidningen_1", BUT this is where it gets strange, I did stop that job and mapped the backup job to the right folder. I did run the backup job and it picked up the files and created a incremental backup, I tried to restore some files from that backup to see that it still works. So no problem and when I for the (feels like the hundredth time) recreated the backup copy job I didn't get the "Source backup job has encryption enabled" warning. I did both the "local" and "cloud" copy jobs without getting this warning.

Will try this with one of the other problematic jobs later to night, when wife and kids are sleeping, to see if I can replicate the result.

Cheers

[Marten_med_e]

Ok, lets see

I can now re-create the error, see the steps below.

1. Create a new backup job, chose a VM or two
2. Chose Backup mode "Reverse incremental"
3. Run the backup job twice, to create a full and a rollback file
4. Create a new Backup copy job
5. Chose to use "Objects to process, from backups" and chose the backup job created in step one
6. And the warning appears



Cheers

[veremin]

Just to clarify - you're concerned with the fact that in case forward incremental mode being used by source job, you don't get notified about source job encryption?

[Marten_med_e]

No, the other way around, if I make an unencrypted Reverse incremental backup job, then after the first and second run, so I got one vbk and one vrb file in the folder, make a backup copy job and chose "Objects to process, from backups" and chose the backup job I get the warning.

Cheers

[veremin]

Since the source job doesn't have encryption enabled, the described behaviour looks unexpected. Feel free to reach the support with that problem. Thanks.

[Marten_med_e]

There is already an open support case on this, but right now I have some problems to convincing the support tech that the source job never has been encrypted, just running in reverse incremental mode. But I made some clarifications in the case today. Going to link this thread to the support case also.

Cheers

[Marten_med_e]

Case is escalated, will see what the Webex session will reveal.

Cheers

[veremin]

May I ask you to provide case number for the convenience of future readers?

[Marten_med_e]

This is a new one for me. This happens when I add this VM to a new backup copy job. Support case ID# 00941923

Cheers

Support case ID is in first post as forum rules requires


Cheers

[veremin]

My bad, I must have missed it. At least now I can see it.

[Marten_med_e]

So, back from a nice tree day weekend without internet connection, yes, we can survive that, or I can.

But back to reality, Veeam Support confirmed this being a "GUI" bug, I will try to explain it. Alexander (foggy) was right on the right track,

Any chance this VM is also backed up by some other backup job that has encryption enabled?

Yes, the VMs are encrypted in the Cloud repository, so the Backup Copy job wizard, don't filter out the Cloud repository from the source repository list, visually it does that, but even though I specifically chose to use only the selected local repository it warns about the source being encrypted, but only when the local source backup job is Reverse incremental backup mode.



Status right now on this case is, "Awaiting Fix Availability" and as this is a pure GUI bug I was told that it was not certain that a HotFix would make it before the realese of Veeam 9.

Cheers

[veremin]

Thank you, Mårten, for coming back and updating the topic with the explanation regarding the root cause of the said problem; highly appreciated. Thanks.

[hyvokar]

Just run into a same problem.

Any chance this would be fixed?