on 01-13-2011 1:54 PM
What would be the best approach to upgrade Contentserver MaxDB 7.5 on W2K server (32-Bit) to MaxDB 7.7 on Windows 2008 Server x64 (R2?)?
1. a) Upgrade MaxDB on the existing installation
b) Create a complete backup
c) Install latest release on new machine
b) recover with backup from existing installation on new machine
2. a) Create a complete backup from existing installation
b) Install same release on new machine
c) recover with backup from existing installation on new machine
d) upgrade to latest release on new machine
Both approaches share the problem that you have to run a OS/DB release constellation that is not released according to SAP PAM. The second approach has the advantage that the source system will not be touched and is still available in the original status if something fails. But the main issue is the compatibility question (7.5 not released for W2008, 7.7 not released for W2K)
Any suggestions?
Thanks,
Matthias
Hello Matthias
the MAXDB version 7.5 is not released on W2008, I recommend to go with 1 option.
Please see SAP Note No. 919224 , SAP Note No. 919225 and
SAP Note No. 1399009 - Content Server 6.40 on Windows Server 2008
Do you have Content Server 6.40 ?
Thank you and best regards, Natalia Khlopina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Natalia,
thanks for your answer.
> Do you have Content Server 6.40 ?
yes.
> the MAXDB version 7.5 is not released on W2008
neither is 7.7 on W2K.
> I recommend to go with 1 option.
Which would be this one:
>>1. a)Upgrade MaxDB on the existing installation
So can I upgrade to 7.7 on W2K though it is not released for this combination?
Best Regards,
Matthias
Hi Mathias,
after replying to your question in 'Recover Content Server MaxDB from a different DB release', let me add that if you are running at least MaxDB 7.5.00.50, you could directly backup/recover to 7.6 or 7.8. Personally, I think there is not much difference between upgrading from 7.5. to 7.5.00.50 and then recover to 7.6 on target system or upgrade from 7.5 to 7.6 and then recover on target system.
Best regards,
Thorsten
Thanks,
that answered my question
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jan,
on 64 bit Windows you should use a 64 bit database version (afaik 32 bit cannot even be installed on a 64 bit OS as the installer rejects ist).
64 bit or 32 bit does not matter for backups, this will always work.
But keep in mind that the recovery must be performed on a OS/processor type that is binary compatible to the backup (littel/big endian type), e.g. Windows and Linux usually are compatible (both little endian).
Thorsten
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.