Backup and Rollback

Unknown

Backup and Rollback

Unknown

Hi Team,

What is best practice to Backup Codebase for Production Move, in case if we need to Rollback to working version in production.
We are going to take backup of Production “Decisions” Database. Is that all is needed? I mean if I restore that database will that restore the Codebase as well(like flows/forms etc..?)

Unknown

Hi,

All the flows, forms, portal settings, etc are stored in the Decisions database. So backing up the Decisions database is the most important step you can take. However in addition to the Decisions database you should also backup the following to ensure that a machine could be rebuilt entirely from backups.

C:Program FilesDecisionsFileStorage* -- This contains any files that have been added to the portal as File References (FileData is stored in the database). If you have not created any File References, this folder may be empty.

C:Program FilesDecisionsDecisions Services ManagerInstancesControlKeys.dat -- This file contains your encryption keys to decrypt any encrypted database values. This file will not exist if you have not created any encrypted data)

C:Program FilesDecisionsDecisions Services ManagerSettings.xml -- This file contains low-level settings about the server like connection string to the database, base URL to portal, enabled logging levels.

C:Program FilesDecisionsDecisions Services Managermodules* -- This folder should be backed up if you have created any customer modules, but does not need to be if you are only using built-in modules from Decisions.

It is also a good idea to archive off the Decisions installer that was used to set up the machine so that you can easily reinstall.
Please let me know if you have any questions.