Enterprise Manager restore subfolders?

[Jonathan]

I'm sure I must be missing something, but I can't figure out why Enterprise Manager only restores the files inside a folder, but not subfolders. The backup machine holds a fresh Veeam 6.5 install, backups stored locally, I can select the relevant restore point, browse the VM's folder structure and click "Download". So far so good, but the result is a restore of the selected folder with files inside, but not the subfolders.

Any suggestions besides getting some more sleep?

[veremin]

The QA team has just confirmed the abovementioned behavior to be a bug. According to the plan, it is likely to be fixed in the upcoming release.

Thanks for the feedback; highly-appreciated.

[Jonathan]

Thanks Vladimir. Luckily we still have the regular Veeam console as a workaround.

[marc.rousseau]

Restoring subfolders is fixed in v7, but there's still a problem : size reported in summary count only files in folder not the total size of subfolders.
Our restore operators can be misleading

Is it possible to have a fix/patch for that ?

[Vitaliy S.]

Hi Marc,

Our support team mostly drives the process for a fix/patch based on the opened tickets and the amount of these tickets. BTW, are you referring to display information which is not accurate or something else?

Thanks!

[marc.rousseau]

Hi Vitally,

Just a simple example:

folder
+----- file1 (1Mb)
+----- file2 (1Mb)
+----- subfolder
----------+---file3 (1Mb)
----------+---file4 (1Mb)

I launch a 1-Click FLR restore operation on "folder".
When 1-Click FLR operation is completed, files and subfolders are successfully restored, but Enterprise manager reports only "2Mb restored" (files in root folder: file1 and file2) which is wrong : 4Mb has been restored (files and subfolders files)

I think I should open a ticket for that, but if you can transmit this information to dev team, it could be great.

Thanks
Marc

[veremin]

I will pass this information to the team tomorrow, once I'm in the office. Let's wait and see what they say about it. Thanks.

[veremin]

QA team has confirmed this to be a bug. According to the plan, it will be fixed in the next release. Thanks.

[marc.rousseau]

Thank you for your quick answer.
When is planned the next release/patch ?

[veremin]

Currently, there is no ETA. Thanks.