On Wed, Jan 11, 2017 at 8:39 PM, Miguel Angel Muñoz Gonzalez <
miguel.angel.munoz.gonza...@ericsson.com> wrote:
> Hi everyone,
>
> We are trying to implement a backup/restore mechanism for ODL. I have not
> found much information about it in pipermail history except some questions
> and brief proposals (such as generating an snapshot and storing in a
> particular file, using an external database,…). I would appreciate if
> someone familiar with the topic could give us some hints on it:
>
>
>
> - Is it possible to backup MDSAL Configuration datastore as of
> today? (I suppose it’s a matter of backing up leveldb files)
>
>
>
> - If so, how can we guarantee that the backup is correct and/or
> consistent while it is running traffic and datastore is being modified?
>
>
>
> - Supposedly there is a working mechanism consisting on:
> stopping ODL, copying the files manually and start it up… However, it would
> nice to know if there a more sophisticated mechanism to backup the
> datastore, especially if it does not imply stopping ODL. E.g. a particular
> API or tool that can be called to perform this activity?
>
I hope more knowledgeable people will give you a detailed answer, but there
is one RPC that allows creating a backup of ODL while it is running:
POST /restconf/operations/cluster-admin:backup-datastore
Where the message body looks like this:
{
"input": {
"file-path": "/tmp/datastore_backup"
}
}
Since the datastore is transaction based, I assume this will save data up
to the last successful transaction, but don't quote me on that.
One of the main issues with backup/restore, AFAIK is the possibility that a
schema (YANG model) may change between the backup and restore, and how to
handle that.
-Lori
_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev
