├── .travis.yml ├── LICENSE ├── NUTSNBOLTS.md ├── README.md └── fi-backup.sh /.travis.yml: -------------------------------------------------------------------------------- 1 | --- 2 | language: python 3 | python: "2.7" 4 | sudo: required 5 | dist: xenial 6 | 7 | install: 8 | # Install dependencies 9 | - sudo apt-get -y update 10 | #- sudo apt-get install --reinstall -y -o Dpkg::Options::="--force-confnew" fontconfig fontconfig-config 11 | - sudo apt-get install --reinstall -y -o Dpkg::Options::="--force-confnew" libvirt-bin virtinst qemu-kvm qemu-utils 12 | 13 | # Configure libvirt qemu 14 | - sudo sh -c 'echo "security_driver = \"none\"" >> /etc/libvirt/qemu.conf' 15 | - sudo service libvirt-bin restart 16 | - sudo service qemu-kvm restart 17 | - sleep 2 18 | 19 | #See if we can setup a VM 20 | - sudo virsh net-list 21 | # Uncomment for more details 22 | #- sudo virsh --connect qemu:///system capabilities 23 | 24 | #install Shellcheck 25 | #- sudo apt-get install -y -o Dpkg::Options::="--force-confnew" cabal-install 26 | #- sudo cabal update 27 | #- sudo cabal install shellcheck 28 | - sudo apt-get install -y -o Dpkg::Options::="--force-confnew" shellcheck 29 | 30 | # Download cirros image and setup disks 31 | - > 32 | wget --no-check-certificate 33 | https://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img 34 | -O /tmp/cirros.img 35 | - mkdir /tmp/test\ disks /tmp/backup\ dir 36 | - sudo chmod 0777 /tmp/backup\ dir 37 | - cp /tmp/cirros.img /tmp/test\ disks/test1\ 1.img 38 | - cp /tmp/cirros.img /tmp/test\ disks/test2\ 1.img 39 | - cp /tmp/cirros.img /tmp/test\ disks/test2\ 2.img 40 | 41 | # Create VMS 42 | - > 43 | sudo virt-install --connect qemu:///system --os-type linux 44 | --os-variant generic --debug --import --name t1d --ram 512 --vcpus 1 45 | --noautoconsole --nographics --virt-type qemu --nonetworks 46 | --disk path=/tmp/test\ disks/test1\ 1.img,device=disk,format=qcow2 47 | 48 | - > 49 | sudo virt-install --connect qemu:///system --os-type linux 50 | --os-variant generic --debug --import --name t2d --ram 512 --vcpus=1 51 | --noautoconsole --nographics --virt-type qemu --nonetworks 52 | --disk path=/tmp/test\ disks/test2\ 1.img,device=disk,format=qcow2 53 | --disk path=/tmp/test\ disks/test2\ 2.img,device=disk,format=qcow2 54 | 55 | - sudo virsh list --all 56 | 57 | script: 58 | # Check fi-backup.sh syntax 59 | - shellcheck --exclude=SC2181 --exclude=SC2034 --exclude=SC2178 fi-backup.sh 60 | 61 | # Test0: stop VMs and see if offline backup works, then restart domains 62 | # shutdown can't be monitored from within virsh. Wait to ensure full start/stop 63 | - mkdir /tmp/backup_off\ dir 64 | - sudo chmod 0777 /tmp/backup_off\ dir 65 | - sleep 20 66 | - sudo virsh shutdown t1d 67 | - sleep 15 68 | - sudo virsh -r list --all 69 | - sudo virsh shutdown t2d 70 | - sleep 15 71 | - sudo virsh -r list --all 72 | - sudo ./fi-backup.sh -d -b /tmp/backup_off\ dir all 73 | - ls -la /tmp/backup_off\ dir/test* 74 | - sleep 2 75 | - sudo virsh start t1d 76 | - sudo virsh start t2d 77 | - sleep 2 78 | 79 | # Test1 1 disk, spaces in filenames 80 | ## 1st Backup 81 | ### Backup 82 | - sudo ./fi-backup.sh -d -b /tmp/backup\ dir t1d 83 | - ls -la /tmp/backup\ dir 84 | - ls -la /tmp/test\ disks 85 | - sleep 2 86 | ### Backup 87 | - sudo ./fi-backup.sh -d -b /tmp/backup\ dir t1d 88 | - ls -la /tmp/backup\ dir 89 | - ls -la /tmp/test\ disks 90 | - sleep 2 91 | ### Consolidate 92 | - sudo ./fi-backup.sh -dc t1d 93 | ## 2nd Backup 94 | ### Backup 95 | - sudo ./fi-backup.sh -d -b /tmp/backup\ dir t1d 96 | - ls -la /tmp/backup\ dir 97 | - ls -la /tmp/test\ disks 98 | - sleep 2 99 | ### Backup 100 | - sudo ./fi-backup.sh -d -b /tmp/backup\ dir t1d 101 | - ls -la /tmp/backup\ dir 102 | - ls -la /tmp/test\ disks 103 | - sleep 2 104 | ### Consolidate 105 | - sudo ./fi-backup.sh -dc t1d 106 | 107 | # Test2 2 disks, spaces in filenames 108 | ## 1st Backup 109 | ### Backup 110 | - sudo ./fi-backup.sh -d -b /tmp/backup\ dir t2d 111 | - ls -la /tmp/backup\ dir 112 | - ls -la /tmp/test\ disks 113 | - sleep 2 114 | ### Backup 115 | - sudo ./fi-backup.sh -d -b /tmp/backup\ dir t2d 116 | - ls -la /tmp/backup\ dir 117 | - ls -la /tmp/test\ disks 118 | - sleep 2 119 | ### Consolidate 120 | - sudo ./fi-backup.sh -dc t2d 121 | ## 2nd Backup 122 | ### Backup 123 | - sudo ./fi-backup.sh -d -b /tmp/backup\ dir t2d 124 | - ls -la /tmp/backup\ dir 125 | - ls -la /tmp/test\ disks 126 | - sleep 2 127 | ### Backup 128 | - sudo ./fi-backup.sh -d -b /tmp/backup\ dir t2d 129 | ### Consolidate 130 | - sudo ./fi-backup.sh -dc t2d 131 | - sleep 2 132 | 133 | # Test3 all domains 134 | ## 1st Backup 135 | ### Backup 136 | - sudo ./fi-backup.sh -d -b /tmp/backup\ dir all 137 | - ls -la /tmp/backup\ dir 138 | - ls -la /tmp/test\ disks 139 | - sleep 2 140 | ### Backup 141 | - sudo ./fi-backup.sh -d -b /tmp/backup\ dir all 142 | ### Consolidate 143 | - sudo ./fi-backup.sh -dc all 144 | ## 2nd Backup 145 | ### Backup 146 | - sudo ./fi-backup.sh -d -b /tmp/backup\ dir all 147 | - ls -la /tmp/backup\ dir 148 | - ls -la /tmp/test\ disks 149 | - sleep 2 150 | ### Backup 151 | - sudo ./fi-backup.sh -d -b /tmp/backup\ dir all 152 | - ls -la /tmp/backup\ dir 153 | - ls -la /tmp/test\ disks 154 | - sleep 2 155 | ### Consolidate 156 | - sudo ./fi-backup.sh -dc all 157 | - sleep 2 158 | 159 | # Test4 all domains, snapshot + consolidate 160 | ## 1st Backup 161 | ### Backup 162 | - sudo ./fi-backup.sh -d -b /tmp/backup\ dir all 163 | - ls -la /tmp/backup\ dir 164 | - ls -la /tmp/test\ disks 165 | - sleep 2 166 | ### Backup 167 | - sudo ./fi-backup.sh -d -b /tmp/backup\ dir all 168 | - ls -la /tmp/backup\ dir 169 | - ls -la /tmp/test\ disks 170 | - sleep 2 171 | ### Consolidate 172 | - sudo ./fi-backup.sh -dC all 173 | - ls -la /tmp/backup\ dir 174 | - ls -la /tmp/test\ disks 175 | - sleep 2 176 | ## 2nd Backup 177 | ### Backup 178 | - sudo ./fi-backup.sh -d -b /tmp/backup\ dir all 179 | - ls -la /tmp/backup\ dir 180 | - ls -la /tmp/test\ disks 181 | - sleep 2 182 | ### Backup 183 | - sudo ./fi-backup.sh -d -b /tmp/backup\ dir all 184 | - ls -la /tmp/backup\ dir 185 | - ls -la /tmp/test\ disks 186 | - sleep 2 187 | ### Consolidate 188 | - sudo ./fi-backup.sh -dC all 189 | - ls -la /tmp/backup\ dir 190 | - ls -la /tmp/test\ disks 191 | - sleep 2 192 | 193 | # Test5 all domains, dump state, snapshot, consolidate 194 | ## 1st Backup 195 | ### Backup 196 | - sudo ./fi-backup.sh -d -s /tmp/backup\ dir -b /tmp/backup\ dir all 197 | - sudo virsh list --all 198 | - ls -la /tmp/backup\ dir 199 | - ls -la /tmp/test\ disks 200 | - sleep 2 201 | ### Backup 202 | - sudo ./fi-backup.sh -d -s /tmp/backup\ dir -b /tmp/backup\ dir all 203 | - sudo virsh list --all 204 | - ls -la /tmp/backup\ dir 205 | - ls -la /tmp/test\ disks 206 | - sleep 2 207 | ### Consolidate 208 | - sudo ./fi-backup.sh -dc all 209 | - sudo virsh list --all 210 | - ls -la /tmp/backup\ dir 211 | - ls -la /tmp/test\ disks 212 | - sleep 2 213 | ## 2nd Backup 214 | ### Backup 215 | - sudo ./fi-backup.sh -d -s /tmp/backup\ dir -b /tmp/backup\ dir all 216 | - sudo virsh list --all 217 | - ls -la /tmp/backup\ dir 218 | - ls -la /tmp/test\ disks 219 | - sleep 2 220 | ### Backup 221 | - sudo ./fi-backup.sh -d -s /tmp/backup\ dir -b /tmp/backup\ dir all 222 | - sudo virsh list --all 223 | - ls -la /tmp/backup\ dir 224 | - ls -la /tmp/test\ disks 225 | - sleep 2 226 | ### Consolidate 227 | - sudo ./fi-backup.sh -dc all 228 | - sudo virsh list --all 229 | - ls -la /tmp/backup\ dir 230 | - ls -la /tmp/test\ disks 231 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | 635 | Copyright (C) 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | Copyright (C) 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /NUTSNBOLTS.md: -------------------------------------------------------------------------------- 1 | Forward incremental Backup 2 | -------------------------- 3 | 4 | Initial configuration. "Current image" pointer is an abstraction for the image currently used by qemu to run a given domain. 5 | 6 | Current image 7 | | 8 | v 9 | +-----------------+ 10 | | disk.qcow2 | 11 | +-----------(R/W)-+ 12 | 13 | Run `fi-backup`. 14 | 15 | Current image 16 | | 17 | v 18 | +------------------+ +------------------------+ 19 | | disk.qcow2 |<--| disk.bimg- | 20 | +------------(R/O)-+ +------------------(R/W)-+ 21 | 22 | 23 | After the first run, `disk.qcow2` is the backing file of `disk.bimg-`. That means that `disk.qcow2` is used in read-only mode by qemu. Thus, it can be safely copied to perform our backup. 24 | 25 | 26 | Current image 27 | | 28 | v 29 | +------------------+ +------------------------+ +------------------------+ 30 | | disk.qcow2 |<--| disk.bimg- |<--| disk.bimg- | 31 | +------------(R/O)-+ +------------------(R/O)-+ +------------------(R/W)-+ 32 | 33 | After the second run, `disk.qcow2` has not changed, so we can just copy `disk.bimg-` to our backup storage. 34 | This is the "key" of forward incremental backup: `disk.bimg-` contains just the deltas since the first `fi-backup` run. 35 | 36 | 37 | Consolidation 38 | ------------- 39 | 40 | Consolidation reduces the number of backing files. This can be done one of two ways. (1) BlockCommit or (2) BlockPull 41 | BlockCommit copies the content of backing files into the current image, and then removing the backing images. 42 | BlockPull copies the state of the current image into the last backing image and then removing the original image and child images up to the last backing image. 43 | 44 | This reduces the number of image files. See README.md for more information about the advantages of BlockCommit vs BlockPull. Like time to consolidate vs image size. 45 | 46 | Here is an example of consolidation via BlockPull 47 | 48 | 49 | Current image 50 | | 51 | v 52 | +------------------+ +------------------------+ +------------------------+ 53 | | disk.qcow2 |<--| disk.bimg- |<--| disk.bimg- | 54 | +------------(R/O)-+ +------------------(R/O)-+ +------------------(R/W)-+ 55 | 56 | 57 | Running in consolidation BlockPull mode will "copy" backing images content into the current image. 58 | 59 | Current image 60 | +--block-pull->+ +--block-pull->+ | 61 | | | | | v 62 | +------------------+ +------v---------+-------+ +--v---------------------+ 63 | | disk.qcow2 | X | disk.bimg- | X | disk.bimg- | 64 | +-----------(R/O)--+ +------------------(R/O)-+ +------------------(R/W)-+ 65 | 66 | After that, the original image and old backing files can be deleted. 67 | `fi-backup.sh` will automatically delete every old backing file. : 68 | 69 | Current image 70 | | 71 | v 72 | +------------------------+ 73 | | disk.bimg- | 74 | +------------------(R/W)-+ 75 | 76 | Here is an example of consolidation via BlockCommit 77 | 78 | Current image 79 | | 80 | v 81 | +------------------+ +------------------------+ +------------------------+ 82 | | disk.qcow2 |<--| disk.bimg- |<--| disk.bimg- | 83 | +------------(R/O)-+ +------------------(R/O)-+ +------------------(R/W)-+ 84 | 85 | 86 | Running in consolidation BlockCommit mode will "copy" backing images content into the current image. 87 | 88 | Current image 89 | +<-block-pull--+ +<-block-pull--+ | 90 | | | | | v 91 | +--------------V---+ +------+---------V-------+ +--+---------------------+ 92 | | disk.qcow2 |<--| disk.bimg- | X | disk.bimg- | 93 | +-----------(R/O)--+ +------------------(R/O)-+ +------------------(R/W)-+ 94 | 95 | After that, the unused files can be deleted.`fi-backup.sh` will automatically delete every unused file. : 96 | 97 | Current image 98 | | 99 | v 100 | +------------------------+ 101 | | disk.qcow2 | 102 | +------------------(R/W)-+ 103 | 104 | 105 | Restore 106 | ------- 107 | 108 | Restore procedure for a domain A, with images in directory B, backup directory C is the following. Thanks to [svorobyov](https://github.com/svorobyov) for these steps. 109 | 110 | 1. clean up the directory B from all images for domain A; 111 | 2. copy the desired chains of the backing images for domain A from C to B (although it is not recommended, chains can be of different lengths, e.g., recover disk 1 to the state two days back and disk 2 to the state three days); 112 | 3. specify (using `virsh`, `virt-manager`, `virt-install`, ...) that the disks for A are the last images of the chains in 2 (this is important, otherwise the VM state description may be inconsistent) 113 | 4. optionally, consolidate for domain A (which will use chains of images in B) 114 | 115 | Restore of backup with domain state dump can be performed 116 | 117 | TBW 118 | ` -incoming "exec: gzip -c -d "` 119 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # LibVirtKvm-Scripts 2 | 3 | **Status** 4 | * [![Build Status](https://travis-ci.org/dguerri/LibVirtKvm-scripts.svg?branch=master)](https://travis-ci.org/dguerri/LibVirtKvm-scripts) on master branch 5 | * [![Build Status](https://travis-ci.org/dguerri/LibVirtKvm-scripts.svg?branch=development)](https://travis-ci.org/dguerri/LibVirtKvm-scripts) on development branch 6 | 7 | ## fi-backup - Online Forward Incremental Backup for Libvirt/KVM VMs 8 | 9 | fi-backup can be used to make offline or online _forward incremental_ backups of libvirt/KVM virtual machines. 10 | It works on VMs with multiple disks but only if disk images are in qcow2 format. 11 | It also allows consolidation of backups previously taken. Both backup and consolidation can be performed live, on running domains. 12 | 13 | Note 14 | ---- 15 | 16 | By default `fi-backup.sh` guarantees that qcow2 images format is consistent, but this doesn't imply that the contained filesystems are consistent too. 17 | In order to perform consistent backups, you can use two different strategies: 18 | 19 | 1. use domain quiescence (`-q` option, see below). This requires configuring the domain to use quiescence (e.g. `apt-get install qemu-guest-agent` inside VM); 20 | 2. dump domain state (`-s ` option, see below). In this case the domain is paused, its state is dumped, a snapshot of all its disks is performed and then the domain is restarted. 21 | 22 | Option number 2 doesn't require agents installed in the domain, but it will pause the VM for some 23 | seconds (the actual number of secords depends on how busy the VM is and the mount of RAM given to the VM). 24 | For very busy domain, state dump could not complete, expecially if it is done on slow disks (e.g. NFS). 25 | 26 | Offline backups work by comparing timestamps on the VM images vs the backup timestamps and doing a 27 | "cp --update" which only updates the backups if the image timestamp is newer than the backup timestamp. 28 | 29 | The Backup method `blockpull` works as: `orig -> snap1 -> snap2 -> ... [becomes] snap3`. 30 | 31 | The blockpull method has the benefit that snap3 will be a compressed image only taking up as much 32 | space as was used by the VM's OS. For example: 33 | if you have a 100 GB Virtual Machine file but the VM only uses 10 GB of that 100 GB, 34 | then the image file created for snap3 will only be about 10 GB, saving you 90 GB of disk space on the 35 | VM host. The disadvantage of this method is that it takes a long time for the blockpull to roll all 36 | previous backing files into the snap3 file (can be minutes). 37 | 38 | The backup method `blockcommit` works as: `orig -> snap1 -> snap2 -> .... [becomes] orig`. 39 | 40 | The blockcommit method has the benefits that the file name of the VM does not change and the backup 41 | is extremely quick (only a few seconds to roll the few changes back to orig) relative to the blockpull 42 | method (can take several minutes depending on how large the VM is or how long the snapshot chain is). 43 | The disadvantage of this method is that it does not shrink the size of orig. 44 | 45 | A recommended method for automating backups via fi-backup.sh is to have the first backup be 46 | done with `--method=blockpull` 47 | to create a smaller disk image and then for all subsequent backups use `--method=blockcommit`. 48 | 49 | See sample usage below for more information. 50 | For more information about how backups are performed, see [Nuts and Bolts of fi-backup](NUTSNBOLTS.md) 51 | 52 | ## Apparmor 53 | 54 | Please note that in some cases, **apparmor prevents this script from working**: 55 | 56 | `fi-backup.sh` uses the `virsh create-snapshot` command. On some distribution (e.g. Ubuntu) this command fails to create external snapshot with apparmor enabled. 57 | 58 | See this [bug report](https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1004606) for more information and for a workaround. 59 | 60 | *Quick and dirty workaround* 61 | 62 | Edit `/etc/libvirt/qemu.conf` and set 63 | 64 | security_driver = "none" 65 | 66 | ## Dependencies 67 | 68 | `fi-backup.sh` is designed to run on GNU/Linux. The following software is also required: 69 | 70 | * libVirt >= 0.9.13 71 | * QEMU/KVM >= 1.2.0 72 | 73 | ### Syntax 74 | 75 | fi-backup version 2.1.0 - Davide Guerri 76 | 77 | Usage: 78 | 79 | ./fi-backup.sh [-c|-C] [-q|-s ] [-h] [-d] [-v] [-V] [-b ] ""|all 80 | 81 | Options 82 | -b, --backup_dir Copy previous snapshot/base image to the specified 83 | -c, --consolidate_only Consolidation only 84 | -C, --consolidate_and_snapshot Snapshot and consolidation 85 | -m, --method Use blockpull or blockcommit for consolidation 86 | -q, --quiesce Use quiescence (qemu agent must be installed in the domain) 87 | -s, --dump_state_dir Dump domain status in the specified directory 88 | -d, --debug Debug 89 | -r, --all_running Backup all running domains only (do not specify domains) 90 | -h, --help Print usage and exit 91 | -v, --verbose Verbose 92 | -V, --version Print version and exit 93 | 94 | ### Sample usage 95 | 96 | #### _Forward incremental_ backup of a virtual machine with one disk 97 | (output might be slightly different depending on the version used) 98 | 99 | ~# mkdir -p /nfs/backup-dir/fi-backups/DGuerri_Domain 100 | 101 | ~# ./fi-backup.sh -b /nfs/backup-dir/fi-backups/DGuerri_Domain -d DGuerri_Domain 102 | [DEB] libVirt version '0.9.13' is supported 103 | [DEB] qemu-img version '1.2.0' is supported 104 | [DEB] KVM version '1.2.0' is supported 105 | [DEB] Snapshot for domain 'DGuerri_Domain' requested 106 | [DEB] Using timestamp '20130531-114338' 107 | [DEB] Snapshotting block devices for 'DGuerri_Domain' using suffix 'bimg-20130531-114338' 108 | [VER] Snapshot for block devices of 'DGuerri_Domain' successful 109 | [VER] Copy backing file '/nfs/original-dir/DGuerri_Domain.img' to '/nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain.img' 110 | [VER] No parent backing file for '/nfs/original-dir/DGuerri_Domain.img' 111 | 112 | The original images directory content after this backup is shown below. 113 | 114 | ~# ls /nfs/original-dir/DGuerri_Domain* -latr 115 | -rw------- 1 libvirt-qemu kvm 64108953600 May 31 2013 /nfs/original-dir/DGuerri_Domain.img 116 | -rw------- 1 libvirt-qemu kvm 1883308032 May 31 2013 /nfs/original-dir/DGuerri_Domain.bimg-20130531-114338 117 | 118 | `DGuerri_Domain.bimg-20130531-114338` is the current image for `DGuerri_Domain`. 119 | `DGuerri_Domain.img` is now the backing file for `DGuerri_Domain.bimg-20130531-114338`. 120 | 121 | The backup directory now contains the following files: 122 | 123 | ~# ls /nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain* -latr 124 | drwxr-xr-x 2 root root 4096 May 31 2013 . 125 | drwxr-xr-x 3 root root 4096 May 31 2013 .. 126 | -rw------- 1 root root 64108953600 May 31 2013 /nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain.img 127 | 128 | Some time later, another backup is made: 129 | 130 | ~# ./fi-backup.sh -b /nfs/backup-dir/fi-backups/DGuerri_Domain -d DGuerri_Domain 131 | [DEB] libVirt version '0.9.13' is supported 132 | [DEB] qemu-img version '1.2.0' is supported 133 | [DEB] KVM version '1.2.0' is supported 134 | [DEB] Snapshot for domain 'DGuerri_Domain' requested 135 | [DEB] Using timestamp '20130531-120054' 136 | [DEB] Snapshotting block devices for 'DGuerri_Domain' using suffix 'bimg-20130531-120054' 137 | [VER] Snapshot for block devices of 'DGuerri_Domain' successful 138 | [VER] Copy backing file '/nfs/original-dir/DGuerri_Domain.bimg-20130531-114338' to '/nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain.bimg-20130531-114338' 139 | [DEB] Parent backing file: '/nfs/original-dir/DGuerri_Domain.img' 140 | [VER] Changing original backing file reference for '/nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain.bimg-20130531-114338' from '/nfs/original-dir/DGuerri_Domain.img' to '/nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain.img' 141 | 142 | The original images directory content after this backup is shown below. 143 | 144 | ~# ls /nfs/original-dir/DGuerri_Domain* - -latr 145 | -rw------- 1 libvirt-qemu kvm 64108953600 May 31 2013 /nfs/original-dir/DGuerri_Domain.img 146 | -rw------- 1 libvirt-qemu kvm 1883308032 May 31 2013 /nfs/original-dir/DGuerri_Domain.bimg-20130531-114338 147 | -rw------- 1 libvirt-qemu kvm 221446144 May 31 2013 /nfs/original-dir/DGuerri_Domain.bimg-20130531-120054 148 | 149 | `DGuerri_Domain.img` is the backing file for `DGuerri_Domain.bimg-20130531-114338` which in turn is the backing file for `DGuerri_Domain.bimg-20130531-120054`. 150 | The image `DGuerri_Domain.bimg-20130531-120054` is the current image for the domain named `DGuerri_Domain`. 151 | 152 | The backup directory now contains the following files: 153 | 154 | ~# ls /nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain* -latr 155 | -rw------- 1 root root 64108953600 May 31 2013 /nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain.img 156 | -rw------- 1 root root 1883308032 May 31 2013 /nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain.bimg-20130531-114338 157 | 158 | `DGuerri_Domain.img` is the backing file for `DGuerri_Domain.bimg-20130531-114338`. 159 | 160 | After some more backups, the content of the original directory is the following: 161 | 162 | ~# ls /nfs/original-dir/DGuerri_Domain* -latr 163 | -rw------- 1 libvirt-qemu kvm 64108953600 May 31 12:40 /nfs/original-dir/DGuerri_Domain.img 164 | -rw------- 1 libvirt-qemu kvm 1883308032 May 31 12:58 /nfs/original-dir/DGuerri_Domain.bimg-20130531-114338 165 | -rw------- 1 libvirt-qemu kvm 1394475008 May 31 2013 /nfs/original-dir/DGuerri_Domain.bimg-20130531-120054 166 | -rw------- 1 libvirt-qemu kvm 524288 May 31 2013 /nfs/original-dir/DGuerri_Domain.bimg-20130531-125445 167 | -rw------- 1 libvirt-qemu kvm 786432 May 31 2013 /nfs/original-dir/DGuerri_Domain.bimg-20130531-125701 168 | -rw------- 1 libvirt-qemu kvm 3604480 May 31 2013 /nfs/original-dir/DGuerri_Domain.bimg-20130531-125719 169 | 170 | And here is the content for the backup directory: 171 | 172 | ~# ls /nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain* -latr 173 | -rw------- 1 root root 64108953600 May 31 12:56 /nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain.img 174 | -rw------- 1 root root 1883308032 May 31 12:58 /nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain.bimg-20130531-114338 175 | -rw------- 1 root root 1394475008 May 31 2013 /nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain.bimg-20130531-120054 176 | -rw------- 1 root root 524288 May 31 2013 /nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain.bimg-20130531-125445 177 | -rw------- 1 root root 786432 May 31 2013 /nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain.bimg-20130531-125701 178 | 179 | Consolidation example: 180 | 181 | ~# ./fi-backup.sh -c -d DGuerri_Domain 182 | [DEB] libVirt version '0.9.13' is supported 183 | [DEB] qemu-img version '1.2.0' is supported 184 | [DEB] KVM version '1.2.0' is supported 185 | [DEB] Consolidation of block devices for 'DGuerri_Domain' requested 186 | [DEB] Block devices to be consolidated: 187 | /nfs/original-dir/DGuerri_Domain.bimg-20130531-125719 188 | [DEB] Consolidation of block device: '/nfs/original-dir/DGuerri_Domain.bimg-20130531-125719' for 'DGuerri_Domain' 189 | [DEB] Parent block device: '/nfs/original-dir/DGuerri_Domain.bimg-20130531-125701' 190 | [VER] Consolidation of block device '/nfs/original-dir/DGuerri_Domain.bimg-20130531-125719' for 'DGuerri_Domain' successful 191 | [VER] Deleting old backup files for 'DGuerri_Domain' 192 | [DEB] Processing old backing file '/nfs/original-dir/DGuerri_Domain.bimg-20130531-125701' for 'DGuerri_Domain' 193 | [VER] Deleting backing file '/nfs/original-dir/DGuerri_Domain.bimg-20130531-125701' 194 | [DEB] Next file in backing file chain: '/nfs/original-dir/DGuerri_Domain.bimg-20130531-125445' 195 | [DEB] Processing old backing file '/nfs/original-dir/DGuerri_Domain.bimg-20130531-125445' for 'DGuerri_Domain' 196 | [VER] Deleting backing file '/nfs/original-dir/DGuerri_Domain.bimg-20130531-125445' 197 | [DEB] Next file in backing file chain: '/nfs/original-dir/DGuerri_Domain.bimg-20130531-120054' 198 | [DEB] Processing old backing file '/nfs/original-dir/DGuerri_Domain.bimg-20130531-120054' for 'DGuerri_Domain' 199 | [VER] Deleting backing file '/nfs/original-dir/DGuerri_Domain.bimg-20130531-120054' 200 | [DEB] Next file in backing file chain: '/nfs/original-dir/DGuerri_Domain.bimg-20130531-114338' 201 | [DEB] Processing old backing file '/nfs/original-dir/DGuerri_Domain.bimg-20130531-114338' for 'DGuerri_Domain' 202 | [VER] Deleting backing file '/nfs/original-dir/DGuerri_Domain.bimg-20130531-114338' 203 | [DEB] Next file in backing file chain: '/nfs/original-dir/DGuerri_Domain.img' 204 | [DEB] Processing old backing file '/nfs/original-dir/DGuerri_Domain.img' for 'DGuerri_Domain' 205 | [WAR] '/nfs/original-dir/DGuerri_Domain.img' doesn't seem to be a backup backing file image. Stopping backing file chain removal (manual intervetion required)... 206 | 207 | The last error occours because the filename `DGuerri_Domain.img` doesn't have `bimg-` suffix. In this particular case, we can safely remove this file. 208 | 209 | ~# ls /nfs/original-dir/DGuerri_Domain.* -la 210 | -rw------- 1 libvirt-qemu kvm 64108953600 May 31 2013 /nfs/original-dir/DGuerri_Domain.bimg-20130531-125719 211 | -rw------- 1 libvirt-qemu kvm 64108953600 May 31 12:40 /nfs/original-dir/DGuerri_Domain.img 212 | 213 | Of course the backup images remain untouched. Each image depends on the previous one. 214 | 215 | ~# ls /nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain* -latr 216 | -rw------- 1 root root 64108953600 May 31 12:56 /nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain.img 217 | -rw------- 1 root root 1883308032 May 31 12:58 /nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain.bimg-20130531-114338 218 | -rw------- 1 root root 1394475008 May 31 2013 /nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain.bimg-20130531-120054 219 | -rw------- 1 root root 524288 May 31 2013 /nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain.bimg-20130531-125445 220 | -rw------- 1 root root 786432 May 31 2013 /nfs/backup-dir/fi-backups/DGuerri_Domain/DGuerri_Domain.bimg-20130531-125701 221 | 222 | The recovery of an incremental backup is possible using the appropriate chain. 223 | For instance, in order to recover the backup with timestamp `20130531-120054`, the following images are needed: 224 | 225 | * `DGuerri_Domain.img` 226 | * `DGuerri_Domain.bimg-20130531-114338` 227 | * `DGuerri_Domain.bimg-20130531-120054` 228 | 229 | # Contributing to LibVirtKvm-Scripts 230 | 231 | * Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet. 232 | * Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it. 233 | * Fork the project. 234 | * Start a feature/bugfix branch. 235 | * Commit and push until you are happy with your contribution. 236 | * Make sure to add tests for it. This is important so I don't break it in a future version unintentionally. 237 | * Please try not to mess with the version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it. 238 | 239 | # Copyright 240 | 241 | Copyright (C) 2013 2014 2015 Davide Guerri - 242 | See LICENSE.txt for further details. 243 | -------------------------------------------------------------------------------- /fi-backup.sh: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env bash 2 | # 3 | # This file is part of fi-backup. 4 | # 5 | # fi-backup is free software: you can redistribute it and/or modify 6 | # it under the terms of the GNU General Public License as published by 7 | # the Free Software Foundation, either version 3 of the License, or 8 | # (at your option) any later version. 9 | # 10 | # fi-backup is distributed in the hope that it will be useful, 11 | # but WITHOUT ANY WARRANTY; without even the implied warranty of 12 | # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 13 | # GNU General Public License for more details. 14 | # 15 | # You should have received a copy of the GNU General Public License 16 | # along with fi-backup. If not, see . 17 | # 18 | # fi-backup - Online Forward Incremental Libvirt/KVM backup 19 | # Copyright (C) 2013 2014 2015 Davide Guerri - davide.guerri@gmail.com 20 | # 21 | 22 | VERSION="2.2.0" 23 | APP_NAME="fi-backup" 24 | 25 | # Fail if one process fails in a pipe 26 | set -o pipefail 27 | 28 | # Executables 29 | QEMU_IMG="/usr/bin/qemu-img" 30 | VIRSH="/usr/bin/virsh" 31 | QEMU="/usr/bin/qemu-system-x86_64" 32 | 33 | # Defaults and constants 34 | BACKUP_DIRECTORY= 35 | CONSOLIDATION=0 36 | DEBUG=0 37 | VERBOSE=0 38 | QUIESCE=0 39 | DUMP_STATE=0 40 | SNAPSHOT=1 41 | SNAPSHOT_PREFIX="bimg" 42 | DUMP_STATE_TIMEOUT=60 43 | DUMP_STATE_DIRECTORY= 44 | CONSOLIDATION_SET=0 45 | CONSOLIDATION_METHOD="blockpull" 46 | CONSOLIDATION_FLAGS=(--wait) 47 | ALL_RUNNING_DOMAINS=0 48 | QEMU_IMG_SHARE_FLAG="" 49 | 50 | 51 | function print_v() { 52 | local level=$1 53 | 54 | case $level in 55 | v) # Verbose 56 | [ $VERBOSE -eq 1 ] && echo -e "[VER] ${*:2}" 57 | ;; 58 | d) # Debug 59 | [ $DEBUG -eq 1 ] && echo -e "[DEB] ${*:2}" 60 | ;; 61 | e) # Error 62 | echo -e "[ERR] ${*:2}" 63 | ;; 64 | w) # Warning 65 | echo -e "[WAR] ${*:2}" 66 | ;; 67 | *) # Any other level 68 | echo -e "[INF] ${*:2}" 69 | ;; 70 | esac 71 | } 72 | 73 | function print_usage() { 74 | [ -n "$1" ] && (echo "" ; print_v e "$1\n") 75 | 76 | cat < 78 | 79 | Usage: 80 | 81 | $0 [-c|-C] [-q|-s ] [-h] [-d] [-v] [-V] [-b ] [-m ] |all 82 | 83 | Options: 84 | -b Copy previous snapshot/base image to the specified 85 | -c Consolidation only 86 | -C Snapshot and consolidation 87 | -m Consolidation method: blockcommit or blockpull 88 | -q Use quiescence (qemu agent must be installed in the domain) 89 | -s Dump domain status in the specified directory 90 | -d Debug 91 | -h Print usage and exit 92 | -v Verbose 93 | -V Print version and exit 94 | 95 | Version Requirements: 96 | bash >= 4.3.0 97 | qemu_img >= 1.2.0 98 | qemu >= 1.2.0 99 | virsh >= 0.9.13 100 | 101 | EOU 102 | } 103 | 104 | # Mutual exclusion management: only one instance of this script can be running 105 | # at one time. 106 | function try_lock() { 107 | local domain_name=$1 108 | 109 | exec 29>"/var/lock/$domain_name.fi-backup.lock" 110 | 111 | flock -n 29 112 | 113 | if [ $? -ne 0 ]; then 114 | return 1 115 | else 116 | return 0 117 | fi 118 | } 119 | 120 | function unlock() { 121 | local domain_name=$1 122 | 123 | rm "/var/lock/$domain_name.fi-backup.lock" 124 | exec 29>&- 125 | } 126 | 127 | # return 0 if program version is equal or greater than check version 128 | function check_version() 129 | { 130 | local version=$1 check=$2 131 | local winner= 132 | 133 | winner=$(echo -e "$version\n$check" | sed '/^$/d' | sort -Vr | head -1) 134 | [[ "$winner" = "$version" ]] && return 0 135 | return 1 136 | } 137 | 138 | # Function: get_block_devices() 139 | # Return the list of block devices of a domain. This function correctly 140 | # handles paths with spaces. 141 | # 142 | # Input: Domain name 143 | # Output: An array containing a block device list 144 | # Return: 0 on success, non 0 otherwise 145 | function get_block_devices() { 146 | local domain_name=$1 147 | local -n return_var=$2 148 | local _ret= 149 | 150 | return_var=() 151 | 152 | while IFS= read -r file; do 153 | return_var+=("$file") 154 | done < <($VIRSH -q -r domblklist "$domain_name" --details|awk \ 155 | '"disk"==$2 {$1=$2=$3=""; print $0}'|sed 's/^[ \t]*//') 156 | 157 | return 0 158 | } 159 | 160 | # Function: get_snapshot_chain() 161 | # Return an array of all backing files 162 | # 163 | # Input: Block Device 164 | # Output: An array containing a backing file list 165 | # Return: 0 on success, non 0 otherwise 166 | function get_snapshot_chain() { 167 | local endmost_child=$1 168 | local -n return_var=$2 169 | local _parent_backing_file= 170 | local _backing_file= 171 | local i=0 172 | local _ret= 173 | 174 | return_var[$i]="$endmost_child" 175 | 176 | _ret=1 177 | 178 | get_backing_file "$endmost_child" _parent_backing_file 179 | if [ $? -eq 0 ]; then 180 | while [ -e "$_parent_backing_file" ]; do 181 | ((i++)) 182 | return_var[$i]="$_parent_backing_file" 183 | #get next backing file if it exists 184 | _backing_file="$_parent_backing_file" 185 | get_backing_file "$_backing_file" _parent_backing_file 186 | print_v d "Next file in backing file chain: '$_parent_backing_file'" 187 | _ret=0 188 | done 189 | fi 190 | 191 | return $_ret 192 | } 193 | # Function: get_backing_file() 194 | # Return the immediate parent of a qcow2 image file (i.e. the backing file) 195 | # 196 | # Input: qcow2 image file name 197 | # Output: A backing file name 198 | # Return: 0 on success, non 0 otherwise 199 | function get_backing_file() { 200 | local file_name=$1 201 | local -n _return_var=$2 202 | local _ret= 203 | local _backing_file= 204 | local version= 205 | 206 | version=$(qemu_version) 207 | _backing_file=$($QEMU_IMG info $QEMU_IMG_SHARE_FLAG "$file_name" | \ 208 | awk '/^backing file: / {$1=$2=""; print $0}'|sed 's/^[ \t]*//') 209 | _ret=$? 210 | if [[ $_ret == 1 ]]; then 211 | print_v e "Error in getting backing file: Check if running with sufficient permissions (sudo, apparmor status, etc)" 212 | fi 213 | 214 | _return_var="$_backing_file" 215 | 216 | return $_ret 217 | } 218 | 219 | # Function: dump_state() 220 | # Dump a domain state, pausing the domain right afterwards 221 | # 222 | # Input: a domain name 223 | # Input: a timestamp (this will be added to the file name) 224 | # Return: 0 on success, non 0 otherwise 225 | function dump_state() { 226 | local domain_name=$1 227 | local timestamp=$2 228 | 229 | local _ret= 230 | local _timeout= 231 | 232 | local _dump_state_filename="$DUMP_STATE_DIRECTORY/$domain_name.statefile-$timestamp.gz" 233 | 234 | local output= 235 | 236 | output=$($VIRSH qemu-monitor-command "$domain_name" '{"execute": "migrate", "arguments": {"uri": "exec:gzip -c > ' "'$_dump_state_filename'" '"}}' 2>&1) 237 | if [ $? -ne 0 ]; then 238 | print_v e "Failed to dump domain state: '$output'" 239 | return 1 240 | fi 241 | 242 | _timeout=5 243 | print_v d "Waiting for dump file '$_dump_state_filename' to be created" 244 | while [ ! -f "$_dump_state_filename" ]; do 245 | _timeout=$((_timeout - 1)) 246 | if [ "$_timeout" -eq 0 ]; then 247 | print_v e "Timeout while waiting for dump file to be created" 248 | return 4 249 | fi 250 | sleep 1 251 | print_v d "Still waiting for dump file '$_dump_state_filename' to be created ($_timeout)" 252 | done 253 | print_v d "Dump file '$_dump_state_filename' created" 254 | 255 | if [ ! -f "$_dump_state_filename" ]; then 256 | print_v e "Dump file not created ('$_dump_state_filename'), something went wrong! ('$output' ?)" 257 | return 1 258 | fi 259 | 260 | _timeout="$DUMP_STATE_TIMEOUT" 261 | print_v d "Waiting for '$domain_name' to be paused" 262 | while true; do 263 | output=$(virsh domstate "$domain_name") 264 | if [ $? -ne 0 ]; then 265 | print_v e "Failed to check domain state" 266 | return 2 267 | fi 268 | if [ "$output" == "paused" ]; then 269 | print_v d "Domain paused!" 270 | break 271 | fi 272 | if [ "$_timeout" -eq 0 ]; then 273 | print_v e "Timeout while waiting for VM to pause: '$output'" 274 | return 3 275 | fi 276 | print_v d "Still waiting for '$domain_name' to be paused ($_timeout)" 277 | sleep 1 278 | _timeout=$((_timeout - 1)) 279 | done 280 | 281 | return 0 282 | } 283 | 284 | # Function: snapshot_domain() 285 | # Take a snapshot of all block devices of a domain 286 | # 287 | # Input: Domain name 288 | # Return: 0 on success, non 0 otherwise 289 | function snapshot_domain() { 290 | local domain_name=$1 291 | 292 | local _ret=0 293 | local backing_file= 294 | local block_device= 295 | local block_devices= 296 | local extra_args= 297 | local command_output= 298 | local new_backing_file= 299 | local parent_backing_file= 300 | 301 | local timestamp= 302 | local resume_vm=0 303 | 304 | timestamp=$(date "+%Y%m%d-%H%M%S") 305 | 306 | print_v d "Snapshot for domain '$domain_name' requested" 307 | print_v d "Using timestamp '$timestamp'" 308 | 309 | # Dump VM state 310 | if [ "$DUMP_STATE" -eq 1 ]; then 311 | print_v v "Dumping domain state" 312 | dump_state "$domain_name" "$timestamp" 313 | if [ $? -ne 0 ]; then 314 | print_v e \ 315 | "Domain state dump failed!" 316 | return 1 317 | else 318 | resume_vm=1 319 | # Should something go wrong, resume the domain 320 | trap 'virsh resume "$domain_name" >/dev/null 2>&1' SIGINT SIGTERM 321 | fi 322 | fi 323 | 324 | # Create an external snapshot for each block device 325 | print_v d "Snapshotting block devices for '$domain_name' using suffix '$SNAPSHOT_PREFIX-$timestamp'" 326 | 327 | if [ $QUIESCE -eq 1 ]; then 328 | print_v d "Quiesce requested" 329 | extra_args="--quiesce" 330 | fi 331 | 332 | print_v v "$VIRSH -q snapshot-create-as $domain_name" \ 333 | "$SNAPSHOT_PREFIX-$timestamp --no-metadata --disk-only --atomic "\ 334 | "$extra_args" 335 | 336 | command_output=$($VIRSH -q snapshot-create-as "$domain_name" \ 337 | "$SNAPSHOT_PREFIX-$timestamp" --no-metadata --disk-only --atomic \ 338 | $extra_args 2>&1) 339 | if [ $? -eq 0 ]; then 340 | print_v v "Snapshot for block devices of '$domain_name' successful" 341 | 342 | if [ -n "$BACKUP_DIRECTORY" ] && [ ! -d "$BACKUP_DIRECTORY" ]; then 343 | print_v e "Backup directory '$BACKUP_DIRECTORY' doesn't exist" 344 | _ret=1 345 | elif [ -n "$BACKUP_DIRECTORY" ] && [ -d "$BACKUP_DIRECTORY" ]; then 346 | #make backup after snapshot 347 | get_block_devices "$domain_name" block_devices 348 | if [ $? -ne 0 ]; then 349 | print_v e "Error getting block device list for domain \ 350 | '$domain_name'" 351 | _ret=1 352 | else 353 | for ((i = 0; i < ${#block_devices[@]}; i++)); do 354 | block_device="${block_devices[$i]}" 355 | #if this is the fist run, need entire chain to back up 356 | print_v d "Getting all backing files for: '$block_device'" 357 | local snapshot_chain=() 358 | get_snapshot_chain "$block_device" snapshot_chain 359 | #backup entire chain except the snapshot just made (0th element of chain) 360 | for ((j = 1; j < ${#snapshot_chain[@]} ; j++)); do 361 | backing_file_base=$(basename "${snapshot_chain[$j]}") 362 | new_backing_file="$BACKUP_DIRECTORY/$backing_file_base" 363 | 364 | print_v v \ 365 | "Copy backing file '${snapshot_chain[$j]}' to '$new_backing_file'" 366 | cp -u "${snapshot_chain[$j]}" "$new_backing_file" 367 | done 368 | done 369 | fi 370 | else 371 | print_v d "No backup directory specified" 372 | fi 373 | else 374 | print_v e \ 375 | "Snapshot for '$domain_name' failed! Exit code: $_ret\n'$command_output'" 376 | if [[ $command_output =~ "Permission denied" ]]; then 377 | print_v e "Check apparmor status or check if running with sufficient permissions" 378 | fi 379 | _ret=1 380 | fi 381 | 382 | if [ "$resume_vm" -eq 1 ]; then 383 | print_v d "Resuming domain" 384 | virsh resume "$domain_name" >/dev/null 2>&1 385 | if [ $? -ne 0 ]; then 386 | print_v e "Problem resuming domain '$domain_name'" 387 | _ret=1 388 | else 389 | print_v v "Domain resumed" 390 | trap "" SIGINT SIGTERM 391 | fi 392 | fi 393 | return $_ret 394 | } 395 | 396 | # Function: consolidate_domain() 397 | # Consolidate block devices for a domain 398 | # !!! This function will delete all previous file in the backing file chain !!! 399 | # 400 | # Input: Domain name 401 | # Return: 0 on success, non 0 otherwise 402 | function consolidate_domain() { 403 | local domain_name=$1 404 | 405 | local _ret= 406 | local backing_file= 407 | local command_output= 408 | local parent_backing_file= 409 | 410 | local dom_state= 411 | dom_state=$($VIRSH domstate "$domain_name" 2>&1) 412 | if [ "$dom_state" != "running" ]; then 413 | print_v e "Error: Consolidation requires '$domain_name' to be running" 414 | return 1 415 | fi 416 | 417 | local block_devices='' 418 | get_block_devices "$domain_name" block_devices 419 | if [ $? -ne 0 ]; then 420 | print_v e "Error getting block device list for domain '$domain_name'" 421 | return 1 422 | fi 423 | 424 | print_v d "Consolidation of block devices for '$domain_name' requested" 425 | print_v d "Block devices to be consolidated:\n\t${block_devices[*]}" 426 | print_v d "Consolidation method: $CONSOLIDATION_METHOD" 427 | 428 | for ((i = 0; i < ${#block_devices[@]}; i++)); do 429 | block_device="${block_devices[$i]}" 430 | print_v d \ 431 | "Consolidation of '$i' block device: '$block_device' for '$domain_name'" 432 | 433 | get_backing_file "$block_device" backing_file 434 | if [ -n "$backing_file" ]; then 435 | print_v d "Parent block device: '$backing_file'" 436 | snapshot_chain=() 437 | #get an array of the snapshot chain starting from last child and iterating backwards 438 | # e.g. [0] [1] [2] [3] 439 | # snap3 <- snap2 <- snap1 <- orig 440 | # 441 | # blockcommit: orig -> snap1 -> snap2 -> snap3 [becomes] orig 442 | # blockpull: orig -> snap1 -> snap2 -> snap3 [becomes] snap3 443 | #do this BEFORE consolidation so that we keep complete chain info 444 | get_snapshot_chain "$block_device" snapshot_chain 445 | 446 | # Consolidate the block device 447 | #echo "ABOUT TO RUN:" 448 | #echo "$VIRSH -q $CONSOLIDATION_METHOD $domain_name $block_device ${CONSOLIDATION_FLAGS[*]}" 449 | command_output=$($VIRSH -q "$CONSOLIDATION_METHOD" "$domain_name" \ 450 | "$block_device" "${CONSOLIDATION_FLAGS[@]}" 2>&1) 451 | if [ $? -eq 0 ]; then 452 | print_v v "Consolidation of block device '$block_device' for '$domain_name' successful" 453 | else 454 | print_v e "Error consolidating block device '$block_device' for '$domain_name':\n $command_output" 455 | return 1 456 | fi 457 | 458 | 459 | if [ "$CONSOLIDATION_METHOD" == "blockcommit" ]; then 460 | # --delete option for blockcommit doesn't work (tested on 461 | # LibVirt 1.2.16, QEMU 2.3.0), so we need to manually delete old 462 | # backing files. 463 | # blockcommit will pivot the block device file with the base one 464 | # (the one originally used) so we can delete all the files created 465 | # by this script, starting from "$block_device". 466 | # 467 | print_v d \ 468 | "Not deleting last element of snapshot_chain (top parent) since consolidation method='blockcommit'" 469 | unset snapshot_chain[${#snapshot_chain[@]}-1] 470 | else 471 | print_v d \ 472 | "Not deleting 0th element of snapshot_chain (last child) since consolidation method='blockpull'" 473 | snapshot_chain=("${snapshot_chain[@]:1}") 474 | fi 475 | #echo "Complete Chain=" ${snapshot_chain[@]} 476 | 477 | # Deletes all old block devices 478 | print_v v "Deleting old backing files for '$domain_name'" 479 | 480 | _ret=$? 481 | for ((j = 0; j < ${#snapshot_chain[@]}; j++)); do 482 | print_v v \ 483 | "Deleting old backing file '${snapshot_chain[$j]}' for '$domain_name'" 484 | rm "${snapshot_chain[$j]}" 485 | if [ $? -ne 0 ]; then 486 | print_v w "Could not delete file '${snapshot_chain[$j]}'!" 487 | break 488 | fi 489 | done 490 | else 491 | print_v d "No backing file found for '$block_device'. Nothing to do." 492 | fi 493 | done 494 | 495 | return 0 496 | } 497 | 498 | function libvirt_version() { 499 | $VIRSH -v 500 | } 501 | 502 | function qemu_version() { 503 | $QEMU --version | awk '/^QEMU emulator version / { print $4 }' 504 | } 505 | 506 | function qemu_img_version() { 507 | $QEMU_IMG -h | awk '/qemu-img version / { print $3 }' | cut -d',' -f1 508 | } 509 | 510 | 511 | # Dependencies check 512 | function dependencies_check() { 513 | local _ret=0 514 | local version= 515 | 516 | if [ ! -x "$VIRSH" ]; then 517 | print_v e "'$VIRSH' cannot be found or executed" 518 | _ret=1 519 | fi 520 | 521 | if [ ! -x "$QEMU_IMG" ]; then 522 | print_v e "'$QEMU_IMG' cannot be found or executed" 523 | _ret=1 524 | fi 525 | 526 | if [ ! -x "$QEMU" ]; then 527 | print_v e "'$QEMU' cannot be found or executed" 528 | _ret=1 529 | fi 530 | 531 | version=$(libvirt_version) 532 | if check_version "$version" '0.9.13'; then 533 | if check_version "$version" '1.0.0'; then 534 | print_v i "libVirt version '$version' support is experimental" 535 | else 536 | print_v d "libVirt version '$version' is supported" 537 | fi 538 | else 539 | print_v e "Unsupported libVirt version '$version'. Please use libVirt 0.9.13 or later" 540 | _ret=2 541 | fi 542 | 543 | version=$(qemu_img_version) 544 | if check_version "$version" '1.2.0'; then 545 | print_v d "$QEMU_IMG version '$version' is supported" 546 | else 547 | print_v e "Unsupported $QEMU_IMG version '$version'. Please use 'qemu-img' 1.2.0 or later" 548 | _ret=2 549 | fi 550 | #Issue 45 551 | if check_version "$version" '2.10.0'; then 552 | QEMU_IMG_SHARE_FLAG="--force-share" 553 | print_v d "$QEMU_IMG version '$version' will use $QEMU_IMG_SHARE_FLAG for file access" 554 | fi 555 | 556 | 557 | version=$(qemu_version) 558 | if check_version "$version" '1.2.0'; then 559 | print_v d "QEMU/KVM version '$version' is supported" 560 | else 561 | print_v e "Unsupported QEMU/KVM version '$version'. Please use QEMU/KVM 1.2.0 or later" 562 | _ret=2 563 | fi 564 | 565 | version=${BASH_VERSINFO[0]}.${BASH_VERSINFO[1]}.${BASH_VERSINFO[2]} 566 | if check_version "$version" '4.3.0'; then 567 | print_v d "Bash version '$version' is supported" 568 | else 569 | print_v e "Unsupported BASH version '$version'. Bash 4.3.0 or later is required for fi-backup > 2.1.1" 570 | _ret=2 571 | fi 572 | 573 | return $_ret 574 | } 575 | 576 | TEMP=$(getopt -n "$APP_NAME" -o b:cCm:s:qrdhvV --long backup_dir:,consolidate_only,consolidate_and_snapshot,method:,quiesce,all_running,dump_state_dir:,debug,help,version,verbose -- "$@") 577 | if [ $? != 0 ] ; then echo "Failed parsing options." >&2 ; exit 1 ; fi 578 | 579 | eval set -- "$TEMP" 580 | while true; do 581 | case "$1" in 582 | -b|--backup_dir) 583 | BACKUP_DIRECTORY=$2 584 | if [ ! -d "$BACKUP_DIRECTORY" ]; then 585 | print_v e "Backup directory '$BACKUP_DIRECTORY' doesn't exist!" 586 | exit 1 587 | fi 588 | shift; shift 589 | ;; 590 | -c|--consolidate_only) 591 | if [ $CONSOLIDATION -eq 1 ]; then 592 | print_usage "-c or -C already specified!" 593 | exit 1 594 | fi 595 | CONSOLIDATION=1 596 | SNAPSHOT=0 597 | shift 598 | ;; 599 | -C|--consolidate_and_snaphot) 600 | if [ $CONSOLIDATION -eq 1 ]; then 601 | print_usage "-c or -C already specified!" 602 | exit 1 603 | fi 604 | CONSOLIDATION=1 605 | SNAPSHOT=1 606 | shift 607 | ;; 608 | -m|--method) 609 | CONSOLIDATION_METHOD=$2 610 | CONSOLIDATION_SET=1 611 | if [ "$CONSOLIDATION_METHOD" == "blockcommit" ]; then 612 | CONSOLIDATION_FLAGS=(--wait --pivot --active) 613 | elif [ "$CONSOLIDATION_METHOD" == "blockpull" ]; then 614 | CONSOLIDATION_FLAGS=(--wait) 615 | else 616 | print_usage "-m requires specifying 'blockcommit' or 'blockpull'" 617 | exit 1 618 | fi 619 | shift;shift 620 | ;; 621 | -q|--quiesce) 622 | QUIESCE=1 623 | shift 624 | ;; 625 | -r|--all_running) 626 | ALL_RUNNING_DOMAINS=1 627 | shift 628 | ;; 629 | -s|--dump_state_dir) 630 | DUMP_STATE=1 631 | DUMP_STATE_DIRECTORY=$2 632 | if [ ! -d "$DUMP_STATE_DIRECTORY" ]; then 633 | print_v e \ 634 | "Dump state directory '$DUMP_STATE_DIRECTORY' doesn't exist!" 635 | exit 1 636 | fi 637 | shift;shift 638 | ;; 639 | -d|--debug) 640 | DEBUG=1 641 | VERBOSE=1 642 | shift 643 | ;; 644 | -h|--help) 645 | print_usage 646 | exit 1 647 | shift 648 | ;; 649 | -v|--verbose) 650 | VERBOSE=1 651 | shift 652 | ;; 653 | -V|--version) 654 | echo "$APP_NAME version $VERSION" 655 | shift 656 | exit 0 657 | ;; 658 | -- ) shift; break ;; 659 | * ) break ;; 660 | esac 661 | done 662 | 663 | if [ $ALL_RUNNING_DOMAINS -eq 1 ]; then 664 | print_v d "all_running_domains = '$ALL_RUNNING_DOMAINS' so all running domains will be backed up" 665 | fi 666 | 667 | # Parameters validation 668 | if [ $CONSOLIDATION -eq 1 ]; then 669 | if [ $QUIESCE -eq 1 ]; then 670 | print_usage "consolidation (-c | -C) and quiesce (-q) are not compatible" 671 | exit 1 672 | fi 673 | if [ $DUMP_STATE -eq 1 ]; then 674 | print_usage \ 675 | "consolidation (-c | -C) and dump state (-s) are not compatible" 676 | exit 1 677 | fi 678 | if [ $CONSOLIDATION_SET -eq 0 ]; then 679 | if check_version "$(qemu_version)" '2.1.0' && \ 680 | check_version "$(libvirt_version)" '1.2.9'; then 681 | CONSOLIDATION_METHOD="blockcommit" 682 | CONSOLIDATION_FLAGS=(--wait --pivot --active) 683 | fi 684 | fi 685 | fi 686 | 687 | if [ $DUMP_STATE -eq 1 ]; then 688 | if [ $QUIESCE -eq 1 ]; then 689 | print_usage "dump state (-s) and quiesce (-q) are not compatible" 690 | exit 1 691 | fi 692 | fi 693 | 694 | dependencies_check 695 | [ $? -ne 0 ] && exit 3 696 | 697 | DOMAIN_NAME="$1" 698 | 699 | if [ -z "$DOMAIN_NAME" ] && [ $ALL_RUNNING_DOMAINS -eq 0 ]; then 700 | print_usage " is missing!" 701 | exit 2 702 | fi 703 | if [ -n "$DOMAIN_NAME" ] && [ $ALL_RUNNING_DOMAINS -eq 1 ]; then 704 | print_usage "Setting all_running (-r) and specifying domains not compatible" 705 | exit 2 706 | fi 707 | 708 | DOMAINS_RUNNING= 709 | DOMAINS_NOTRUNNING= 710 | if [ "$ALL_RUNNING_DOMAINS" -eq 1 ]; then 711 | DOMAINS_RUNNING=$($VIRSH -q -r list --state-running | awk '{print $2;}') 712 | elif [ "$DOMAIN_NAME" == "all" ]; then 713 | DOMAINS_RUNNING=$($VIRSH -q -r list --state-running | awk '{print $2;}') 714 | DOMAINS_NOTRUNNING=$($VIRSH -q -r list --all --state-shutoff --state-paused | awk '{print $2;}') 715 | else 716 | for THIS_DOMAIN in $DOMAIN_NAME; do 717 | DOMAIN_STATE=$($VIRSH -q domstate "$THIS_DOMAIN") 718 | if [ "$DOMAIN_STATE" == running ]; then 719 | DOMAINS_RUNNING="$DOMAINS_RUNNING $THIS_DOMAIN" 720 | else 721 | DOMAINS_NOTRUNNING="$DOMAINS_NOTRUNNING $THIS_DOMAIN" 722 | fi 723 | done 724 | fi 725 | 726 | print_v d "Domains NOTRUNNING to backup: $DOMAINS_NOTRUNNING" 727 | print_v d "Domains RUNNING to backup: $DOMAINS_RUNNING" 728 | 729 | for DOMAIN in $DOMAINS_RUNNING; do 730 | _ret=0 731 | if [ $SNAPSHOT -eq 1 ]; then 732 | try_lock "$DOMAIN" 733 | if [ $? -eq 0 ]; then 734 | snapshot_domain "$DOMAIN" 735 | _ret=$? 736 | unlock "$DOMAIN" 737 | else 738 | print_v e "Another instance of $0 is already running on '$DOMAIN'! Skipping backup of '$DOMAIN'" 739 | fi 740 | fi 741 | 742 | if [ $_ret -eq 0 ] && [ $CONSOLIDATION -eq 1 ]; then 743 | try_lock "$DOMAIN" 744 | if [ $? -eq 0 ]; then 745 | consolidate_domain "$DOMAIN" 746 | _ret=$? 747 | unlock "$DOMAIN" 748 | else 749 | print_v e "Another instance of $0 is already running on '$DOMAIN'! Skipping consolidation of '$DOMAIN'" 750 | fi 751 | fi 752 | done 753 | 754 | for DOMAIN in $DOMAINS_NOTRUNNING; do 755 | _ret=0 756 | declare -a all_backing_files=() 757 | if [ "$BACKUP_DIRECTORY" == "" ]; then 758 | print_v e "-b flag (directory) required for backing up the shut-off domain '$DOMAIN'" 759 | print_v e "Skipping backup of '$DOMAIN'" 760 | _ret=1 761 | fi 762 | if [ $_ret -eq 0 ] && [ $CONSOLIDATION -eq 1 ]; then 763 | print_v e "Consolidation only works with running domains. '$DOMAIN' is not running! Doing full backup only of '$DOMAIN'" 764 | if [ "$DOMAIN_NAME" != "all" ]; then 765 | print_v e "Skipping consolidation/backup of '$DOMAIN'" 766 | _ret=1 767 | else 768 | print_v d "Doing full backup (not consolidation) of '$DOMAIN'" 769 | _ret=0 770 | fi 771 | fi 772 | 773 | if [ $_ret -eq 0 ]; then 774 | try_lock "$DOMAIN" 775 | _ret=$? 776 | if [ $_ret -ne 0 ]; then 777 | print_v e "Another instance of $0 is already running on '$DOMAIN'! Skipping backup of '$DOMAIN'" 778 | fi 779 | fi 780 | 781 | if [ $_ret -eq 0 ]; then 782 | get_block_devices "$DOMAIN" block_devices 783 | #print_v d "DOMAIN $DOMAIN $BACKUP_DIRECTORY/ $block_devices" 784 | for ((i = 0; i < ${#block_devices[@]}; i++)); do 785 | backing_file="" 786 | block_device="${block_devices[$i]}" 787 | print_v d "Backing up: cp -up $backing_file $BACKUP_DIRECTORY/" 788 | cp -up "$block_device" "$BACKUP_DIRECTORY"/ || print_v e "Unable to cp -up $block_device" 789 | get_backing_file "$block_device" backing_file 790 | j=0 791 | all_backing_files[$j]=$backing_file 792 | while [ -e "$backing_file" ]; do 793 | ((j++)) 794 | all_backing_files[$j]=$backing_file 795 | print_v d "Parent block device: '$backing_file'" 796 | #In theory snapshots are unchanged so we can use one time cp instead of rsync 797 | print_v d "Backing up: cp -up $backing_file $BACKUP_DIRECTORY/" 798 | cp -up "$backing_file" "$BACKUP_DIRECTORY"/ || print_v e "Unable to cp -up $backing_file" 799 | #get next backing file if it exists 800 | get_backing_file "$backing_file" parent_backing_file 801 | print_v d "Next file in backing file chain: '$parent_backing_file'" 802 | backing_file="$parent_backing_file" 803 | done 804 | done 805 | print_v d "All ${#all_backing_files[@]} block files for '$DOMAIN': $block_device : ${all_backing_files[*]}" 806 | _ret=$? 807 | unlock "$DOMAIN" 808 | fi 809 | done 810 | 811 | exit $_ret 812 | --------------------------------------------------------------------------------