Hi RGijsen,
If your goal is to restore using Robocopy, why not use the disk publishing feature?
You can mount any backed-up disk to a target system of your choice. The disk will be mounted read-only, with the same path as Windows Explorer would show: C:\VeeamFLR\
Best,
Fabian
-
- Product Manager
- Posts: 10619
- Liked: 2859 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Feature request - mount to console by default
Product Management Analyst @ Veeam Software
-
- Service Provider
- Posts: 507
- Liked: 123 times
- Joined: Apr 29, 2022 2:41 pm
- Full Name: Tim
- Contact:
Re: Feature request - mount to console by default
Well I'll definitely agree that not all changes are improvements, though I'll say the move to a web-interface increases compatibility, especially important now as Veeam is moving to running infrastructure on Windows and Linux, the Win32 console application is OS specific and as a result less compatible with potential user's existing infrastructure.
Regarding your scenario, I definitely agree that restore operation would be slow, any way you do it, and so I definitely understand you not wanting to use the built-in Veeam recovery functionality to transfer the data. This is a sort of situation I've mentioned in the past, the amount of effort it takes to access Veeam data. For your scenario using Robocopy, the Disk Publishing feature that Mildur mentioned sounds like it would be most applicable, but you can also check the Extract Utility, as that could be helpful for situations without the VBR server itself: https://helpcenter.veeam.com/docs/backu ... ml?ver=120
Regarding your scenario, I definitely agree that restore operation would be slow, any way you do it, and so I definitely understand you not wanting to use the built-in Veeam recovery functionality to transfer the data. This is a sort of situation I've mentioned in the past, the amount of effort it takes to access Veeam data. For your scenario using Robocopy, the Disk Publishing feature that Mildur mentioned sounds like it would be most applicable, but you can also check the Extract Utility, as that could be helpful for situations without the VBR server itself: https://helpcenter.veeam.com/docs/backu ... ml?ver=120
-
- Expert
- Posts: 133
- Liked: 31 times
- Joined: Oct 10, 2014 2:06 pm
- Contact:
Re: Feature request - mount to console by default
It sounds like the publish function might be what we need to use going forward. However, will that still be available in the new versions? I assume it will, as I guess things like transport roles and such will remain the same. But I'd like some confirmation on that.
-
- Product Manager
- Posts: 10619
- Liked: 2859 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Feature request - mount to console by default
Yes, the "disk publishing" feature will not go away. You can still do that in the upcoming release V13.
Best,
Fabian
Best,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: d.artzen, dmagoga, kevin.boddy and 27 guests