Situation
In was recently asked how to recover the configuration from a development Rhapsody server, where the configuration had not been backed up and the configuration had not been stored as a RLC, Rhapsody Local Configuration file used to store and migrate Rhapsody configurations.
The Rhapsody service had failed, for some reason, before the configuration had been moved to a more secure platform. The configuration contained many hours of development and needed to be recovered as soon as possible.
Solution
Not sure if this solution is approved by Orion Health! My solution was to copy the contents of the Config folder, and subfolders to a new Rhapsody installation with Rhapsody service in a stopped state, overwriting any existing files and folders in Config.
D:\Program Files\Orion Health\Rhapsody\rhapsody\data
When the files and folders are copied the Rhapsody service can be started. The original configuration should now be configured on the new Rhapsody service.
I would advise having both Rhapsody services at the same version number.
Advice
The best advice I can give is to avoid getting into this situation by configuring Rhapsody Backup to backup the server at reasonable intervals. On a development server I recommend more frequent full and incremental backups than on a production Rhapsody server due to the constantly changing configuration of the routes during the development process.
I would recommend saving configurations as an RLC file for the whole configuration, at locker level or folder/solution level. It is far easier to reinstall a RLC for a single folder, for example than to role back the configuration.
