1,077
edits
Changes
mLine 1:
Line 1: − + + + Line 32:
Line 34: − + − − After creation of such stack of images some data would get duplication in dumps. If you don't want to keep duplicates there's an ability to punch duplicate data from non-top images. There are two options for this.+ − − ; Deduplication action − : The <code>crui dedup</code> command would open the image directory and punch holes in the ''parent'' images in needed places − ; Automatic deduplication while dumping+ − : The <code>--auto-dedup</code> option would cause every write to images with process' pages to go an punch holes in respective parent images. − The latter option appies to both <code>dump</code> and <code>page-server</code> actions and thus is extremely useful in [[disk-less migration]] scenario.+ + + + +
→See also: add Memory images deduplication link
If you're doing several dumps in a row, the 2nd and subsequent dumps can be speed up. Here's how:
{{FIXME|describe why incr. dumps are needed, and when to use pre-dump ([[iterative migration]]) instead of incr. dumps.}}
If you're doing several dumps in a row, the 2nd and subsequent dumps can be sped up. Here's how:
== Create the first dump ==
== Create the first dump ==
# criu restore --images-dir <path-to-images>/ANY/
# criu restore --images-dir <path-to-images>/ANY/
{{Note|After each (but the last) dump tasks continue running and thus can modify filesystem. CRIU does not snapshot filesystem and assumes, that proper filesystem state for restore is provided by a user.}}
{{Note|After each (but the last) dump tasks continue running and thus can modify filesystem. CRIU doesn't snapshot filesystem and assumes, that proper filesystem state for restore is provided by user}}
== Data deduplication ==
== Data deduplication ==
See [[memory images deduplication]].
== See also ==
* [[Live migration]]
* [[Disk-less migration]]
* [[Iterative migration]]
* [[Memory images deduplication]]
* [[Page server]]
[[Category:HOWTO]]
[[Category:HOWTO]]
[[Category:Memory]]
[[Category:Memory]]