Skip to main content

Make Backups using LVM snapshots

With Logical Volume Manager, backups can be taken using snapshots.

in this example the resources are:
Volume Group = vg1
Logical Volume1 = /dev/vg1/data 100M /data             //data disk
Logical Volume2 = /dev/vg1/backup 100M /backup    //backup disk
Snapshot Volume = /dev/vg1/snap 100M /snap          //snapshot disk
Disk Name = /dev/sdb                                            //physical disk

First we are going to create a partition.
# fdisk /dev/sdb
new partition: n

primary partition: p

partition number: 1
then the size of the disk will be specified.

Now we create physical volume and logical volumes.
# pvcreate /dev/sdb1

# vgcreate vg1 /dev/sdb1

# lvcreate -L 100M -n data vg1

# lvcreate -L 200M -n backup vg1

Logical volumes will be formatted with ext3 file system format.

# mkfs.ext3 /dev/vg1/data

# mkfs.ext3 /dev/vg1/backup

Logical volumes will be mounted.

# mkdir /data

# mkdir /backup

# mount /dev/vg1/data /data

# mount /dev/vg1/backup /backup

Create some test data.

# cd /data

# mkdir deneme

# touch test

Physical and logical volumes can be listed.

# pvdisplay

# lvdisplay

Now we can take a snapshot.
# lvcreate -L 100M -s -n snap /dev/vg1/data

To see the snapshot volume.
lvdisplay

Mount the snapshot volume.

# mkdir /snap

# mount /dev/vg1/snap /snap

Copy and compress the snapshot volume.
# tar -czvf /backup/backup.tar.gz /snap

Backup is taken so snapshot is no longer needed.

# umount /snap

# lvremove /dev/vg1/snap

Comments

Popular posts from this blog

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address 10.1.10.11 Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are 10.1.3.11, 10.1.35.11, 10.1.40.11 respectively. Proper communication with other servers on the network we should use routing tables. There are three

Listing Zimbra Accounts with Some Details

Recently I have to export the user list for a particular domain. Luckily Zimbra has Admin GUI with a search feature. When you search accounts, you can download search results as a comma-separated csv file. So I did a search and download the result file, but the result did not have all the columns I need and also there is no option for customizing columns for search results. So I had to write a bash script to get the desired list. Here is the bash script ( It can be customized by adding or removing field names. Run it under zimbra user like ./zimbra_account_list.sh <domain_name_here> ):