Important Considerations When Overwriting a Non-Production Database with a Copy of Production
Configurations Sync
Under special circumstances, non-Production databases will be overwritten by a copy of Production. This is generally done for testing purposes only. This is not a sync operation, but it is covered in this document to differentiate this process from a sync. Overwriting a non-Production database with a copy of Production will harmonize the setup data between environments but there are other important implications to consider.
- Any development in process in the overwritten destination inclusive of optional Portal configurations will be removed
- Support issues will be lost in the overwritten destination
- Misalignment of the support numbering system in overwritten destination
- Increased database size of the overwritten destination
- Live Client data is now in a training environment. Extra caution needs to be taken to ensure Client data is not being shared or discussed during the training process
- Client transactional data should be removed but will vacate any testing data.
- The Eccovia Support team may log into your training environment for issue resolution
- Users with access to a training environment can have different user permissions than in production. Ensure the users do not have additional security settings giving them access to data they would not have in Production
- Generated test/sample data will be lost