Jimįrom within a running Guest, you can run a backup application. Let’s not be argumentative with someone who’s trying to help you. > virtual disk file, not even with qcow2. > snapshots don’t ever create any separate files from the original > From what I read in other sites, internal > storage disk, settings, xml, etc, all under a same folder! > NOT the same as VirtualBox, which creates different separate files for > not, is it that settings get stored somewhere else? In both cases KVM is Probably all VM settings are stored within this file as well? If > inside the KVM storage pool directory I only see one file: the qcow2 one > For example, I currently have just one KVM guest, with no snapshots, and > All virtualization technologies being the same? WTH? That would sound > or whatever? What are you talking about!? > How do you even make backups “from guest itself”, “from host to guest” > had direct base on first one… at least that’s how I meant Did you even read question 1) ? Because question 2) > It would seem as if you only read exclusively the “best practices” part I would certainly prefer the separate files though… All snapshots are stored within same qcow2 file itself. Probably all VM settings are stored within this file as well? If not, is it that settings get stored somewhere else? In both cases KVM is NOT the same as VirtualBox, which creates different separate files for storage disk, settings, xml, etc, all under a same folder!įrom what I read in other sites, internal snapshots don’t ever create any separate files from the original virtual disk file, not even with qcow2. How do you even make backups “from guest itself”, “from host to guest” or whatever? What are you talking about!?Īll virtualization technologies being the same? WTH? That would sound illogical.įor example, I currently have just one KVM guest, with no snapshots, and inside the KVM storage pool directory I only see one file: the qcow2 one itself. Did you even read question 1) ? Because question 2) had direct base on first one… at least that’s how I meant It would seem as if you only read exclusively the “best practices” part of my first post. The important question isn’t what is the Best Backup method, but what backup methods should be chosen that are consistent with your Backup Strategy, and should be defined by your understanding of what a recommended Backup Strategy according to best practices. Lots and lots of choices, and they all work. You can do ordinary backups on the HostOS pointing at the Guests. You can do ordinary backups within the Guest But, of course since it will have its own identity, dependent applications won’t run the same or need modification. When you do this, you create a copy of your machine but with different settings which can run simultaneously with the original on the same network. Then you have all those other files which may or may not be important like memory files, lock files, more.Ĭlone a machine. Copying only a diskfile is possible, but did you copy all the diskfiles if there is one or more snapshots? BTW - Is one reason to merge snapshots ASAP when they’re no longer needed… many times snapshots won’t be recoverable or read in a recovery of any type. Same applies to all virtualization technologies, there is no difference for example between VBox and KVM… The directory will contain the necessary files plus possibly some unnecessary to run. What if I need to copy directly to a USB stick or external hard disk? Wouldn’t it be highly insecure to access any external storage as root?Īnd for some reason I feel modifying ownerships and/or permissions would somewhat break virt-manager (not to mention some security flaws?) What would be a “best practice” to be able to backup VM? Or is it that the only one supposed to do any KVM related stuff is root indeed? So by default it doesn’t allow to copy the VM as normal user.Īre such ownership and permissions certainly default behavior of virt-manager? So inside is the VM file, but it was created with permissions “root:root -rw-”. Of course I manually created the directory beforehand. Thing is, for almost obvious reasons, I created the VM in a different storage pool than the default one: a directory called “VirtualMachines” just inside home directory. Reviewing some past threads I read one common way to backup a VM is just copying the entire VM file similar to VirtualBox except that here one copies an entire directory instead of a single file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |