03-20-2014 04:17 AM
I'm planning a much-needed upgrade of my DP environment, going from 6.20 on a W2K3 32-bit cluster to 7.0 on a W2K8 R2 64-bit cluster.
I had originally considered going straight to 8.1 but it became clear that that wouldn't be possible as W2K3 isn't supported.
So my plan was to upgrade to 7.0 on my current system, then transfer and convert the IDB for 64-bit on the new platform in line with the steps in the Installation Guide. However, a check of the Support Matrix suggests that DP7.0 doesn't support 32-bit W2K3.
Can anyone suggest how best to approach this problem?
Is it possible to integrate IDB files from a 6.20 IDB into a 7.0 (or 8.1) installation?
Any advice would be welcome...
03-20-2014 09:47 AM
You are right, at first, I looked at the support matrix:
click on 'Platform and Integration Matrix', this shows the following are supported as Cell Managers and Installation servers
Windows 7 (32-bit)
Windows Server 2003 (64-bit) (x64)
Windows Server 2008 (32-bit) <<<<<<<
Windows Server 2008 (64-bit) (x64)
Windows Server 2008 R2 (64-bit) (x64)
Windows Server 2012 (64-bit) (x64) 14
HP-UX (PA-RISC) 6 11.31 HP-UX (Itanium)6 11.31
Red Hat Enterprise Linux (RHEL) 4 5.x, 6.0, 6.1, 6.2, 6.3 (64-bit) (x64)
SUSE Linux Enterprise Server 10, 11 (64-bit) (x64)
Then, I noticed that the indicated line was for Windows 2008 32-bit. I was hoping that W2003 might be the same as Windows 7, but some research shows that Windows 2003 is actually equivalent to Windows XP
I think that your best bet would be to either do a IDB backup of your existing DP to tape, Install DP 7.0 on your W2K8 cluster, connect a tape drive to the new server, create a device, and import the tape, and do the IDB restore. I don't think that there was a major change to the IDB between 6.2 and 7.0
I would not updating to DP 8.1 at this time, there are just too many issues with it. I'm not sure I would advise an upgrade to 8.0 either
Whatever version of DP you upgrade to, plan so that you can go back to the previous version of something fails
03-21-2014 04:03 AM
Thanks for the advice - looks like an IDB restore or file migration might be the way to go alright.
I've had to transplant a database before, to a test environment, so I might give that a go before a tape-based recovery.
My plan in such a case would be to:
- Run a full maintenance of my IDB, including a writedb / readdb;
- Back it up;
- Take a copy of \db40, leaving services stopped;
- On the W2K8 cluster, stop services and copy the \db40 files to a safe location;
- Copy in the files from the 32-bit instance;
- Start the W2K8 services;
- Convert the files for 64-bit operation (would this be the correct point?)
- Check operation.
This will be my first upgrade to a new platform - in previous instances I've simply upgraded in place - so I'm wondering if I'll need to worry about things like IP addresses or the cluster and Cell Manager ID?
If it was to be a direct upgrade, in place, the names and IP addresses would be retained; however in this instance my IPs will definitely change, and importing the old IDB will bring the 32-bit Cell Manager's identity with it, will it not?
Looks like it's going to take some careful planning...
03-21-2014 04:54 AM
your plan should work, but do not start dp services on the w2k8 box until you did run the winomnimigrate command. -> you need to convert idb first from x86 to x64, then start the dp services on the new host.
you could also have a look at the install paper. there the migration scenario is also described
03-21-2014 06:55 AM
Hi Andre - thanks, the 32- to 64-bit conversion part was a concern.
I'll plan accordingly...