Quoting Marco ([email protected]): > Hi, > > On 13 febbraio 2015 04:31, Fajar A. Nugraha <[email protected]> wrote: > > > On Thu, Feb 12, 2015 at 12:26 AM, Marco <[email protected]> wrote: > > > Hi, > > > I've some questions for which I couldn't find good answers online and I'd > > > like your suggestions. > > > > > > OS: Linux/Debian 8 Jessie > > > LXC: 1.0.6-6 > > > Backing store: LVM > > > > > > It seems that snapshot clones cannot be done online : > > > "lxc-clone -s" require the original container to be stopped! > > > i.e. : << lxc_container: error: Original container (lxc1) is running >> > > > It actually works when I lxc-stop the container. > > > ==>This means I cannot do a snapshot of a live container. > > > Does this depends on LVM or the same apply for btrfs and zfs? > > > BTW, all the online examples I've found regarding "lxc-clone -s" seems to > > > assume online clone snapshotting ! > > > > > > > Can you explain what you're trying to achieve? > > > > On zfs backend, lxc-snapshot pretty much does zfs snapshot-clone, and > > then modifies the necessary lxc config files. If you're ONLY looking > > for somekind of ONLINE snapshot of the STORAGE, and don't really care > > about running state, then doing storage-level snapshot directly should > > be more appropriate for you. > > > > Yes, you are right. > > > > If you're looking for vmware/virtualbox-like snapshot where the > > in-memory state is also preserved, then this is not for you. > > > > > Yes, I actually was looking for something that consistently saved the > memory and disk of the container. > Thanks.
Then you are looking for lxc-checkpoint, which uses criu to checkpoint the non-disk state. _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
