Geoff Nordli <geo...@gnaa.net> writes: >> And finally is it neccessary to include anything but the vms home >> files? That is, something like /vb/vm/vm1 /vb/vm/vm2 .. etc where >> /vb/vm/vm[0-9] has all disks and other related files in each directory. >> >> Something like: ls /vb/vm/d0 >> Logs d0-0.vdi d0-1.vdi d0-2.vdi d0-3.vdi d0-4.vdi d0.vbox d0.vbox-prev >> >> Oh yes, and finally would it matter if I installed the newest VBox >> release as apposed to the 5.0.28 that the vms are currently running under? >> >> > Hi Harry. > > Yes, that will work fine. > > One thing to note, you probably want to separate out your VM storage > onto a separate zfs dataset. You can then snapshot and zfs send it to > another location. > > I use zvols and iscsi targets and connect using the vbox built-in iscsi > initiator. > > Another note, make sure the VMs are powered off. Upgrading vbox with > saved states is not a good idea.
Thanks for the input. About the zfs stuff. They are on their own dataset. Trouble with send/receive is I have no where to send to.. hehe. I could start a vbox vm of openindiana (solaris 11 offshoot) on a windows host and send to it, but seems like more trouble than tar would be. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ VBox-users-community mailing list VBox-users-community@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vbox-users-community _______________________________________________ Unsubscribe: mailto:vbox-users-community-requ...@lists.sourceforge.net?subject=unsubscribe
