We see the need to archive Projects. Silk Central provides since a few versions the possibility to export and import project manually. We have now more than 250 projects and there is now the question if it makes sence to export project and delete projects which were inactive for some time. This would also need that we are able to import these project if required. Recommendations are welcome.
Since Silk Central 12.1 you can export Silk Central projects in order to archive them on a "cheaper" data store than the database like a file system or tapes. In order to free up database space in your production system, you can then delete the archived projects.
Please note, that this approach is tightly bound to the database and the SC version, hence you can import and export only between the same versions.
Means: When you export a project for example with Silk Central 15.0, you can only import it back into Silk Central 15.0 again. The archived project file is not compatible to be imported in Silk Central 15.5 or any other non-15.0 version.
So, if you archive several projects with SC 15.0 and you need to import one or more projects later, you will keep an eye on the following things:
- beside archiving the exported project files (zip) you should also archive the installer of SC 15.0
- to import a project on a later Silk Central version, you need to temporarily setup a Silk Central 15.0 instance and import the project there.
- the database where you have imported the archived project, needs to be upgraded to the currently used Silk Central version (e.g. 15.5).
- if your production Silk Central is 15.5, you can now export the project from the temporary SC 15.5 instance and import it into your production Silk Central 15.5 system.
I want to also highlight the following notes regarding project export/import that should be considered when using this feature:
- When you export/import large projects with a huge amount of project data, the export/import process can take a long time (up to some hours).
- The file size can vary tremendously from project to project and depends on many factors, for example: On the amount of assets, the run count, the attachments, the code coverage statistics, and most importantly on the result files.
- We recommend to minimize the size of a project before you export it. Therefore, you should remove unneeded data and especially unused result files.
- Some browsers have file upload limitations, like for example Internet Explorer. If the project that you want to import exceeds that size, the import will fail. Use another browser to avoid this issue.
- Be aware that the export/import process puts considerable load on Silk Central and on the database server. Export/import actions should be done during off-hours (for example over night or on the weekend) or at least when the Silk Central usage is low and no users are logged in.
- Exporting and importing data is tightly bound to and relying on the database and its content. If the database already contains any inconsistency in data, importing a project might fail. Hence, we strongly recommend - as good practice for every backup process - to try a re-import immediately after an export to ensure validity, data consistence and recover-ability.
- If you want to re-import project data, use the exact same .zip file that you have exported. Other file formats will not be accepted. You can import the data only into the same Silk Central and database version that you have used to export the data.
- If you have any questions concerning the export/import process, do not hesitate to contact the customer support or this forum.
It is not possible to export several projects at once, you can only start the export for a single project with one action.
We have not implemented it that way, as it puts considerable amount of load on the affected systems and we wanted to avoid such high-load scenarios that might lead to problems.