From: Tim H. <th...@op...> - 2012-11-02 17:09:57
|
On 2 November 2012 14:47, Alexey Zakhlestin <ind...@gm...> wrote: Hi, The part which happens on developer machine is ok, because it is easily > scriptable. > But the part which has to be run on production system uses web-ui, which > is not easily scriptable. > Variant 1: if it's scriptability you need, why not run http://docs.openlinksw.com/virtuoso/fn_backup_online.html via isql(1) or even via your language-of-choice's ODBC module? Variant 2: you could set up a scheduled task to perform the online backup at regular intervals as well, so you only need to rsync newer .bp files. Variant 3: our commercial Virtuoso packages feature replication<http://docs.openlinksw.com/virtuoso/htmlconductorbar.html#replicationandsynchronization>- snapshot, transactional, incremental - which would be the ideal way to solve this. > It would make a lot of sense if there were special command-line tools for > exporting and importing data. We're mostly interested in RDF data, so if > there was an option which omits everything else from the dump we would be > even happier. > Our page http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtRDFDatasetDump documents how to dump RDF graphs to file(s), which can then be easily imported into your development instance in bulk. For relational tables, it should be easy to knock-up a quick odbc2csv.py or similar. HTH, ~Tim -- Tim Haynes Product Development Consultant OpenLink Software <http://www.openlinksw.com/> <http://twitter.com/openlink> |