Hi,

Thanks a lot for the quick response.

Please, see my doubts below.

Thanks again and best regards/
Esther

From: Tom Pantelis [mailto:tompante...@gmail.com]
Sent: martes, 21 de febrero de 2017 12:48
To: Esther Terrero <esther.terr...@ericsson.com>
Cc: controller-dev@lists.opendaylight.org
Subject: Re: [controller-dev] Questions about Backup&Restore



On Tue, Feb 21, 2017 at 6:34 AM, Esther Terrero 
<esther.terr...@ericsson.com<mailto:esther.terr...@ericsson.com>> wrote:
Hello,

Please, I would appreciate if you could clarify me the questions below 
regarding backup and restore:


1.       I see that when snapshots are generated they are generated for both 
the configuration and the operational data. What is the reason for having 
snapshots for operational data that are not going to be restored?
A snapshot also contains the election term info and peer configuration which is 
needed for raft.
(Esther) Then the election term info and the peer configuration, are they in 
both snapshots for config data and operational data even if they are redundant? 
(I understand that operational and config data are in the same shard, correct?)


2.       Upon performing a backup by means of the 
cluster-admin:backup-datastore rpc, is writing on the datastore stopped to 
ensure consistency while the backup takes place?, i.e., is the consistency 
ensured, for instance suspending modifications to the data (from NBI/SBI 
traffic) while the backup takes place?
A backup does not suspend anything - it merely takes a snapshot.
(Esther) How do we ensure then that while the snapshot is being taken in 
information there is consistent?


3.       If we use LevelDB journaling, is LevelDB compaction blocked while 
backup takes place?

No.

4.       Does the backup generation imply the generation of an snapshot? If so, 
are the latest entries of the journal included in that snapshot?

Yes

Thanks a lot in advance and best regards/
Esther Terrero


_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org<mailto:controller-dev@lists.opendaylight.org>
https://lists.opendaylight.org/mailman/listinfo/controller-dev

_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev

Reply via email to