KB10022 How to create VDO volume on multiple disk devices

📚

Documentation

Installation guides, configuration steps, and product documentation.

Explore documentation →

🎧

Support

Create a support request or review your existing cases.

Go to support →

⬇️

Download trial

Download the product trial and try it out.

View downloads →

KB10022 How to create VDO volume on multiple disk devices

KB ID: 10022

Product: vProtect

Version: 4.0.0 +

Published: 2021-02-25

Last modified: 2021-02-25

Problem

How to prepare a machine with a vProtect node to create a file system backup destination (with deduplication) on multiple disk devices.

Note: If you have a single block device, there is no need to prepare OS


Let assume that you have a VM (or bare metal, there is no difference) machine with 4 disks.


Hard disk 1 is for the operating system, disks from 2 to 4 are for backup destination.

You want to have a single backup destination with the sum of available disk space.

Solution

vProtect use a build-in deduplication feature into CentOS/RHEL operating systems - VDO.

Because VDO requires a singular device in the creation process, we need to create an LVM logical volume on our three disks.


Check disks available on the machine

Use lsblk command

[root@localhost ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 16G 0 disk ├─sda1 8:1 0 1G 0 part /boot └─sda2 8:2 0 15G 0 part ├─rhel-root 253:0 0 13.4G 0 lvm / └─rhel-swap 253:1 0 1.6G 0 lvm [SWAP] sdb 8:16 0 20G 0 disk sdc 8:32 0 20G 0 disk sdd 8:48 0 20G 0 disk sr0 11:0 1 1024M 0 rom


Initializing Physical Volumes
Use the pvcreate command to initialize a block device to be used as a physical volume. Initialization is analogous to formatting a file system.
The following command initializes/dev/sdb,/dev/sdc, and /dev/sdd as LVM physical volumes for later use as part of LVM logical volumes.

[root@localhost ~]# pvcreate /dev/sdb /dev/sdc /dev/sdd Physical volume "/dev/sdb" successfully created. Physical volume "/dev/sdc" successfully created. Physical volume "/dev/sdd" successfully created.


Check physical volumes available for lvm

[root@localhost ~]# pvs PV VG Fmt Attr PSize PFree /dev/sda2 rhel lvm2 a-- <15.00g 0 /dev/sdb lvm2 --- 20.00g 20.00g /dev/sdc lvm2 --- 20.00g 20.00g /dev/sdd lvm2 --- 20.00g 20.00g


Initializing Volume Group
Now we need to create a volume group using our three physical volumes

[root@localhost ~]# vgcreate vg4vdo /dev/sdb /dev/sdc /dev/sdd Volume group "vg4vdo" successfully created


Initializing Logical Volume
In the last step, we will create a logical volume and thanks to that we will have the block device/dev/mapper/vg4vdo-lvm4vdo (this is what we need for a later configuration in vProtect)
The following command creates a logical volume called lvm4vdo that uses all of the unallocated space in the volume group vg4vdo

[root@localhost ~]# lvcreate -v -l 100%VG -n lvm4vdo vg4vdo Converted 100% of VG (15357) extents into 15357 (with mimages 1 and stripes 1 for segtype striped). Archiving volume group "vg4vdo" metadata (seqno 1). Creating logical volume lvm4vdo Creating volume group backup "/etc/lvm/backup/vg4vdo" (seqno 2). Activating logical volume vg4vdo/lvm4vdo. activation/volume_list configuration setting not defined: Checking only host tags for vg4vdo/lvm4vdo. Creating vg4vdo-lvm4vdo Loading table for vg4vdo-lvm4vdo (253:2). Resuming vg4vdo-lvm4vdo (253:2). Wiping known signatures on logical volume "vg4vdo/lvm4vdo" Initializing 4.00 KiB of logical volume "vg4vdo/lvm4vdo" with value 0. Logical volume "lvm4vdo" created.


To be 100% sure, check if there is a block device

[root@localhost ~]# ls -l /dev/mapper/vg4vdo-lvm4vdo lrwxrwxrwx. 1 root root 7 Feb 25 16:10 /dev/mapper/vg4vdo-lvm4vdo -> ../dm-2

/dev/mapper/vg4vdo-lvm4vdo - this is the path that we need to provide in vProtect



Now we can go to vProtect WebUI to create a new backup destination with enabled deduplication

Example how to fill a file system settings. This configuration will create a backup destination with deduplication enabled and a staging area located on the same vdo volume.
This speeds up the backup process as vProtect will only move the backup data from the staging area to the backup subdirectory.

In the "storage path" enter the path where you want to keep backup data: /vprotect_data/name_of_subdirectory
In the deduplication device, enter the block device created before: /dev/mapper/vg4vdo-lvm4vdo
In the "deduplicated path store", enter the default path to the staging area: /vprotect_data (we usually do not recommend changing the default /vprotect_data path for the staging area)