IGA Suite v15 – Database Migration Approach

[Rinat Matityahu]

Hi All

With the adoption of IGA v15 increasing, a common query to many (most) of the customers planning the migration is related to the database migration - what are the options for such a migration, pros and cons etc.

We have therefore created the attached document, aimed to assist with this query.

Please feel free to comment, ask, correct and add your requests for missing information, as we do plan for this document to be updated over time.

Regards

Rinat

Client Services Consultant – Customer Engagement

Broadcom Software

-------------------------------------------

Attachment(s)

Approach to database migration in IGA R15.pdf   87 KB 1 version

[William Cheang]

Hi Rinat,

Thank you for the database migration pdf. Beside database migration, how about migration strategy current Production env with 3 nodes cluster ? 

1. Migrate all 3 nodes r14.5 to R15 ?
2. Migrate 1 node(r14.5) to R15 node, then 2nd new node(R15) & 3rd new node(R15) join to new R15 cluster ? 

regards,

William

-------------------------------------------

[Rinat Matityahu]

Hi William

Are you planning to utilize any of the hardware used with 14.5 in the new r15 setup (assuming non vApp is the source)?

When we think about it, the new deployment model requires us to install IGA Xpress v15 to begin with (on any number of nodes) and we then extract the data captured by mogrify into this new r15 deployment. When running the mogrify tool, we first extract data from all available services (IM / IP / IG / US / IMPS / IMPD / JCS) which we would then restore in the new setup - in any layout that we choose to. There is no dependency between the way / location services were implemented in 14.x and the new v15 architecture. We can add / remove nodes as well as deploy services on different nodes.
If you require any further clarifications on this topic, please let us know

Regards
Rinat    

-------------------------------------------

[William Cheang]

Hi Rinat,

We are using virtual appliance for 14.5 with 3 nodes, we will not utilize old VM hardware. New R15 will be in new VM hardware and different network segment.

I think best way is to migrate the 1 node (r14.5) to 1 node (R15), then verify the data been migrated.

If data migrated is verified correct, then we perform join 2nd & 3rd node into cluster then verified data is sync across other nodes.

Q. With the above migration way, once all the new R15 nodes is sync successfully, then  we will perform patching all nodes to latest R15.0.x version, right ? 

Regards,

William

[Rinat Matityahu]

Hi  William

We believe watching the training video on Mogrify (available via https://brocade.csod.com/samldefault.aspx?ouid=12285&returnUrl=%252fDeepLink%252fProcessRedirect.aspx%253fmodule%253d365) would make things clearer when it comes to migrating data from 14.x. It is an 11 min video so shouldn't take too long to go through it.

We run the mogrify utility on all nodes (in turn, one at a time), extracting configuration from all services and then restoring the complete exported bundle into r15. You stated your plan was to migrate node1, verify then proceed to node2 etc. The migration utility is meant to collect data anc configuration from all nodes, then restore the collection into r15.

Please view the training specified and we are here to answer any follow up questions regarding the migration to r15.

Regards

Rinat

-------------------------------------------

[William Cheang]

Hi Rinat,

Will take a look, thank you.

regards,

William

-------------------------------------------