Hi Aree and Bradley, About the backup, it really depends on your uses cases. Most of the Stanbol services are completely stateless and that (initially) means you don’t need a backup. If you are using a custom dataset, or some custom configurations you probably would like to backup them. For the datasets, if you have used the generic indexer to build them, the outcomes of that tool could be your backup: at the end you will have a Solr index that you can install in a clean Stanbol whenever you want and a bundle for the EntityHub site that you can also install in any moment.
Regarding configuration, probably the best solution is to configure your own Stanbol launcher with your final configuration. With all these resources you can easily replicate your instance. Hope that helps. Cheers, Rafa En 25 de marzo de 2015 en 23:31:18, Aree Cohen (aree.co...@sbs.com.au) escrito: Perfect timing. We are in the same boat. We're about to deliver a critical project using Stanbol and need help with setting up our production environment. Moreover, does anyone know the best strategy for replication between two Stanbol servers. Is rsyncing a feasible strategy? Any help with this would be extremely appreciated. Thanks, Aree ________________________________________ From: Bradley Falzon <b...@teambrad.net> Sent: Thursday, 26 March 2015 9:14 AM To: dev@stanbol.apache.org Subject: Recommended Backup Strategy Hi All, We're beginning initial testing of Stanbol, and wanted to know the recommended approach to backups. We've tried checking the mailing list and stanbol.apache.org for best practices, to no avail. Is there any features built in? We're really unsure on the internal workings and best strategy here. Thoughts? -- Bradley Falzon b...@teambrad.net [Vikings. Thursdays, 8.30pm, SBS ONE.]<http://sbs.com.au/vikings>
