A snapshot and backup are basically analogous terms in trove. A backup snapshot[1] is a copy of the database data that is stored on the volume or locally on the instance and backed up to swift at a point in time. Trove stores the location of the backup so that a user can restore a database to a new instance. There is another blueprint to support incremental backups.[2] Which will allow point in time restore/recovery of data. Hope this helps. [1] https://blueprints.launchpad.net/trove/+spec/consistent-snapshots [2] https://blueprints.launchpad.net/trove/+spec/incremental-backups On Wed, Nov 6, 2013 at 3:05 AM, Giuseppe Galeota <giuseppegaleota at gmail.com>wrote: > Can you give me a simple workflow that explains the process of a > backup/snapshot? > > Thanks, > Giuseppe > > > 2013/11/6 Giuseppe Galeota <giuseppegaleota at gmail.com> > >> Dear all, >> what is the difference between Snapshot and Backup in the context of >> Trove (o Redwwarf) database backups that I see here<https://wiki.openstack.org/wiki/Trove/snapshot-design> >> ? >> >> Is it maybe the following: >> - backup = copy of volume in which data are stored; >> - snapshot = copy of volume plus virtual machine used to host the engine? >> >> Are they the same concept? >> >> Thanks, >> Giuseppe >> > > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack at lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20131108/c7de55ee/attachment.html>