Hi all,
I am du to upgrade a cluster of 8 3300's, from MCD4 to MCD5, in the process performing RDN migration.
I have migrated a few 3300's before this is not my question, to speed up the process i was hoping to be able to perform an online upgrade to the same software release. So i had a pertition that is the same release, and i would use this partition to migrate, and if i experienced any issues,i could use the swap command to go back to the partition with the non-migrated database.
I have not done an online upgrade for a while, and only had a limited time to play so far, but from what i have seen, you either have to schedule the reboot/software activation using the SI tool, or reconnect with the SI tool when you want to activate the new load, but in between you activating the new load all changes to the DB will be lost it seems.
What i am planning to do is upgrade the inactive partition in hours. Then as soon as i get in out of hours, perform a swap command from the ESM, and activate the partition with the same load but then use this for migration, and then upgrade to MCD 5 after the migration is deemed ok.
I am aiming for some more lab time on this, but wanted some thoughts from those with recent real world experience of doing this.
Thanks all.
I am du to upgrade a cluster of 8 3300's, from MCD4 to MCD5, in the process performing RDN migration.
I have migrated a few 3300's before this is not my question, to speed up the process i was hoping to be able to perform an online upgrade to the same software release. So i had a pertition that is the same release, and i would use this partition to migrate, and if i experienced any issues,i could use the swap command to go back to the partition with the non-migrated database.
I have not done an online upgrade for a while, and only had a limited time to play so far, but from what i have seen, you either have to schedule the reboot/software activation using the SI tool, or reconnect with the SI tool when you want to activate the new load, but in between you activating the new load all changes to the DB will be lost it seems.
What i am planning to do is upgrade the inactive partition in hours. Then as soon as i get in out of hours, perform a swap command from the ESM, and activate the partition with the same load but then use this for migration, and then upgrade to MCD 5 after the migration is deemed ok.
I am aiming for some more lab time on this, but wanted some thoughts from those with recent real world experience of doing this.
Thanks all.