collecting recovery media files fails

[mcz]

Hi everybody,

very often, many clients exit their backups with a warning: "Collecting recovery media files Details: Windows recovery image file not found"

Any ideas about it? Thanks!

[Gostev]

Hello, as requested when you click New Topic, please do not include log snippets in the forum posts. Instead, please open a support case with full debug log package included, and include the support case ID. Thanks!

[mcz]

Hi Anton, thanks for the reply. May I ask for the reason why I shouldn't post log snippets? Wasn't able to find a explanation in the FAQ's...

[PTide]

May I ask for the reason why I shouldn't post log snippets

Because although support team occasionally monitors this forum too, they will analyse logs only if you contact them directly and upload the complete log bundle to the dedicated ftp. That is, there is no point in posting snippets as they will only trash the forum.

Thank you

[mcz]

case # is 02461474

[mcz]

Ok it looks like that adk was missing on the affected machines and support wasn't able to tell me why adk is missing on some machines. I was also told that veeam doesn't install adk during deployment of the agents so I would call it a feature request to automatically install adk during agent deployment - thanks!

[Dima P.]

Michael,

Thanks for sharing. Last time I checked ADK components were ~3GB size. We decided not to push them automatically and, instead, recommend to install them only when it’s really required.

[mcz]

Yeah my latest download also has 3 GB but you won't get any recovery media on certain machines without it. I agree that it's a big package and doesn't make sense to integrate into the VAW installer but probably agents could automatically deploy adk when recovery media build fails. Or you could integrate a functionality within B&R console which would let you deploy adk via context menu. What do you think?

[mcz]

Just for clarification: Support told me that ADK is not needed per default but it fixes some broken windows components which are used for building the recovery media...

[Dima P.]

Michael,

Just for clarification: Support told me that ADK is not needed per default but it fixes some broken windows components which are used for building the recovery media...

True. Thanks for your feedback – we will discuss it with development team.

[davidinmemphis]

I'm experiencing this problem currently with one of my machines. I'm confused about the whole ADK installation solution.

Do I need to install the ADK on the target computer, or on the Veeam B&R console or...what?

[mcz]

Hi davidinmemphis,

you have to install ADB on the target machine. You can also install it via CLI or psexec remotely.

https://docs.microsoft.com/en-us/window ... ne-install

[ValiantMartian]

I have a few machines that error with "Collecting recovery media files: Windows recovery image file not found." Is there any way to NOT generate an error for machines that are hitting that? This is making it look like the machine backup failed, when really, the 'normal' file system is backed up fine.

[HannesK]

Hello,
instead of suppressing a valid warning, I suggest to fix the issue. If the hints from above don't work, support is available for help (please post the case number for reference)

Best regards,
Hannes

[edison5000]

We are also having this same problem. While this systems might somehow be missing components for the recovery image / pe to work, this was not a necessary use case for us to use Veeam. Pushing out the missing components to every system that is missing them (for whatever reason) seems unnecessary if, as ValiantMartian suggested, we could just disable this warning.