Best method to archive diagrams?

[BobM]

Dear,

I just tried RAS to try to import the diagram I want to archive into another repository
At first glance it looks very good and fancy, but in the end it didn't only add all elements required to display the diagram I want to archive, but it also wanted to add all diagrams where those elements are used + all elements included in the diagram where all those elements were used, etc... etc...
essentially as everything is related to everything it was busy transferring my entire repository into the other repository without me being able to set a stop point.

My Endgoal: I want to delete a selection of packages with diagrams in my main repository, but still make this old diagrams available in an archive repository
My Expected result: All elements in direct relationship to the diagrams in the selected packages to be sent to the archive repository in order to still be able to display the diagrams; This preferably stored in the same structure as in the initial repository

What is the best method to achieve this goal?

[Geert Bellekens]

Use project transfer to create a complete snapshot of your current repository.

We have a script that we execute every week to create such a snapshot as .eap file.
It's easy, quick, and we don't need to rely on any other operations or support department to restore a backup of the database somewhere, ....

Geert

[qwerty]

In the past we always created snapshots of the current model on a weekly basis. But never ever we had the need to use them. You might see them as backup, but there are also other (better) ways to create those.

q.