On maandag 14 november 2011 16:15:42 Pablo Sanchez wrote: > > The other possibility is to `rsync' the .VDI. Restoring would be to > copy the .VDI back to the source. Again, the GUID may be tied to the > .VDI so if you re-create the VM, you'll need to ensure its GUID > reflects the original.
This is about what I do. I stop the VM, I rsync the three .VDI files to another system. On the other system I just recreated the VM using these three .VDI files as the disks of the new VM. Just make sure the other details of the VM are the same. Pay attention to the MAC address of the Ethernet interface. I have two definitions of an Ethernet interface in the original system. eth0 is linked to the interface in the original VM. The other eth1 in the original VM has no interface to link to in that system. But when starting that system in the second VM eth1 will be linked to the MAC address of the Ethernet interface in that system, so it gets the IP address defined with eth1. So you can have both systems active on a bridged network. The VM's are using a bridged interface. For testing I rsync the three .VDI files to a remote system, not on the same Ethernet. The created VM there gets an Ethernet interface with the same MAC address as the original VM, so when starting it gets the same IP address as the original VM, but it is a 192.168.x.x address. -- fr.gr. Freek de Kruijf ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
