D2 4.5 in AWS Cloud

Xyril1993
Xyril1993 Member
in Documentum #1
Is anyone currently using D2 4.5 hosting in AWS Cloud? Do you experience performance issue after migrating? 

Thank you in advance!
Tagged:

Comments

  • DCTM_Guru
    DCTM_Guru Member
    #2
    Is your entire stack in AWS (DB and Content Server)?  We have entire Documentum stack on AWS and we don't have any issue.  Obvious thing to check is tracert and make sure you are not making unnecessary hops to different servers/networks.
  • Xyril1993
    Xyril1993 Member
    #3
    Yes, except the content (where the data and share folders located) is on a different server which is still on-prem. 
  • Xyril1993
    Xyril1993 Member
    #4
    Also, I spoke to two of the OpenText supports and they said that v4.5 does not have Cloud support and probably that's why we are having performance issue.
  • DCTM_Guru
    DCTM_Guru Member
    #5
    That makes more sense now.  Think about how route that the request/response has to take:

    1) Browser makes request for file to App Server (Azure)
    2) App Server pass requests to Content Server (Azure)
    3) CS retrieves content from local file store - this probably takes the longest to send file back to Azure
    4) CS sends file to App Server
    5) App Server sends file back to browser

    You should always put the content store closest to the CS for optimal performance.  We initially tried storing content in S3 bucket (vs local storage on EC2 instances) and it wasn't performant as well.  Supposedly, they improved this with latest release, but we're fine with existing storage in AWS.
  • Xyril1993
    Xyril1993 Member
    #6
    Interesting, but is it still relevant to the content store if it's also slow upon accessing D2, logging in and opening workspaces/widgets?
    Also, when you say s3 bucket? are you referring to the storage gateway?


  • DCTM_Guru
    DCTM_Guru Member
    #7
    So everything in D2 is configuration based and that configuration is stored in repository.  I believe some of the configuration information is actually stored as xml config files in the repository (vs database tables), so the performance of D2 would definitely be impacted by this if app server had to download xml config file from your local file store and read it before display app configuration to the users.

    AWS s3 bucket is AWS object level storage that anyone (or application) can use to store files in the cloud with high reliability.  S3 bucket is entirely different from "mounted drive" that is attached to EC2 instance.  Storage gateway is how your EC2 instance is accessing file store in your local network.  Have you tried enabling local cache on your storage gateway?  This might help if the D2 user xml config files do not change often.
  • Xyril1993
    Xyril1993 Member
    #8
    We really haven't tried storage gateway yet but that's what we are considering, and our last option, at this moment.
    If we migrate, or copy, the content store from on-prem to s3 bucket (by storage gateway)... most probably we will have to perform reindexing of data, correct?
  • DCTM_Guru
    DCTM_Guru Member
    #9
    How is D2 connecting to your on-prem file store if you are not using storage gateway?  Is your Content Server on prem?  
    If you installed xplore in AWS, then its indexes should be in AWS as well and reindexing may not be required.
  • Xyril1993
    Xyril1993 Member
    #10
    File store is currently in NAS, it's just mounted in our content servers but all our servers including App, CS and xPlore are in AWS. 
  • DCTM_Guru
    DCTM_Guru Member
    #11
    How does CS in AWS connect to your NAS?  Are you using DirectConnect?  
    As for you re-indexing, this depends on where xPlore is storing index.  If its storing it in AWS, then you should be fine.
  • Xyril1993
    Xyril1993 Member
    #12
    Initially, the environment are all on-prem until we migrated to Cloud, except the storage where the filestore is located, so that server of the storage is the one that's still on-prem.

    That's I am not exactly sure how they're connected. The dm_location and dm_server_config path are all configured to be stored in that NAS.
  • DCTM_Guru
    DCTM_Guru Member
    #13
    Typically, content server sees dm_location or dm_storage as NFS mount (or other storage refererence).  If your Content Server is in AWS, I don't see how it would see the storage mount unless it can see your network directly (ie via storage gateway or DirectConnect).
  • Xyril1993
    Xyril1993 Member
    #14
    I have to confirm with our Cloud team on how it's connecting to on-prem.
    But, what would you recommend?
  • DCTM_Guru
    DCTM_Guru Member
    #15
    Recommend what?  As my initial reply indicated, we have since moved everything (servers, content store, etc) to AWS and have not had any performance issues. If you are concerned about time it would take to move content to AWS, you can always order a AWS Snowball.  This is how we move 5 TBs of data from our data center to AWS data center.
  • Xyril1993
    Xyril1993 Member
    #16
    Okay, understood, i just thought that there's other option that we could try, but it looks like we really have to do something with our content store, to move it over to AWS too. I really appreciate your help sir! 
  • DCTM_Guru
    DCTM_Guru Member
    #17
    Per you statement above about bad performance of D2 independent of file retrieval, I gave some options to check on how to potentially cache some of the D2 user config.  Since you dont know how you are connecting file store to Content Server, I don't have any other recommendations.

Categories