Arangodump Limitations

Arangodump has the following limitations:

• In a cluster, arangodump does not guarantee to dump a consistent snapshotif write operations happen while the dump is in progress (seeHot Backups for an alternative). It istherefore recommended not to perform any data-modification operations on thecluster while arangodump is running. This is in contrast to what happens ona single instance, a master/slave, or active failover setup, where even ifwrite operations are ongoing, the created dump is consistent, as a snapshotis taken when the dump starts.
• If the MMFiles engine is in use, on a single instance, a master/slave, oractive failover setup, even if the write operations are suspended, it is notguaranteed that the dump includes all the data that has been previouslywritten as arangodump will only dump the data included in the datafiles_but not the data that has not been transferred from the _WAL to thedatafiles. A WAL flush can be forced as documented in theWAL flush section.