Veeam Data Platform
Cloud AWS | Azure | Google | IBM | Kubernetes
Virtual VMware | Hyper-V | Nutanix AHV | RHV
Physical Windows | Linux | MacOS | Unix | NAS
Apps Microsoft | Oracle | SAP Hana | PostgreSQL
SaaS Microsoft 365 | Salesforce
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Please try again later.
When restoring via Direct SAN, disks must be restored as Thick, either lazy zeroed or eager zeroed. Performance has been shown to be much higher when using the eager zeroed option1.
On the Datastore tab of the Full VM Restore wizard, use the Disk Type button in the bottom-right corner to set the restored disk type to "Thick (eager zeroed)."
On the Disk Mapping tab of the Virtual Disk Restore wizard, use the Restored disk type dropdown box to select "Thick (eager zeroed)."
If you'd prefer to restore the disk as Thick (lazy zeroed), performance can be improved by using the "Picky proxy to use" option in the Full VM Restore and Virtual Disk Restore wizards to select either a proxy that does not have Direct SAN capability or a proxy that has been manually configured to use either Virtual Appliance or Network transport mode.
Additionally, simply selecting the disk type Thin will force the restore to use any other transport mode because Direct SAN cannot restore disks as Thin provisioned.
Your feedback has been received and will be reviewed.
Please try select less.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case