#first stop VM
#
lvname=vm_www
lvcreate -L5G -s -n $lvname-snap /dev/VolGroup00/$lvname
#the VM can be re-started now
#turn the snapshop into a file image (optionally gzip it)
#dd if=/dev/VolGroup00/$lvname-snap | bzip2 -9 >/backup/$lvname.dd.bz2
dd if=/dev/VolGroup00/$lvname-snap >/backups/$lvname.img
#remove the snapshot
lvremove -f /dev/VolGroup00/$lvname-snap
#copy to another machine
scp $lvname.img root@jordan:/amf300;
rm -f $lvname.img
#on the other machine, run bzip2 -9 vm_xxxx.img

#create a snapshot of the LV drive
/usr/sbin/lvcreate -L5G -s -n vm_test_snap /dev/VolGroup00/vm_test
#turn the snapshop into a file image
dd if=/dev/VolGroup00/vm_test_snap | gzip -9 >/backup/vm_test.dd.gz
#remove the snapshot

I would recommend not using LVM within a VM because it makes it harder to back up the files within the VM

It is confusing that a logical volume can contain either a partitioned drive or a single file-system with no partition table. Doing an fdisk -lu will determine which.

A partition can contain several file-systems, such as boot and a “nested” LVM partition. The link at the bottom gives examples of how to access this.

Create and mount a LV

/usr/sbin/lvcreate -L 20G -n jessica VolGroup00
/sbin/mkfs -j /dev/VolGroup00/jessica -L jessica #format jessica as ext3
mkfs.ext4 -L ext4volname /dev/vg/newvol # or ext4
mount /dev/VolGroup00/jessica /home/jessica/backup

My default Zimbra VM install uses LVM within its own virtual machine. This makes it harder to get at the data from outside the VM, and so complicates backup. The following steps need to be taken