Hello! Actually I think that checkpoint is performed when cluster is deactivated, so db/ should be in consistent state after deactivation. This means nodes should startup OK after removal of all WAL, WAL Archive and WAL marker files.
Be sure to check that in development before going live with this solution, of course. Regards, -- Ilya Kasnacheev пн, 3 июн. 2019 г. в 08:00, Zaheer <zaheersyed...@gmail.com>: > Hi, > > In this post it has been mentioned that to manually take a snapshot of > Ignite without using commercial solutions, we need to deactivate the > cluster > , copy work/db folder to our backup location and activate cluster. And to > restore we deactivate, copy the backed up data and activate. > > > http://apache-ignite-users.70518.x6.nabble.com/Snapshot-backup-of-Ignite-native-persistance-data-tp20103.html > > When I was trying this, I faced these errors : > > 1. WAL error : On restoring it says critical WAL archive missing and the > nodes crash. > 2. Node Lock : This lock in node00-UUID folder is held from start to stop > of > a node. So deactivating the cluster will not remove the lock. > > I tried copying only the node00-UUID folders without WAL and I was able to > restore my caches. Is this approach correct ? Will WAL overwrite the > restored node00-UUID folders' data ? > > > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
