It would be very handy to have a rest call, or an option under Administration > Database Backup, to archive the complete history of a subtree, rather than the entire server. We do nightly full backups with history for purpose of disaster recovery. But that's a limited rolling window. As configurations run through their lifecycle we want to remove them to reclaim storage folder space, but want to be able to restore them, perhaps for a patch or to recover some metrics from an old release. Something like
curl -u admin http://server/rest/archive/123 -o 123.zip
curl -u admin -X POST --data-binary 123.zip "http://srver/rest/restore?parent_id=122&config_id=123"
If the parent_id or config_id are not specified then whatever is in the supplied zip file is used. Errors would be thrown on restore if the parent_id doesn't exist or the config_id already exists.
|
