How does vzmigrate work

Migration fails if this method is not available for some reason. It is useful to be sure that delay in service will be the smallest. Option that will perform only checks and will not perform actual data transfer.

Option that will force migrate of CT private from shared partition on non-shared. Utility can migrate either stopped or running CT. For stopped CT, simple CT private area transfer is performed rsync 1 is used for file transferring.

For running CTs the migration may be slow with minute or longer downtime , fast seconds of downtime or online zero-downtime. For the fast migration the kernel support for VZFS tracking is required. For the online migration kernel support of CPT is required. Utility also can migrate shared CTs, in this case it attempts to find suitable templates set coincides with one of source CT shared base CT on destination side, in case of failure it copies source shared base on destination side. BR rsync 1 ,.

For running CTs, the migration may be slow with a minute or more. Option doesn't affect CT that was stopped at the. Whether to remove private area on source node for successfully migrated. Private area will be saved with.

BR vz 5. Skip some or all checks on the destination node before performing migration. The argument is comma-separated set of checks to skip. B all. B technologies. B license. B rate. B bindmount. To prevent CT from filesystem errors due to absent template. Additional options that will be passed to ssh during establishing. Please be careful with these,. Override the cipher configured in the SSH configuration file.

Both the source and. Note, passing anything but a cipher. Keeper CT identification. The service CT ID is used if not. B --keep-dst. Don't clean synced destination CT private area in case of some. It is usefull to use this option on big CT migration to protect. B --keep-images. B --online. Perform online zero-downtime migration: during the migration the CT. B --keeper and. B --nostart. By default iterative scheme is used for online migration, that is most of the CT. This method introduces the smallest.

B --noiter. Do not use iterative scheme during online migration. B --readonly. Allows to skip locking the source container and writing any migration-related information to the source server. Use the option if the source server's filesystem is remounted as readonly e.

This configuration along the use of a SAN, gives interesting advantages when migrating containers that last so long at sincronization phase. If the same device is presented in both HN, we can skip sincronization phase.

Migration only have to unmount filesystem in source HN and mount the filesystem in target HN avoiding this way the copy of data. This parameter has only meaning if we share between HN the device over which container is set up. The issue has required a lot hard work for modifying vzmigrate to track undo actions when a error arises in the code. I felt free to reorganise undo actions in the function described on the following diagram. To overcome this:.

Jump to: navigation , search.