If you know of any other techniques, please feel free to email me. I’ll finish covering the third and fourth moves next issue. This issue, I’ll look at the first two techniques. IBM‘s live partition mobility might be another example of this type of cloud-related migration. Many SANs including the IBM Storwize V7000, have flash-copy capabilities where you can flash a copy of an existing partition to another SAN. Using flash copy or another SAN technology to move a machine between connected networks.Working with your HA vendor to replicate your machine to a different partition and then switch over to that partition to complete the migration. Replicate to a different location using high availability (HA) software.
This move still requires a cut-over period and it requires additional configuration. This technique allows you to run both old and new systems at the same time and to test one installation against the other before cutting over. Restore to a new location using a different system name.This is a traditional restore where you take the old system down one night and bring it up on another system the next day. Restore the partition in place or to a new location using the same system name.In general, there are four techniques for moving an IBM i partition to a different machine: While there are several ways to approach migration, over the next two issues I’ll discuss four specific techniques for moving an IBM i partition to a new location and the different tasks you have to perform for each technique. I’m currently working with a client to migrate three IBM i partitions to new Power 7+ machines located in two data centers in different states. Admin Alert: Four Ways To Move An IBM i Partition, Part 1
0 kommentar(er)
