Common FAQ around upgrade, DB housekeeping and DB HA

book

Article ID: 210474

calendar_today

Updated On:

Products

Continuous Delivery Director

Issue/Introduction

Can you please elaborate more on below

  • A rollback procedure as a part of the upgrade in case the upgrade fails
  • What are database housekeeping maintenance recommendations from a product perspective?
  • HA of DB with SQL Server and support of the same with CDD

Environment

Release : 8.0.0

Component : CONTINUOUS DELIVERY DIRECTOR

Resolution

Please find more details around the below mentioned queries

  • A rollback procedure as a part of the upgrade in case the upgrade fails

With CDD our approach is roll-forward and henceforth we don't have a rollback procedure. CDD product aligns to standard enterprise on premise guidelines, which has below recommendation

    • The upgrade/install of software should be done first in the sandbox(replica or aligned to prod) environment.
    • All sanity testing with third party tools etc., should be done in sandbox.
    • With a satisfactory confidence in sandbox same process should be applied to production environment with a dump of Database for quick rollback, this will guarantee that there won't be any compatibility issue.
    • In case even after following above guidelines still if there are some environment specific issues and related to the product(which is extremely rare) we can provide an urgent patch to resolve it.

Note:

  • The rollback procedure should include backup of the database before the upgrade and restore the database in case of failure ( post upgrade or during upgrade). 
  • As this is very specific to DB it's currently in scope of DBA to do respective backup and restore of respective DB's.
  • What are database housekeeping maintenance recommendations from a product perspective?

At current there is no retention-policy built in product. However, we may support some retention policy for offline database tables of CDD, but that will be an Enhancement request and we can discuss the requirements of the same and can include them as features in future releases. (Please refer to release notes of CDD release to validate if it's been delivered in future releases)

  • How to setup Hight Availability (HA) of DB with SQL Server and does it is supported with CDD?

Setup of MSSQL server in High Availability (HA) is very specific to MSSQL and the customer Database Administrator(DBA) should plan and provision for same.

  • Can we trace functionalities of Bitbucket commits and JIRA tickets related to the artifacts of a release in CDD with MSSQL Server or we need MongoDB for this?

The JIRA tickets related to the artifacts of a release in CDD (Planned vs. Actual ) does not require MongoDB. MongoDB is required for the operation of the Intelligent Test Module(CDI) of CDD for running Maven Testing, Selenium Testing, Cucumber Testing, etc... 

End user can see the status of the ALM work items based on commit messages - without using MongoDB