keeping prod and dev data in sync

[Russ_Mellnick]

What is the recommended way to keep data sync'd between prod and dev. We want all the changes replicated to Dev each night without having to reactivate the system each time.

Is there a list of tables to script? or is there an automated way to do this?

thanks

Russ

[Kristin_Young]

I am also interested in knowing how to do this!

[Eric_Beavers · Accepted solution]

There is not an automated way to do this.

The first suggestion you will always get is to use Configuration Migration https://www.onbase.com/community/technical_communities/configuration_migration/). This tool only copies configurations. Since this will be DEV you will want to use the Unlinked option. There are a few limitiations of this option that will need to be planned for. A complete list of constraints are available in the Config migration MRG

Next, if you have onbase 14+ you can use the new option in Onbase Configuartion, under the Utils menu, called Export Configuration Items. This tool lets you move specific configurations. More options were added in 15.

Finally, there is a manual method of copying an entire database and attaching it as the new system. This will grab all configuration and meta data. Complete documentation is available under the Technical group in the Performance and Scalability downloads (https://www.onbase.com/community/technical_communities/performance_and_scalability/m/performance_and...) This option will require you to call your first line of support for an activation if you intent to use the system longer than 14 days. With a little innovation and engineering you could probably automate most of this 3rd method.

[Dhwani_Pandya]

Does the export/import tool work if the doc type exist in Dev and QA. And if there are changes in the doctype such as changes in keywords/dip/autoname string. Can I use the export and import from dev and qa for that?