Migrating Documentum Filestore to AWS S3 bucket

Options
Xyril1993
Xyril1993
in Documentum #1
We already migrated our Documentum filestores to S3 bucket using 'aws s3 cp' and sync sessions. There are some files under ..\data\<repo>\content_storage_01\.. that were not accessible and unable to copy, most of them are txt files and there are some xml files. Wondering if it's okay to not copy the files at all or is there a way to copy it? The install owner has full permission to all folders/subfolders/files in the filestore.

Thank you in advance!

Comments

  • Hicham Bahi
    Hicham Bahi E
    #2
    Options
    They are probably orphaned file. Try to run the dm_DMClean job and it will probably delete them.
  • Hemanth88
    Hemanth88
    #3
    Options

    after you migrated the content ,were there any updates to be done on documentum tables(like updating dm_sysobject.a_storage_type) ?

  • Xyril1993
    Xyril1993
    #4
    Options

    @Hemanth88 - on our case, just the file_system_path in dm_location table

  • Hemanth88
    Hemanth88
    #5
    Options
    @Xyril1993 - so you updated the dm_location.file_system_path with S3 bucket url ..? also I’m sure you created the s3_store object too
  • Xyril1993
    Xyril1993
    edited May 23, 2021 #6
    Options

    @Hemanth88 - yes, with the s3 bucket URL and yes s3_store was created

  • Hemanth88
    Hemanth88
    #7
    Options
    @Xyril1993 - Thanks much.
  • Sriki_Ra
    Sriki_Ra
    #8
    Options

    @Xyril1993 In continuation to Hemanth88 discussion, how is a dm_s3_store linked to dm_location table? since i am still trying to figure out how to link a s3 object to a dmr_content.

Categories