Checkpoint/restore streamer
Last updated
Was this helpful?
Last updated
Was this helpful?
The Cedana daemon supports checkpoint/restore via low-overhead streaming. It's powered by the , which is a fork of CRIU's .
Real benefit of streaming is realized when checkpointing and restoring to/from a remote location. See Remoting.
Create an account with Cedana, to get access to the streamer plugin. See .
Set the Cedana URL & authentication token in the .
Install the streamer plugin with sudo cedana plugin install streamer.
Ensure the daemon is running, see .
Do a health check to ensure the plugin is ready, see .
The cedana dump subcommand supports a --stream <n> flag, where n is the number of parallel streams to use. For example:
This will directly stream the checkpoint to a directory, using 4 parallel streams. You will notice that the checkpoint directory contains 4 separate image files:
Similarly, the cedana restore subcommand supports a --stream <n> flag, where n is the number of parallel streams to use. For example:
Note that, here you must pass in 4 as the number of parallel streams, as the checkpoint directory contains 4 separate image files, since the checkpoint was taken with 4 parallel streams.
All compression algorithms supported for basic checkpoint/restore are supported. See for more information.
The daemon simply reads/writes from the filesystem. This is also the case for streaming, with the additional requirement that the underlying filesystem must be .
To checkpoint/restore to/from a remote directory, you can use a FUSE-based filesystem mount backed by your network storage. For Amazon's S3, check out .
To enable streaming by default, set the Checkpoint.Stream field in the to the desired number of parallel streams. Zero means no streaming.
For all available CLI options, see . Directly interacting with daemon is also possible through gRPC, see .