kraken: make data copyable and add method on data_manager for handling disruptions

We serialize in a string then we deserialize it, it's ugly, but it
will do the job for now. The ClonningArchive will save us!!!
I think it can be better to have load and save on a std::[io]stream, and sharing its usage with the serialization/deserialization on lz4