Process Hibernation

From MemCP
Revision as of 12:14, 28 August 2026 by Wikiservice (talk | contribs) (Refresh MemCP documentation: accuracy, operational guidance, performance profile and maintained API reference)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Process Hibernation

Linux CRIU can checkpoint and restore a complete process, including RAM-only state. This makes it interesting for development experiments with memory tables, but it is not MemCP's supported durability, backup or upgrade mechanism. Open sockets, kernel features, file descriptors, JIT mappings and external storage connections can make restoration fail or restore an unsafe environment.

An experimental local workflow is: 

sudo criu dump -t PID -j -D DUMP_DIRECTORY
sudo criu restore -j -D DUMP_DIRECTORY

Stop incoming traffic and test the exact kernel, CRIU and MemCP build before relying on this even temporarily. A checkpoint is tied to its host/runtime environment and does not replace a portable data backup. Persistent production data should use ENGINE=safe and tested storage-level backup/restore procedures.

See Persistency and Performance Guarantees, File System and Deployment.

Retrieved from "https://www.memcp.org/index.php?title=Process_Hibernation&oldid=399"