upgrading from V9 to V11

[gk]

We are intending to upgrade from V9 to V11 very shortly. Should I be scared? Is there anything I need to particularly worry about or watch out for?

[Share Tech News]

No need to worry. We did the upgrade and faced no problem. You can migrate to Management Server 11.0 only from Management Server 10.1 SP2. For migration of installations of versions of Management Server (or RedDot CMS) older than 10.1 SP2 it is required first to migrate the installation to Management Server 10.1 SP2.

[gk]

Thanks. It's reassuring to know someone else has done it with no problems.

[efwe]

We did a migration from 7.5 to 11 via project export/import. No Problems.

[Jian Huang]

Hi,

Please see https://groups.google.com/forum/?fromgroups#!searchin/reddot-cms-users/upgrade$20jian/reddot-cms-users/o6-v58xnKho/niV0juFmo5AJ[1-25]

Best of luck,

-Jian

[Tim D]

Also check out the information on KC.  https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=22633196&objAction=browse&sort=name 

Project export and import is generally preferable as it helps reduce DB sizes in the new environment, there is an OS/CPU architecture change. If your exports take a long time try deleting your publication reports ( a tip I heard worked for another customer recently )

[Morgan Ritchings]

Hi Tim,

Any tips on maintaining the audit trail for ldap based users when export/importing to a new system? Last time i checked ldap users will be created with a different guid on the new system on import leading to this information being lost e.g. last changed user reported as "unkown user"? We've been recommending the migration approach ever since for this reason.

 - Morgan

[Tim D]

Morgan,

Good point, if you source your users from LDAP this info would be lost. If you use the info element for authors in pages or want to preserve this audit trail this would be a significant concern. Especially if you are moving database servers, then it might be better just move the databases then just spin up your new v11 environment and connect to existing "new" database server. To reset your transaction log size at any point where you have good backups with MSSQL you can switch to simple logging mode, truncate and shrink you logs, then return to full logging. 

The more complex the scenario the more it may not be best served by general high level guidance and consulting with partners or OpenText Professional Services may be advisable for planning or executing a move if you have concerns.

Best,

Tim

[Tim D]

By this I meant replicate your whole DB io_applicaiton io_administration and all project databases to the new DB server, moving a couple tables isn't reliable as DBs can change significantly between versions. Support can be helpful with more detail.

On Monday, September 10, 2012 9:20:02 AM UTC-4, Jaime B wrote:

Hi there Tim, can you explain:

Especially if you are moving database servers, then it might be better just move the databases then just spin up your new v11 environment and connect to existing "new" database server.  

I'm thinking it may be possible to just import the old io_usr to preserve user guids, is this what you are suggesting?