• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer
TSB Alfresco Cobrand White tagline

Technology Services Group

  • Home
  • Products
    • Alfresco Enterprise Viewer
    • OpenContent Search
    • OpenContent Case
    • OpenContent Forms
    • OpenMigrate
    • OpenContent Web Services
    • OpenCapture
    • OpenOverlay
  • Solutions
    • Alfresco Content Accelerator for Claims Management
      • Claims Demo Series
    • Alfresco Content Accelerator for Policy & Procedure Management
      • Compliance Demo Series
    • OpenContent Accounts Payable
    • OpenContent Contract Management
    • OpenContent Batch Records
    • OpenContent Government
    • OpenContent Corporate Forms
    • OpenContent Construction Management
    • OpenContent Digital Archive
    • OpenContent Human Resources
    • OpenContent Patient Records
  • Platforms
    • Alfresco Consulting
      • Alfresco Case Study – Canadian Museum of Human Rights
      • Alfresco Case Study – New York Philharmonic
      • Alfresco Case Study – New York Property Insurance Underwriting Association
      • Alfresco Case Study – American Society for Clinical Pathology
      • Alfresco Case Study – American Association of Insurance Services
      • Alfresco Case Study – United Cerebral Palsy
    • HBase
    • DynamoDB
    • OpenText & Documentum Consulting
      • Upgrades – A Well Documented Approach
      • Life Science Solutions
        • Life Sciences Project Sampling
    • Veeva Consulting
    • Ephesoft
    • Workshare
  • Case Studies
    • White Papers
    • 11 Billion Document Migration
    • Learning Zone
    • Digital Asset Collection – Canadian Museum of Human Rights
    • Digital Archive and Retrieval – ASCP
    • Digital Archives – New York Philharmonic
    • Insurance Claim Processing – New York Property Insurance
    • Policy Forms Management with Machine Learning – AAIS
    • Liferay and Alfresco Portal – United Cerebral Palsy of Greater Chicago
  • About
    • Contact Us
  • Blog

Documentum Upgrade – Inplace or Migration

You are here: Home / Documentum / D6 / Documentum Upgrade – Inplace or Migration

September 29, 2009

For many Documentum customers, deciding how to upgrade a Documentum system often boils down to whether or not to upgrade in-place with a clone or just leave the environment alone and upgrade it in-place on the existing hardware. This year, I worked with a client on a project to explore the differences between upgrading several Documentum systems in place versus migrating the documents straight to a new 6.5 installation. Many of the in-place upgrade complexities were due to the older database and OS.

  • Oracle needed to go from 9i to 10.2.03 as well as be converted to UTF-8
  • The Unix OS needed a significant upgrade, including the rack supporting the virtual partitions
  • The Documentum Content Server required several upgrade steps. It needed to go from 5.2.5 (some 5.2) to 5.2.5 SP5, then 5.3 SP6, and finally to 6.5. I then did a separate upgrade to 6.5 SP2.

There were several project goals that could only be achieved with a migration strategy.

  • Combine Repositories on Windows installation and move to a single UNIX installation
  • Reorganize object model by flattening object hierarchy
  • Undo custom folder configurations created many years ago

The technical complexities of upgrading in-place from 5.2.5, and the need to merge Documentum repositories, led the client to pick a migration approach for the upgrade

Based on TSG’s upgrade experience with this client and others, we created an upgrade planning guide.

The planning guide is available here.

Please let me know your thoughts below.

Filed Under: D6, D6.5, Documentum, OpenMigrate, R&D, Upgrades Tagged With: Migration, Upgrade

Reader Interactions

