Overview - vmPRO Global Block Diagram
This diagram gives you a high level schematic view of the different components of the vmPRO product and how the components fit in together. The diagram represents data flow as of version 3.0. For version 2.3.x, the data is slightly different, which is described below the diagram.

For version 2.3.x, the data is slightly different in the following ways:
- Recover wizard copies directly from network storage to import_fs before 3.0, and will not take advantage of SmartRead and merging done by recovery_fs.
- files_fs opens its own set of loop device and device mapper on top of /export before 3.0, which affects performance. In 3.0, files_fs shares the loop device/device mapper created by vm_proxy_fs whenever possible.
- export_fs uses the loop device and device mapper for most of the data movement from datastore_fs before 3.0. In 3.0, it only uses the loop device and device mapper for getting live block map, most of the data movement uses a direct file handle on datastore_fs to improve performance.
- recovery_fs uses the loop device and device mapper on top of the network storage to merge the pancbt file with the flat file. In 3.0, it only uses loop device and device mapper for getting the live block map, the data merger uses direct file handles to improve performance.
What's Next?
vmPRO Components >