Log inSkip to main contentSkip to sidebar
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Improve Confluence Sandbox copy reliability by supporting other data migration options
Currently, when copying Confluence production data to sandbox, the sandbox service relies on Confluence's CSV Backup export and import services, to copy the data.
This can cause the sandbox copy to fail, if there's any issues with the CSV Backup export and import services, or if we have data that triggers any one of the existing bugs with the CSV Backup export and import services.
Suggested Solution
Improve the resilience of Confluence Sandbox copy by;
Having a separate service for the Sandbox copy to fall back to, if the CSV backup services hit into any issues/bugs, or
Use a separate service entirely, to avoid the existing issues with the CSV backup services.
Why This Is Important
With use cases of sandbox copy having over hundreds to thousands Spaces, having missing Spaces impacts the usage of the entire Sandbox service.
In most cases, the Spaces that fail, will have to be manually export, fixed, and imported.
These workarounds are require lots of time and manual work, to review and fix, leaving the Sandbox partially or completely unusable in some cases.