Migrating a client

mdodo · 2022-06-29T10:07:15+00:00

There was an error rendering this rich post.

Hi,

A client has broken into 2 entities entities and they were using one implementation with multiple filestores for each division. The broken away division has been given its filestore(Documentum filestore) and a dump of their database only. No passwords or encryption key given.

My task, if possible, is to implement a new Documentum docbase and use this given database(after restore) and filestore as the repository. Without any other information given, is this task possible? If so, which approach because I believe the cloning one is out of the windows

Kind regards

Find more posts tagged with

Comments

Hicham Bahi

Feasible? Yes but only to the extent that you know how to read the metadata directly from the database and decode data ticket to associated content files in order to import them in the new repository. It would probably make more sense if they provide you with an export of the relevant documents in some agreed format (e.g. metadata as XML with location of content files), which you would then import. Or use a commercial tool for export/import.

DCTM_Guru

Curious - why do you think cloning is "out of the windows"? If this entity is going to be in an entirely different network (or even subnet), you can clone it (delete primary docbase filestore) and in the remaining system (delete secondary docbase and filestore).

We used to clone Documentum systems with multiple repositories into different environments (DEV, TST, PRD) as long as you network is configured to segregate the diff env. Once they were cloned, they operated independently - which meant you could delete whatever you like from each of them.

mdodo

Thank you for the response.

I have always successfully cloned(copied) a repository following the documentation which states that the following are requirement from the source implementation:

aek.key
dbpasswrd.txt
installation owner and password
repository ID
etc,

Now none of the above is provided, only the database dump and filestore. We done have access to the current production but if this is enough to clone then that would be great, any tips or pointers will be welcomed

Kind regards

DCTM_Guru

In your original statement:

"A client has broken into 2 entities entities and they were using one implementation with multiple filestores for each division. "

- You maybe able to re-use existing aek and dbpassword if they were originally using the same Documentum Content Server.

Hicham Bahi

What about sitting together with other division and agreeing on a strategy to split up the repositories. And then they provide you with what you need to achieve this. Is that too much common sense?

mdodo

Thank you very much for the responses.

I am afraid they haven't agreed to give us the aek and dbpasswd. They could have given us those details and updated their own, if they wanted too.

Sitting down with the team from the other side to make them see reason is too much common sense for them, I suppose😆

We are continuing with the talks and hopefully something will give, I am just preparing for the worst while hoping for the best

Kind regards