Solved Question About Veeam Endpoint Protection Recovery Media
-
Note the highlighted section. This is what embeds the drivers in the ISO, they are checked by default. Also note, I selected to make an image file.
Specify the location for the image file. I use a network share, but you can easily put it on the C drive temporarily and copy it off after the process is done.
Confirm what you picked.
Watch it complete.
-
Looks like you could add the network drivers for most if not all of your systems so a single restore image could work for them all.
A bit more work, but only having to hang onto one disk, kinda nice.
-
@Dashrender said:
Looks like you could add the network drives for most if not all of your systems so a single restore image could work for them all.
A bit more work, but only having to hang onto one disk, kinda nice.
I assume you meant drivers?
-
@JaredBusch said:
@Dashrender said:
Looks like you could add the network drives for most if not all of your systems so a single restore image could work for them all.
A bit more work, but only having to hang onto one disk, kinda nice.
I assume you meant drivers?
yes, corrected.
-
@Dashrender said:
Looks like you could add the network drivers for most if not all of your systems so a single restore image could work for them all.
A bit more work, but only having to hang onto one disk, kinda nice.
No, i think you have to create for each system his own image, when you have issue with machine x, go and find the image x and boot from it (make bootable USB based on this image)
-
@IT-ADMIN said:
@Dashrender said:
Looks like you could add the network drivers for most if not all of your systems so a single restore image could work for them all.
A bit more work, but only having to hang onto one disk, kinda nice.
No, i think you have to create for each system his own image, when you have issue with machine x, go and find the image x and boot from it (make bootable USB based on this image)
No, look at my first screenshot. there is a checkbox there to let you include MORE drivers. If you do this, you could easily have a single ISO image that would work on all your devices.
-
@JaredBusch said:
@IT-ADMIN said:
@Dashrender said:
Looks like you could add the network drivers for most if not all of your systems so a single restore image could work for them all.
A bit more work, but only having to hang onto one disk, kinda nice.
No, i think you have to create for each system his own image, when you have issue with machine x, go and find the image x and boot from it (make bootable USB based on this image)
No, look at my first screenshot. there is a checkbox there to let you include MORE drivers. If you do this, you could easily have a single ISO image that would work on all your devices.
do you mean the third checkbox ??
-
@IT-ADMIN said:
@JaredBusch said:
@IT-ADMIN said:
@Dashrender said:
Looks like you could add the network drivers for most if not all of your systems so a single restore image could work for them all.
A bit more work, but only having to hang onto one disk, kinda nice.
No, i think you have to create for each system his own image, when you have issue with machine x, go and find the image x and boot from it (make bootable USB based on this image)
No, look at my first screenshot. there is a checkbox there to let you include MORE drivers. If you do this, you could easily have a single ISO image that would work on all your devices.
do you mean the third checkbox ??
yes
-
i see it now, but do you think it is safe to boot all of your machines from one image that has multiple drivers, is that the best practice
i think if you have an image for each machine is safe and smooth, what do you think ?? -
@IT-ADMIN said:
i see it now, but do you think it is safe to boot all of your machines from one image that has multiple drivers, is that the best practice
i think if you have an image for each machine is safe and smooth, what do you think ??As we said before. if your hardware is all similar, then it really should not matter.
Please remember, the point of this image, is simply to boot the hardware far enough to provide network connectivity and allow the Veeam software to pull the backup back down onto the hardware. It is not designed to have all functions for the hardware.
-
@IT-ADMIN said:
i see it now, but do you think it is safe to boot all of your machines from one image that has multiple drivers, is that the best practice
i think if you have an image for each machine is safe and smooth, what do you think ??
Why do you feel that it would not be a best practice to have a single image with all of the necessary drivers? What downside are you proposing this has?
-
@scottalanmiller said:
@IT-ADMIN said:
i see it now, but do you think it is safe to boot all of your machines from one image that has multiple drivers, is that the best practice
i think if you have an image for each machine is safe and smooth, what do you think ??
Why do you feel that it would not be a best practice to have a single image with all of the necessary drivers? What downside are you proposing this has?
i don't know, the idea of having multiple drivers in one image make me thinking that this may cause driver issues or incompatibility (by mistake pulling driver x instead of driver y) i'm just talking
-
@IT-ADMIN said:
i don't know, the idea of having multiple drivers in one image make me thinking that this may cause driver issues or incompatibility (by mistake pulling driver x instead of driver y) i'm just talking
But that is how every OS works. Thousands and thousands of drivers in the base install image. You don't worry about Windows, Linux or Mac when you install them, right?
-
yeah it is true, it was just a wrong thought
-
Hi folks,
Its recommended to keep the recovery media per OS (32-bit and 64-bit) just because of the drivers, but:
- You can include additional drivers to recovery media during creation
- You can disable drivers collection from the OS during creation
- You can load the drivers while performing the Bare Metal Recovery
- You can disable the collected drivers being injected from Recovery Media during recovery
-
@angrydok said:
Hi folks,
Its recommended to keep the recovery media per OS (32-bit and 64-bit) just because of the drivers, but:
- You can include additional drivers to recovery media during creation
- You can disable drivers collection from the OS during creation
- You can load the drivers while performing the Bare Metal Recovery
- You can disable the collected drivers being injected from Recovery Media during recovery
it looks like my idea was correct
-
Which idea is that?
-
I have a suspicion that you are completely misreading what that quote says. It very clearly says that you should NOT have lots of images, only one (because it is not recommended to have multiple OSes or architectures.) It shows that you were mistaken and should have just one 64bit image and put all of the drivers on it.
-
@IT-ADMIN Iād say two images x32 and x64 without any drivers included - minimum. You have to manually upload the drivers (and install them) during bare metal recovery then. However, thats not a big issue if you are using the USB stick - you can just drag and drop the storage and network drivers to any folder inside the recovery media.
BTW we had some discussions on the forums check for creative workarounds: http://forums.veeam.com/veeam-endpoint-backup-f33/multiple-computer-recovery-media-on-single-usb-t29636.html?hilit=unified
-
Is 32-bit Windows still be deployed? It seems like that would have gone away when Windows XP did.
