Description of problem: HE-to-HE migration could lead to stale SPM or duplicating SPM_IDs. To prevent that, two steps should be done: * Before migration manually set SPM host to any of non-HE hosts. * After migration old HE hosts should be redeployed as soon as possible. Those steps above should be documented.
We don't have a guide for HE-to-HE today? Can you provide the info on the flow for this process? What is the use case?
I'm not sure if we have a HE-to-HE guide today. Possible use cases are listed my Simone in BZ1417518. Let me copy them here: Migrating from an NFS based hosted-engine deployed to an iSCSI one or from an iSCSI LUN to one on different target and so on (just because you have to decommission the storage you are using for hosted-engine) without the need to power-down the whole datacenter. We already have different users asking for this; customers are also asking to backport to 4.0.
We will use bug 1420604 to track items related to SHE backup and restore (and migration), and use the information in this bug's description to ensure that migration prerequisites are covered. Closing as duplicate. *** This bug has been marked as a duplicate of bug 1420604 ***
(In reply to Denis Chaplygin from comment #0) > * After migration old HE hosts should be redeployed as soon as possible. If we recommend to switch the old HE hosts to maintenance mode before starting the procedure it would be safer, wouldn't it? It would release their locks, right?
Yes. Putting them to the maintenance mode in prior is the best way to do migration.