Backup/Restore vs. Export/Import

[Paul Stovell]

I have an application that I plan to use RavenDB embedded with, and I'm trying to work out a backup strategy. From a brief look it appears that I can either use backup/restore, or import/export to achieve similar things. I've read that:

- Export doesn't include indexes, these will be rebuilt after importing

- Restore requires an empty database, while import can be run on an existing database

- Export includes documents created during the export, while backup will be a snapshot of the point when the backup was started

Are there any other reasons to choose one over the other? Is there anything that makes Export inappropriate for backups? 

Paul

[Tobi]

Am 14.03.2012 16:29, schrieb Paul Stovell:

> Are there any other reasons to choose one over the other? Is there anything
> that makes Export inappropriate for backups?

Import/Export works between different architectures and Esent versions
while Backup/Restore only works on the same architecture/Esent version.

Tobias

[Oren Eini (Ayende Rahien)]

Paul,

Backup is meant to do backups, it allows you to quickly restore from a failure on the same/similar system.

It can do incremental backups as well.

Export is meant to get a dump out and that is about it. Backup is usually much faster than an export.

[tur...@gmail.com]

How to backup/restore using code? We want  a schedualer to get backups on specific intervals using code.

[Oren Eini (Ayende Rahien)]

See https://github.com/ayende/ravendb/blob/master/Raven.Backup/Program.cs

Oren Eini

CEO

Hibernating Rhinos

Cellular: +972-52-548-6969

Office:    +972-4-674-7811

Fax:       +972-153-4622-7811

--
You received this message because you are subscribed to the Google Groups "RavenDB - 2nd generation document database" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ravendb+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.