Debian P2V - Historique des versions

Philippe le 11 mars 2008 à 11:34

2008-03-11T11:34:31Z

Philippe : /* Synchronise */

2008-03-11T10:59:08Z

‎Synchronise

Philippe : /* Prepare */

2008-03-11T09:51:37Z

‎Prepare

Philippe le 10 mars 2008 à 22:28

2008-03-10T22:28:48Z

Nouvelle page

Debian Physical to Virtual -- Brain dump; this is very basic...

= Prepare =
Create the Debian Virtual Machine which will receive the Physical Machine data
{{Boite Code|shell|2=<nowiki></nowiki>
xen-create-image --hostname=...}}

= Synchronise =
Synchronize data at any time:
{{Boite Code|shell|2=<nowiki></nowiki>
mount /dev/<path to disk image> /mnt
rsync \
--verbose \
--archive \
--numeric-ids \
--hard-links \
--exclude=/tmp \
--exclude=/proc \
--exclude=/dev \
--exclude=/sys \
--compress \
--rsh=ssh \
<physical machine>:/ \
/mnt/
umount /mnt}}

Note: if the ''--delete'' option is used, we need to re-add the modules from the Xen Kernel afterwards...

= Migrate =
# Shutdown all services but ''ssh'' on the source server
# Synchronize (as above)
# Free / change IPs from the source server
# Mount / chroot to the disk image
#* Install ''libc6-xen''
#* Cleanup fstab
#* ...
# Unmount the image
# Start the VM
# Configure for pygrub

@@ Ligne 1: / Ligne 1: @@
-Debian Physical to Virtual -- Brain dump; this is very basic...
+[http://www.debian.org Debian] Physical to Virtual migration.<br />
 = Prepare =
@@ Ligne 10: / Ligne 11: @@
 At this stage we use temporary IP addresses to avoid conflicts.
-= Synchronise =
+= Synchronise and test =
 To minimize downtime for the actual migration, one can synchronize the data beforehand:
 {{Box Code|shell|2=<nowiki></nowiki>
@@ Ligne 30: / Ligne 32: @@
-{{Box Note|This is to be refined and tested. To have an exact copy of the Physical Machine, we should use the ''--delete'' option if we synchronize multiple times; but that would also delete the files from our pre-seeded Xen Environment.<br>
+{{Box Note|This is to be refined and tested. To have an exact copy of the Physical Machine, we should use the ''--delete'' option if we synchronize multiple times; but that would also delete the files from our pre-seeded [[Xen]] environment.<br>
 As far as I can see, the only files we really need to keep are the kernel modules, but that needs to be confirmed.
 }}
 = Migrate =
-# Shutdown all services but ''ssh'' on the source server
+# Shutdown all services but {{Commande|sshd}} on the source server.<br />I actually boot in ''maintenance mode'' and start {{Commande|sshd}} manually.
-# Synchronize (as above)
+# Synchronize the data (see above).
-# Free / change IPs from the source server
+# Change the IP addresses on the physical server, as we want to keep the current IP addresses for our migrated server.
-# Mount / chroot to the disk image
+# Mount the disk image and ''chroot'' it as described above. We need to:
 #* Install ''libc6-xen''
-#* Cleanup fstab
+#* Cleanup {{Fichier|/etc/udev/rules.d/z25_persistent-net.rules}}
-#* ...
+#* Cleanup {{Fichier|/etc/fstab}}
 # Unmount the image
-# Start the VM
+# Start the virtual machine
 # Configure for pygrub

@@ Ligne 11: / Ligne 11: @@
 = Synchronise =
-Synchronize data at any time:
+To minimize downtime for the actual migration, one can synchronize the data beforehand:
-{{Boite Code|shell|2=<nowiki></nowiki>
+{{Box Code|shell|2=<nowiki></nowiki>
   mount /dev/<path to disk image> /mnt
   rsync \
@@ Ligne 29: / Ligne 29: @@
   umount /mnt}}
-Note: if the ''--delete'' option is used, we need to re-add the modules from the Xen Kernel afterwards...
 = Migrate =