Академический Документы
Профессиональный Документы
Культура Документы
ENSURE IN AN ECM
UPGRADE/MIGRATION
Aakash Sharma
Lead Engineer Documentum, ECMP, HCL Technologies India
Introduction
With content management now more important than ever, and with
the sheer, nearly choking amounts of data now being stored by
companies worldwide, data migration has become one of the hottest
market segments of the information technology (IT) industry.
• Make sure the count and size estimations are inclusive of all
versions and rendtions of a document. E.g there may be tiff
renditons of a document that are to be migrated across and tiffs
are generally bigger in size
Before the content is extracted from the old system the users who are
currently working on the documents would need to complete their tasks and
check-in all such documents back in to the System. This is normally
referred to as ‘freeze-point’.
So we can say that it’s best to put a freeze point at the time you are ready.
Remember, the longer the freeze, the harder it will also be to restart and
re-engage the content authors and owners.
As we discussed there are time lags between the production migration and
migration on to preproduction and test systems. To over come this we
followed an approach of ‘Delta Migration’. This approach suggests that the
moment you are ready with the migration on to the test or preproduction
system make an extract of documents from the repository. However this
doesn’t mean putting up a freeze point on to the old system. The end-users
can continue to work in normal manner with out knowing what’s going
behind the scenes (Obviously for their better!!)
Once all tests have completed on preproduction system, all issues have
been resolved and a green signal has been given for production migration
we would put up a freeze point on the old system. No further modifications
on old stuff we are moving to the new system. But then what we gain out of
it wouldn’t it take same amount of time to take the dump again and load in
to the production system. But here we can use our old dumps that we used
for pre-production. But what you say lot of documents may have been
changed and new documents added in to the system between the
preproduction and production dates. Yes you are correct and precisely that’s
what Delta Migration Approach targets to achieve. During the delta
migration we would make an extract of only those documents that have
been modified or newly created between the dates of preproduction and
production migration (i.e the current date). Infact, the freeze point can be
delayed to the point when we have migrated the old dumps used in
preproduction in to the production system. Normally this would account for
almost 90% of the content that is to be migrated across. Then we would put
up a freeze point on the old system extract the rest 10% of the data and do
the loads in the production. This should be a weekend activity. Thus users
can get back to their normal work on Monday itself if you had put up a
freeze point last Friday.
• Maintain migration Details – Fill in all the required steps needed before
starting migration of a batch in the form of checklist. This checklist helps to
ensure all team members of migration stream are following all required
steps. Also ensures you have documented all the necessary account names
and passwords, and estimate needed disk space. During migration maintain
sheets for the loads like start time, end time, batch size etc. It is a little
dated, but still relevant and helpful.
• Connectivity and disk space – Verify that the connectivity among the
Servers and other devices involved in the migration/upgrade is adequate
(i.e. Bandwidth is sufficient to move large amounts of data) and that
enough free disk space is available for the temporary storage needed during
the migration.
• Verify downtime – Verify that your planned downtime for the migration is
adequate and well advertised to the users. You may want to do some
testing by copying large files across the network to gauge transfer rates.
You should also plan your migration during a time when it will impact your
customer the least. This usually means at night or over the weekend, but
make contingencies plan for it takes longer and overlaps expected
operational hours.
Case 1
The first case is very simple: there is a Content Server, the database
server and the content files all on a homogeneous hardware platform. We
need to move the Content Server to a more modern, powerful and robust
platform. There is no need to change operating systems, hardware
architecture, or Content Server versions. All we really want to do is clone the
existing Docbase to the new hardware platform quickly and easily.
Challenge
The challenge in this scenario is how to make this migration quick, easy and
complete. We would also want to do it with minimal monetary investment in
software tools.
Approach
In this scenario our prime objective is to ensure that the System function
smoothly in the same way as before the transition to new hardware platform.
The first approach to this scenario should be to look for any native tool that
could meet this challenge.
In case of Documentum we can opt for Dump and Load operations. However,
before using any such tool make sure to go through with the latest releases
of Content Server and the features of such a tool. Many a times tools like
Dump and Load can miss several very important object types like workflow
instances, Object types without any instances, registered tables etc. Be
aware of short comings of such default tools before attempting a migration
using them.
Make sure to run Consistency Checker and other jobs to know the state of
the system after the migration. Resolve any issues identified by the
Consistency Checker. Compare the State of the System through audit or
other reports in the new environment. Do some basic operations on the
migrated content to identify any inconsistencies in the new system. This
comparison should be a good indicator of the thoroughness of your migration
and state of the new system.
The bottom line with this approach is that it is simple and utilizes built-in
Capabilities and tools. However, there could be some potentially serious
drawbacks to using such an approach that you should be aware of before
attempting.
Alternate Approach
Alternatively, if the migration described by this scenario is really just a
Virtualization of your existing Content Server, then a simpler approach could
be to use VMware’s Converter utility. The Converter utility will create an
exact copy of a physical system in a VMware image
Case 2
The second scenario to consider is one that contains a little bit of everything.
We must deal with the changes in hardware and addition, the content of the
source Docbase must be split into two different doctypes based upon a
business rule, the object name will become a combination of other
Meta-data values, and the title must be trimmed.
Challenge
The challenges in this scenario are to identify, segregate and move content
based upon specific business rules, and apply metadata conversion and
mapping rules as the content is migrated from one repository to another. The
hardware, platform, OS and databases are also different between the source
and target environments.
Approach
Summary
Like the cases discussed above other cases can be constructed which can be
more complex and demanding but that would be out of scope for this paper.
However, essence here is to analyze the situation and decide the best
suitable option by which the ETL operation can be supported. Moreover, ECM
upgrade/Migration is a specialized job and you would find you would get
better analyzing and predicting things with each migration. I hope the five
do’s and don’t’s of migration/upgrade that I have try to discuss would be
useful to some extent. I wish a smooth upgrade migration that you may
undertake.
http://www.f5.com/news-press-events/news/2008/20080228.html
http://developer.emc.com/developer/edn_redirect_secure.htm?redirectUR
L=http://developer.emc.com/developer/Articles/SevenDCTMJobs.pdf