Virtual Data Optimizer (VDO)
In this section, you can find information on how to enable deduplication using basically any block storage available. We assume that you have prepared your storage provider and have exposed the block device to the system where vPlus Node is installed.
Preparation
Note. Disable Secure Boot option for the VM to allow VDO work properly. Run below command to check status of Secure Boot option:
Log in to vPlus Node and create a mount directory as in the example
/backupdestination
List all existing disks, and find your drive. Let's assume
/dev/sdc
is your empty block device that you want to use:Log in to the vProtect web UI.
Go to Backup Destinations.
Click on Create Backup Destination, choose a File system.
Type the name for the new backup destination, set the retention, and select at least one node configuration.
Based on whether the staging space is same as backup destination or not, do one of the following:
If the staging space is different from your backup destination storage:
In Storage paths type
/backupdestination
- this path will be used to mount the prepared file system (XFS) on top of the VDO volume.Check Enable deduplication.
Provide your block device (for example
/dev/sdc
) as your Deduplication device.
If the staging space needs to be the same as your backup destination storage:
In Storage paths type
/vprotect_data/backups
- this path assumes that/vprotect_data
is your staging space path andbackups
is a subdirectory of the staging space.Check Enable deduplication.
Provide your block device (for example
/dev/sdc
) as your Deduplication device.Enable Mount deduplicated file system to a different directory than backup destination path and provide the mount point - your staging space path, for example
/vprotect_data
- this will force vPlus to mount XFS on top of VDO in the staging space directory rather than in the backup subdirectory.
Note. Only one file system backup destination with deduplication using VDO pointing to a specific directory can be used. If you want to add another backup destination using the same VDO device, but just a different subdirectory, create it without deduplication enabled.
Importing existing VDO volumes to LVM
The Python-based VDO management software has been deprecated and removed from RHEL 9/CentOS 9 Stream. It has been replaced by the LVM-VDO integration. If you are using VDO on RHEL 8/CentOS 8 Stream and plan to upgrade to version 9, you need to convert VDO volume.
In this example we have VDO volume called VDOexample created and managed by vPlus.
On vPlus Node, stop vprotect-node service.
Unmount VDO volume from backup destination path.
Convert VDO volume. Change
/dev/sdb
to the device on which you have created VDO.Rename volume group and logical volume names. They must be the same as the original VDO volume name.
Edit /etc/yum.repos.d/vProtect.repo and change
baseurl
to point toel9
.On vPlus Server machine, create a vprotect database backup and copy it to safe place. Wait for all tasks to finish before stopping the vprotect-server service.
Login to mysql and execute below SQL query.
Start vprotect-server service.
Proceed with the system upgrade of the vPlus Node machine. After the reboot, you should have new LVM-VDO mounted on your backupdestination directory.
Last updated