2.6. LVM-VDO deployment scenarios
LVM-VDO can be deployed in various scenarios including KVM, file systems, iSCSI targets, and encryption configurations to provide deduplicated storage solutions.
You can deploy VDO on LVM (LVM-VDO) in a variety of ways to provide deduplicated storage for:
- block access
- file access
- local storage
- remote storage
Because LVM-VDO exposes its deduplicated storage as a regular logical volume (LV), you can use it with standard file systems, iSCSI and FC target drivers, or as unified storage.
- KVM
You can deploy LVM-VDO on a KVM server configured with Direct Attached Storage.
図2.1 LVM-VDO deployment with KVM
- File systems
You can create file systems on top of a VDO LV and expose them to NFS or CIFS users with the NFS server or Samba.
図2.2 LVM-VDO deployment with NAS
- iSCSI target
You can export the entirety of the VDO LV as an iSCSI target to remote iSCSI initiators.
図2.3 LVM-VDO deployment with block storage target
- Encryption
Device Mapper (DM) mechanisms such as DM Crypt are compatible with VDO. Encrypting VDO LV volumes helps ensure data security, and any file systems above the VDO LV are still deduplicated.
重要Applying the encryption layer above the VDO LV results in little if any data deduplication. Encryption makes duplicate blocks different before VDO can deduplicate them.
Always place the encryption layer below the VDO LV.
図2.4 LVM-VDO deployment with encryption