Refresh a Clarity SaaS environment (with database backup)

Products

• Clarity PPM SaaS

Issue/Introduction

You need to request a restore of data from one Clarity environment to another environment. (Request to replicate a Database (DB) to another environment)

Examples:

• Refresh from PROD to DEV environment
• Refresh from PROD to TEST environment
• Refresh from PROD to SAND environment
• Refresh from DEV to TEST environment
• Refresh from TEST to DEV environment
• Refresh from Prod to a Training environment

Notes:

• A refresh is a replacement/overwrite, where the source data will overwrite the target data.

Resolution

Open a case

To refresh an environment, open a case with Broadcom Support, and provide the following information:

• (Mandatory) Source environment URL
• (Mandatory) Destination environment URL
• Preferred schedule (date and time)
• Specify if the filestore needs to be copied to the destination

Requirements

• Cases - Create a new ticket for each refresh request.
• Environments - Both environments need to be on the same Clarity version and build/patch.
  
  Note: It is not technically feasible to perform a refresh if there is a mismatch. We are unable to make any exceptions to this in the GCP platform and are we unable to downgrade one environment to match the other. If a refresh is required, please submit the request prior to an upgrade while the two environments are still on the same version. See the upgrade schedule for Clarity SaaS.
  
  
• Refresh Schedule - Refresh requests will require 48 hours advance notice prior to the proposed scheduled date. The refresh will be scheduled for a 4 hour downtime/outage period.
• Additional Issues - For any issue that arises after a refresh, you need to create a new case.
• Jobs and Processes - Before refreshing, pause all your jobs and processes pertaining to any external integrated system. This ensures that your data from production, as well as the refreshed environment, don't get overwritten
• Integrations - If you have any integrations (including Rally), you are responsible for ensuring that the integration mapping is disabled in non-production post refresh, if applicable. This may be important to ensure data is not incorrectly synced from non-production to the production integration.
  • See Rally and Clarity integration best practices regarding steps for pre/post refreshes.

Additional Information

See Clarity PPM SaaS Service Description (On-Demand Only).

Note: In the very rare scenario where you need to request a refresh from a lower environment TO PROD, additional approval from the Service Management team is required.