Hi Jakob, The scope of Managment API additions for ML7 was: * Make it easy to initialize hosts and build a cluster * Expose creation, configuration, deletion of forests (including replicas) * Expose configuration of hosts * Expose removal of hosts from a cluster * Exposed tiered storage operations (working with partitions, sub-databases, super-databases)
Combining that with the packaging API for database and app server configuration gives you fairly good coverage for the scenario you're laying out below. Initiating backup and restore operations on a content database was not in scope for ML7 (so that might be something you'd need to continue addressing with Ant); I'd be interested to know what else you run into that you can't accomplish with the ML7 additions. --Colleen ________________________________ From: [email protected] [[email protected]] on behalf of Jakob Fix [[email protected]] Sent: Wednesday, October 30, 2013 3:44 PM To: MarkLogic Developer Discussion Subject: Re: [MarkLogic Dev General] backup/restore forests/databases using REST API? Thanks Michael for your reply. The current, very basic, use case is that we need to be able to reset our test content database into a previous, known state. Our business users will use this feature to restore the database to this state whenever they've messed up the contents sufficiently through their tests (probably using Selenium). So it's not a scheduled backup in this case, but an ad-hoc task. We have Jenkins-CI jobs to execute the restore aand backup tasks, respectively. Right now all our deployment tasks are scripted using the MarkLogic ant tasks (https://github.com/garyvidal/marklogic-ant-tasks). While they do work nicely, it seems we could do a lot of our recurrent setup and teardown tasks now more efficiently using the packaging and manage REST APIs; for example: we have to create four databases, a forest for each, associate them all, set up indexes etc which is 4 times 4 tasks using the ant tasks (and not to forget the necessary restarts after many operations); with the packaging API I think we could make one call to create all databases, their index configurations, forests and make the necessary associations. So I'm investigating whether we can move all admin tasks to the REST APIs, or whether we need to keep some as ant tasks (which is not a problem per se, as they mostly work fine). cheers, Jakob. On Wed, Oct 30, 2013 at 5:54 PM, Michael Blakeley <[email protected]<mailto:[email protected]>> wrote: Not as far as I know. Of course you could create a REST instance and extend it: that might be one step better than a raw script. Or maybe something like https://github.com/codycollier/booster but extended beyond admin:* functions. Can I ask more about your use-case? Mostly I'd expect folks to set up scheduled backup, but I'm sure you know about that feature. Are you duplicating forests or something like that? Depending on the details, there might be an easier way in ML7. -- Mike On 30 Oct 2013, at 04:06 , Jakob Fix <[email protected]<mailto:[email protected]>> wrote: > Hi, > > I'm wondering whether it's possible to initiate the backup and restore > processes of a database and its associated forests via REST, in the upcoming > now version of MarkLogic? > > I know that today I can script this process using xdmp:database-backup and > -restore functions in an xquery script. But I was wondering whether it could > be done using the REST API. > > Thanks in advance, > Jakob. > _______________________________________________ > General mailing list > [email protected]<mailto:[email protected]> > http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected]<mailto:[email protected]> http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
