Project

General

Profile

Bug #16211

Bug #15071: Make our server backup process more usable

move data away from virtual pv's

Added by groente 11 months ago. Updated 11 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Infrastructure
Target version:
Start date:
12/09/2018
Due date:
% Done:

100%

Spent time:
Feature Branch:
Type of work:
Sysadmin
Blueprint:
Starter:
Affected tool:

Description

Currently a number of systems have the following storage configuration:

- lizard has a logical volume DISKNAME and feeds it to a virtual machine.
- the virtual machine sees DISKNAME as /dev/vdb and treats this as an LVM PV
- the virtual machine uses this PV for a volume group
- on this volume group is a logical volume, which is mounted in the virtual machine.

This does not play very nice with our backup system and adds several layers of complexity with close to zero benefits.

My plan is to get to the following situation:

- lizard has a logical volume DISKNAME and offers it to the vm
- the vm sees DISKNAME as /dev/vdb
- /dev/vdb has ext4 on it and is mounted in the vm.

This desired situation is already what we do on www.
This situation allows for a backup procedure that simply takes a snapshot of the logical volume on lizard, mounts it, and sends the data to the backup server.

Affected vm's are: apt-proxy, bitcoin, isobuilder1-4, puppet-git, rsync

History

#1 Updated by intrigeri 11 months ago

My plan is to get to the following situation:

LGTM!

#2 Updated by groente 11 months ago

rsync is done.
puppet-git is done.
isobuilders are done.
apt-proxy is done.
bitcoin is done.

#3 Updated by groente 11 months ago

  • Status changed from Confirmed to Resolved
  • Assignee deleted (groente)
  • % Done changed from 0 to 100

Also available in: Atom PDF