https://drive.google.com/file/d/1dEF0KxCYq66j6aPkyMbp6I2tAFHfrLwu/view?usp=sharing

1. Understanding Cross-Machine LVM Migration

Purpose

• Move an entire LVM setup (VG + LVs) from one machine to another.
• Common for hardware upgrades, server replacements, or disaster recovery.

Key Concepts

• vgexport: Marks a Volume Group as inactive and exportable (prevents auto-activation).
• vgimport: Makes an exported VG available on the new machine.
• No data copying needed—just physically move the disk!

✅ Critical:

The disk must be physically moved (or attached via SAN/iSCSI).

Never run both machines with the same LVM disk attached simultaneously!

2. Lab Setup: Prepare LVM on Source Machine

Create LVM

# Create partition on /dev/sdb (5GB+ disk)
sudo fdisk /dev/sdb
# Commands: n → p → 1 → [Enter] → [Enter] → t → 8e → w
sudo partprobe

# Create LVM
sudo pvcreate /dev/sdb1
sudo vgcreate VolGrp /dev/sdb1
sudo lvcreate -L 2G -n LogVol VolGrp    # Fixed: -L for size (not -l)
sudo mkfs.ext4 /dev/VolGrp/LogVol

# Mount and add data
sudo mkdir /data
sudo mount /dev/VolGrp/LogVol /data
sudo touch /data/{1..11}
sudo umount /data

⚠️ Note:

• l 2000 = 2000 extents (size depends on VG extent size).

Use -L 2G for predictable 2GB size.

3. Export LVM on Source Machine

Steps to Safely Export

# 1. Ensure filesystem is unmounted
df -hT    # Verify /data not mounted

# 2. Deactivate VG
sudo vgchange -an VolGrp    # -an = deactivate all LVs

# 3. Export VG
sudo vgexport VolGrp

# 4. Verify
sudo pvs    # Shows PV but no VG
sudo vgs    # Empty
sudo lvscan # Shows "inactive" (but won't list exported VG)