Author: Matt Mickle
Updated: October 2024
Audience: Everyone
Products Applicable: Jama Connect®
Use Case
How to Create an Archive Environment
Best Practice
Currently, Jama cannot take a single project from an instance and move it to another instance or archive it in another location. The only way this is feasible is to back up the entire instance and then delete the projects you no longer wish to see in the current instance. Here are some steps to do this.
Implementation
1. It's crucial to start by creating a backup of your instance. You can do this using the XML Backup functionality in Jama's root admin. Your Database Administrator (DBA) could also create a database backup as an option (the option varies according to the database). This step ensures that your data is secure and you are prepared for unforeseen circumstances.
2. To make the archived data accessible, you must migrate it to another instance.
Note: To prevent duplication of items or notifications, you must disable SMTP from the General Properties and any Integrations or Web Services connections that may exist.
3. When you're ready to delete the projects you no longer need from your original instance, use Hard Delete. But remember, restoring the data (Step 2) first is crucial, as this is an irreversible change. This caution ensures that you keep all important data during the process.
You should now have an archive instance containing your old data and a current instance containing only what you wish to be active.
References
Please feel free to leave feedback in the comments below.
Related to
Comments
0 comments
Article is closed for comments.