search for: destination_host

...s , it results in different unit names on the destination hosts. Thus the migrated guest gets mapped to the wrong LUNs and is given the wrong disks. The problem is that the LUN numbers on the destination host and source host do not agree. Example, LUN 0 on source_host, for example, may be LUN 5 on destination_host. When the guest is given the wrong disk, it suffers a fatal I/O error. (This is manifested as fatal I/O errors since the guest has no idea that its disks just changed out under it.)The migration does not take into account that the unit numbers do match on on the source and destination sides. So, s...

...inutes). All machines are running rsync v2.5.6, and using ssh2 v3.2.3 as the transport rather than rsh. The commands used to rsync to both clients are exactly the same: /usr/local/bin/rsync -rltvR -e "/usr/local/bin/ssh2 -x" \ --size-only --delete <source_dir> <destination_host>:<dest_dir> The destination directory on both clients for the files/directories being mirrored is a samba share, the active share being on client A, and the backup(inactive) share on client B. The files in the share, and the samba share itself are set to be read only by th...