Windows Native File Level Restore Total Amount of Disks Limit
| KB ID: | 1772 |
| Product: | Veeam Backup & Replication |
| Version: | 6.5, 7.x, 8.x |
| Published: | 2013-06-20 |
| Last Modified: | 2020-08-13 |
Challenge
File level restore fails, or displays fewer disks than expected.
Cause
Windows File Level Restore is limited to displaying 20 virtual disks. Multi-OS File Level Restore is limited to browsing VMs with 16 virtual disks.
Solution
You can use VM Hard Disk Restore or VM Files restore to restore only those disks that contain data needing to be restored, and attach those disks to a VM in order to retrieve files. You can also use Instant Recovery to restore the entire VM.
Note: For Veeam Backup & Replication 8.x use the following registry value to increase the limit for Windows File Level Restore:
Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
DWORD: VdkMaxDisksNum
Default value: 20 (decimal)
Max Value: 128
Set the value to a number greater than the largest number of disks on any of the VMs in your environment.
Please keep in mind that attempting to perform an FLR with from a VM with a large amount of disks may take a very long time.
Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
DWORD: VdkMaxDisksNum
Default value: 20 (decimal)
Max Value: 128
Set the value to a number greater than the largest number of disks on any of the VMs in your environment.
Please keep in mind that attempting to perform an FLR with from a VM with a large amount of disks may take a very long time.
More information
| KB ID: | 1772 |
| Product: | Veeam Backup & Replication |
| Version: | 6.5, 7.x, 8.x |
| Published: | 2013-06-20 |
| Last Modified: | 2020-08-13 |
Couldn't find what you were looking for?
Below you can submit an idea for a new knowledge base article.
Report a typo on this page:
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Spelling error in text
Knowledge base content request
