Sparx Systems Forum

Enterprise Architect => General Board => Topic started by: andykennelly on June 19, 2013, 05:40:09 pm

Title: Disaster recovery (securing my model for restore)
Post by: andykennelly on June 19, 2013, 05:40:09 pm
I need to be able to restore earlier versions of a folder(s), either to roll back changes or in case an entire folder gets inadvertently deleted. Now, while baselining is ideal (for example) to compare versions before restoring, it doesn't help me if the folder has been deleted (since the baselined versions are part of the folder and, therefore, are also deleted).

Is that right? If so, that leaves me with the options of either securing using XMI exports or integrating with a version control system (e.g. SVN). While SVN allows me to restore in a more user friendly way (possibly) it does mean I'm reliant on another system (external to Sparx) and,also, my users have the overhead of installing SVN and maintianing SVN-related user credentials etc.|

Is there anything else related to disaster-recovery that I'm failing to see, or is my only choice between XMI exports/imports and SVN?
Title: Re: Disaster recovery (securing my model for resto
Post by: Helmut Ortmann on June 19, 2013, 07:27:06 pm
Hi,

an easy way to make a logical backup is to copy the model to an *.eap file (Tools, Datamanagement, Project Transfer). This is my preffered way.
With this you also have all the referenced data (Glossary, Scripts,..) safed.

Using Version Control or XML don't give you a complete copy of the information stored in the repository. The referenced data aren't safed. Version Control will bring you some more pros and cons. You can read some of them here in the forum.

Kind regards,

Helmut
Title: Re: Disaster recovery (securing my model for resto
Post by: qwerty on June 19, 2013, 09:00:55 pm
Helmut is right. If you use RDBMS instead of EAP then make backups using native tools.

Using VC for UML models in the way you use it for code is no valid way to go. While code has local easily readable changes a build script might validate nightly a UML model is different. Introducing a change at one place might have impact at the complete other end thus making it invalid. Partially VC can be misused for collaboration but even there it has a couple of drawbacks.

q.
Title: Re: Disaster recovery (securing my model for resto
Post by: Geert Bellekens on June 20, 2013, 04:40:31 pm
Andy,

In fact there's no real difference between xmi import/exports and using VC, except for the fact that VC does the importing/exporting of xmi files for you.

Geert