How to encrypt the repository content using Trusted content service

MVK4Atos · 2022-07-15T14:40:28+00:00

There was an error rendering this rich post.

Hello All,

I have an existing repository that will be upgraded to the latest version and the old version does not use the Trusted content service. Still, the new version wants to implement a trusted content service. After the upgrade is there any JOBS provided by Trusted content service module to encrypt the content?

Find more posts tagged with

Documentum

Comments

DCTM_Guru

I dont remember the details, but I believe you have to create a NEW encrypted filestore and then use MIGRATE_CONTENT method/job to encrypt the files using TCS.

MVK4Atos

Thank you Guru for response.

My scenario is I am going to perform repository copy operation and upgrade from 7.x to 21.x. I have ~150TB of data partially on SAN/NAS and Majority in ECS store.

DCTM_Guru

AFAIK - you cant encrypt filestore outside of the MIGRATE_CONTENT

Hicham Bahi

If you have licensed the Content Storage Services (CSS) module, it comes with additional content migration jobs (which use MIGRATE_CONTENT internally). I'm not sure if it's still the case but I think that this license also enables you to use the PARALLEL_DEGREE parameter for the MIGRATE_CONTENT method, which allows you to speed up the migration.

You can also write your own content migration batch script.

MVK4Atos

thank you, before even i think of migration - i will have to see what % is in ECS and what in NAS/SAN storage. If encryption already available on ECS storage, I can avoid this .. reason total data is ~160/170 TB.. not sure how much time and can be content consistency issue on live system..