From f41bd92e257d44c8b1ecf7508cc8e7ba285e7c51 Mon Sep 17 00:00:00 2001
From: Rich Megginson Contents
id="toc-snapshot_lvm_mount_origin">snapshot_lvm_mount_origin
snapshot_lvm_action
conflicts and there is sufficient space to take the snapshots
remove
: Remove snapshots that conform to the
specified prefix and pattern
revert
: Revert to snapshots that are specifed by
+
revert
: Revert to snapshots that are specified by
either the pattern or set. If either the source LV or snapshot are open,
the merge is deferred until the next time the server reboots and the
source logical volume is activated.
The mount_origin flag defaults to false, so it is not necessary when the user is mounting the snapshot rather than the origin.
-If before running the role, with :
This variable is required. snapshot_lvm_snapset_name is a string that will be appended to the name of the LV when the snapshot set is created. @@ -364,8 +365,16 @@
If set to true, unmount all mountpoint for the resulting blockdevice. -Linux allows filesytems to be mounted in multiple locations. Setting +Linux allows filesystems to be mounted in multiple locations. Setting this flag will unmount all locations.
+When using snapshot_lvm_all_vgs
, there may be some
+subset of all volume groups that you want to use. Set
+snapshot_lvm_vg_include
to a regex pattern that matches the
+names of the volume groups you want to use and the rest will be
+excluded. For example, snapshot_lvm_vg_include: "^sql_db_"
+will only operate on volume groups whose names start with
+sql_db_
. This uses the Python re.search
.