Process Hibernation - Revision history

Wikiservice: Refresh MemCP documentation: accuracy, operational guidance, performance profile and maintained API reference

2026-08-28T10:14:02Z

Refresh MemCP documentation: accuracy, operational guidance, performance profile and maintained API reference

← Older revision		Revision as of 12:14, 28 August 2026
Line 7:		Line 7:
	An experimental local workflow is:		An experimental local workflow is:

	<~~syntaxhighlight lang="bash"~~>sudo criu dump -t PID -j -D DUMP_DIRECTORY		<pre>sudo criu dump -t PID -j -D DUMP_DIRECTORY
	sudo criu restore -j -D DUMP_DIRECTORY</~~syntaxhighlight~~>		sudo criu restore -j -D DUMP_DIRECTORY</pre>

	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 <code>ENGINE=safe</code> and tested storage-level backup/restore procedures.		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 <code>ENGINE=safe</code> and tested storage-level backup/restore procedures.

	See [[Persistency and Performance Guarantees]], [[File System]] and [[Deployment]].		See [[Persistency and Performance Guarantees]], [[File System]] and [[Deployment]].

Wikiservice: Refresh MemCP documentation: accuracy, operational guidance, performance profile and maintained API reference

2026-08-28T09:59:35Z

Refresh MemCP documentation: accuracy, operational guidance, performance profile and maintained API reference

← Older revision		Revision as of 11:59, 28 August 2026
Line 1:		Line 1:
	~~MemCP is a In~~-~~Memory database. In case you use the <code~~>~~memory~~<~~/code~~> ~~engine, there is no data stored on disk.~~		<!-- Copyright (C) 2026 Carl-Philip Haensch -->
			<!-- SPDX-License-Identifier: GPL-3.0-or-later -->
			= Process Hibernation =

			Linux CRIU can checkpoint and restore a complete process, including RAM-only state. This makes it interesting for development experiments with <code>memory</code> 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.

	~~<code>criu</code>~~ is ~~an OpenSource project to hibernate processes on linux on disk and restore them later (see https~~:~~//criu.org/Main_Page).~~		An experimental local workflow is:

			<syntaxhighlight lang="bash">sudo criu dump -t PID -j -D DUMP_DIRECTORY
			sudo criu restore -j -D DUMP_DIRECTORY</syntaxhighlight>

	~~You can hibernate~~ the ~~memcp process with~~		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 <code>ENGINE=safe</code> and tested storage-level backup/restore procedures.
	~~sudo criu dump -t~~ [~~PID~~] ~~-j -D~~ [~~DUMP_DIRECTORY~~]
	~~And reactivate the process with:~~		See [[Persistency and Performance Guarantees]], [[File System]] and [[Deployment]].
	~~sudo criu restore -j -D~~ [~~DUMP_DIRECTORY~~]

Carli: Created page with "MemCP is a In-Memory database. In case you use the `memory` engine, there is no data stored on disk. `criu` is an OpenSource project to hibernate processes on linux on disk and restore them later (see https://criu.org/Main_Page). You can hibernate the memcp process with sudo criu dump -t [PID] -j -D [DUMP_DIRECTORY] And reactivate the process with: sudo criu restore -j -D [DUMP_DIRECTORY]"

2024-05-17T21:07:55Z

Created page with "MemCP is a In-Memory database. In case you use the <code>memory</code> engine, there is no data stored on disk. <code>criu</code> is an OpenSource project to hibernate processes on linux on disk and restore them later (see https://criu.org/Main_Page). You can hibernate the memcp process with sudo criu dump -t [PID] -j -D [DUMP_DIRECTORY] And reactivate the process with: sudo criu restore -j -D [DUMP_DIRECTORY]"

New page

MemCP is a In-Memory database. In case you use the <code>memory</code> engine, there is no data stored on disk.

<code>criu</code> is an OpenSource project to hibernate processes on linux on disk and restore them later (see https://criu.org/Main_Page).

You can hibernate the memcp process with
sudo criu dump -t [PID] -j -D [DUMP_DIRECTORY]
And reactivate the process with:
sudo criu restore -j -D [DUMP_DIRECTORY]