Upgrade to 6.7 SP1

Hi,

We are currently upgrading our content server from 6.5 SP3 to 6.7 Sp1

we have 5 repositories and one content server .

Our DEV operating system is 2008 SP2 and as per the requirements of 6.7 SP1 the OS need to be 2008 R2 SP1

Our systems team mentioned that they cannot in-place upgrade from 2008 SP1 to 2008 R2 SP1 , They will provide a new machine with 2008 R2 and clone the drives from the old content server machine ( 2008 Sp2 ) . My question is that , will it work fine if they do it like this ?

Find more posts tagged with

Documentum

API

Comments

pettitk

Clone the drives? Not sure how they will remedy the registry settings, etc and make the new OS aware of all previous installs. There is typically some footprint of dctm files on the c drive too, even though you specify to another drive, etc. Without knowing more about how your systems are setup and were installed, I would say you will be missing registry and knowledge of the installs. When I have a new machine, I typically just clone Documentum to that. There are numerous forum entries and docs on how to clone Documentum. Essentially, you install a fresh a system of Documentum, exactly as the old one, down to each repository name, etc. shutdown all repositories and clone data directories. Make sure the databases point to the correct databases, etc. In either case, if the hostnames changes, you have to run a series of SQL updates. Also documented… If you can’t find the steps, I can email later.

-Kyle Pettit

T_G

Following are the 3 Windows OS supported for Content Server 6.7 sp1.

Windows Server 2008 SP2 (32-bit version)

Windows Server 2008 SP2 (64-bit version) x64

Windows Server 2008 R2 SP1 x64 Edition

I think you are already on the supported OS.

tsg_dave

Your system team is correct that you can't inplace upgrade Windows so a clone is the Documentum recommended approach.

We just wrote a blog about the upgrade process:

http://blog.tsgrp.com/2012/07/27/documentum-6-5-to-6-7-upgrade-lessons-learned/

Can't really comment on "will it work fine" - the approach seems valid. One of our biggest issue was the Lucene upgrade - everything needs to be reindexed - so make sure you allocate the time - our with 3.5 million took 40 hours and it crapped out halfway through due to memory issues on indexing server. We added more memory and had to restart.

Dave