Comments

  1. Jazz says

    February 4, 2010 at 12:08 am

    Hi

    Thanks for the information.

    I am little bit confused with the Migration and Upgradation may i know the exact difference between these

    Thanks
    Jazz

    Reply
  2. George says

    February 5, 2010 at 10:08 am

    Hi Jazz. When we’re talking about a Documentum upgrade, we mean when you want to move to a newer version. For example, currently a lot of Documentum customers are upgrading from 5.3 SPx to D6.5 SP2. A migration means moving (or migrating) objects from one environment to another.

    An upgrade can involve a migration, but doesn’t necessarily need to. If you’re upgrading with a migration, you would need to set up a separate environment with the new software on it, and then move the objects from the old environment to the new. An upgrade without a migration is called an “in place” upgrade. In an in place upgrade, you update the software on the old servers to the new version. There are pros and cons to both approaches. The post above goes over how we analyzed a client’s environment to decide whether to use a migration or in place strategy for the upgrade.

    Also, a migration doesn’t necessarily need to be tied to an upgrade. For example, there may be needs to migrate documents from one Documentum repository to another, or from a server file system to Documentum, or the other way around.

    If you’re interested in using an automated tool for migrations, check out our OpenMigrate offering:

    https://tsgrp.wpengine.com/Open_Source/OpenMigrate/open-migrate.jsp

    Hope this helps!

    Reply
  3. ROX says

    February 23, 2010 at 8:55 pm

    I want to use Repository miration approach to migrate my up and running D5.3 application/repository to another up and running D6.5 content Server.

    What approach should I follow.
    Can I create a new repository on D6.5 environment and then copy my D5.3 repository content on the setup and go for an upgrade.(Provided It allows me to do that)
    Or how can I make my existing D5.3 repository contents compatible to D6.5 setup without upgrading my existing D5.3 environment.

    Kindly suggest.

    Reply
    • chris3192 says

      February 25, 2010 at 8:06 am

      Hi ROX.

      Your first approach can be modified some to be a clone and upgrade approach. With a clone approach, you would create an identical copy of your 5.3 repository and content server on new hardware. You then walk the clone through the in-place upgrade steps to reach 6.5. At that point you can turn-off the 5.3 repository and just use the 6.5 repository.

      One thing to note is that you need to do the switch during an outage period or you could end up with users adding content to the 5.3 repository after you’ve made the clone. If that happens you’ll end up missing that content in the 6.5 upgrade.

      Your other question of how to make the existing 5.3 repository contents compatible with 6.5 is interesting. Outside of an upgrade path or explicitly copying/migrating content from 5.3 to 6.5 I do not know of a way to upgrade from 5.3 to 6.5. You can copy/migrate data from a 5.3 repository to a 6.5 repository through the Documentum API. If you are interested, our TSG OpenMigrate product does this, https://tsgrp.wpengine.com/Open_Source/OpenMigrate/open-migrate.jsp

      I hope this helps!
      Christine

      Reply

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

Search

Related Posts

  • Documentum Full Text Search with Lucene – Honoring ACL Security
  • Documentum Upgrade – High Volume Server – A Basic Understanding
  • Documentum 6.5 Upgrade – Character Encoding Issues
  • Migrating From Documentum with OpenMigrate: Best Practices
  • Documentum – What’s Next Updated for 2010
  • Documentum Search – Lucene, FAST, Verity, Google and upcoming DSS
  • Documentum Migration – Buldoser and OpenMigrate – Folders versus Nodes
  • TSG Open Source Product Plans
  • Supersized Documentum Migrations and Upgrades Two Billion Documents and Counting
  • Documentum 6.7 Upgrades and Hardware Changes

Recent Posts

  • Alfresco Content Accelerator and Alfresco Enterprise Viewer – Improving User Collaboration Efficiency
  • Alfresco Content Accelerator – Document Notification Distribution Lists
  • Alfresco Webinar – Productivity Anywhere: How modern claim and policy document processing can help the new work-from-home normal succeed
  • Alfresco – Viewing Annotations on Versions
  • Alfresco Content Accelerator – Collaboration Enhancements
stacks-of-paper

11 BILLION DOCUMENT
BENCHMARK
OVERVIEW

Learn how TSG was able to leverage DynamoDB, S3, ElasticSearch & AWS to successfully migrate 11 Billion documents.

Download White Paper

Footer

Search

Contact

22 West Washington St
5th Floor
Chicago, IL 60602

inquiry@tsgrp.com

312.372.7777

Copyright © 2023 · Technology Services Group, Inc. · Log in

This website uses cookies to improve your experience. Please accept this site's cookies, but you can opt-out if you wish. Privacy Policy ACCEPT | Cookie settings
Privacy & Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Non-necessary
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
SAVE & ACCEPT