Layer7 API Management

  • Private Community

  • 1.  Portal DR data migration

    Broadcom Employee
    Posted Aug 08, 2017 04:33 AM

    Hi,

     

    We are trying to deploy one Developer Portal in Production environment and another one in DR. The one in DR will standby. If the Portal in Production is down, request will be directed to the Portal in DR. We don't plan to set DB replication between Production and DR Portal.

     

    Is there any best practice how to copy the latest data from Production to DR after Production down and before DR takes over? There are two types of changes, file based change and db change. For file based change, we can't create and export the patch from CMS since the Portal already down. For db changes, we may not be able to get DB dump because the server or db may down. Is it a working way to import patch and db dump to DR even if we have the patch and db dump?    

     

    Thanks.

    Yang 



  • 2.  Re: Portal DR data migration
    Best Answer

    Broadcom Employee
    Posted Aug 08, 2017 04:52 PM

    You are correct - the Portal stores all artifacts in 2 places: DB + Filesystem.

    So - in order to feed your DR system you need to capture both on a daily basis.

    Filesystem: Backup /opt/Deployments/lrs (this includes all patches)

    DB: mysqldump lrs and mysqldump lrsdata

    Store those outside the Portal or moved them to the DR portal on a daily basis.