Hardware Migration

[Former Member]

Dear All,

We are in progressing of Hardware Migration for All prod servers.

Below is the ECC system detail .

CI and DB are separate nodes and 4 App servers were installed.

ECC EHP5 6.0 , AIX , DB2

Active and Active cluster setup.

Now can you suggest how we can proceed a new system build on new hardware in with cluster environment ( CI and DB separate nodes with Active and active cluster setup )

thanks

[Former Member]

I'm not into DB2, but we once migrated a system using archive logs. Install you target system first, then restore a backup and don't start the database. Next step is to process all archived logs, when everything is recovered you can switch to the new environment.

[Former Member]

Dear All,

Additional point .

Currently we are in AIX 6.1 and DB2 9 version as well as hardware maintenance validity got expired hence we are going to hardware migration.

In the New hardware OS team will install latest version AIX 7.1.

Export/Import can possible since we are going upgrade DB2 latest version also .?

Pls suggest how we can proceed mainly production systems since Prod is currently cluster environment.

FYI :In dev and Qas , we are going use export/import ...

[former_member188883]

Hi John,

As you mentioned export/import is one of the options which when optimized can minimize the downtime on Production environment.

Second option which I could suggest is to perform offline backup restore and then perform in-place upgrade using db2se upgrade .

Found some links to guide you on this.

http://support.esri.com/en/knowledgebase/techarticles/detail/40798

http://www.dangerousdba.com/upgrading-from-db2-luw-9-7-to-10-1/

Hope this helps.

Regards,

Deepak Kori

[former_member188883]

Hi John,

What will be your target hardware environment ?

Regards,

Deepak Kori

[Former Member]

Sorry .

Target is same source system OS, DB and ECC EHP5 6.0 versions .

Note : Only hardware migration (IBM to Hitachi).

[MarcinOzdzinski]

Hi

Create same architecture on new hardware for cluster , same mountpoints , nfs etc.

Then two options:

First unsupported by IBM and SAP:

Just copy/attach  all /db2 /usr/sap /sapmnt filesystems , create manually user accounts (copy home directories) and groups  for db2sid, sidadm , sapadm etc. copy /etc/services , copy global registry file located in /var/db2/ install hostagents .... suggest to perform it twice : once in dry run then test if machines are working ok then in final switch ....

Second preferred by SAP:

via normall homogenous migration by restoring db2 backup using SWPM tool ....

[former_member188883]

Hi John,

My suggestion would be

1) install a fresh ECC 6.0 EHP5 system on new hardware.

2) Configure HA.

3) Restore backup from source to target system.

4) Perform recovery  and start database

5) Start application & apply license

6) Check Failover

7) release the system to users

Hope this helps.

Regards,

Deepak Kori

[Former Member]

John sat wrote:

Note : Only hardware migration (IBM to Hitachi).

What does this mean? Do you want to migrate on new Disk Subsystem only? Whether the server hardware remains the same?