I'm trying to manage my backup policies and I am having a very annoying
time with CloneZilla (disk to disk).
My source disk is 500gb ; so I purchase a 500gb SSD to clone the image;
however the SSD image was too small as it wasn't exactly 500gb.
I purchase a 1tb SSD; expecting clonezilla to utilise only the 500gb it
needs to backup my 500gb; but to my surprise on testing recovery the 1tb is
now too large to copy the backup back to the source.
This feels like an endless cat and mouse. If I purchase a source SSD > 1 TB
and recover my back; next time I backup the source it will be too large for
the 1TB SSD.
Surely theres a better way of doing this?
If I resize my source parittion and burn to the 500gb; its only going to
cause an issue when I bur the 500gb back to the source as it will be larger!
Hello all,
I'm trying to manage my backup policies and I am having a very annoying
time with CloneZilla (disk to disk).
My source disk is 500gb ; so I purchase a 500gb SSD to clone the image;
however the SSD image was too small as it wasn't exactly 500gb.
I purchase a 1tb SSD; expecting clonezilla to utilise only the 500gb it
needs to backup my 500gb; but to my surprise on testing recovery the 1tb is
now too large to copy the backup back to the source.
This feels like an endless cat and mouse. If I purchase a source SSD > 1 TB
and recover my back; next time I backup the source it will be too large for
the 1TB SSD.
Surely theres a better way of doing this?
If I resize my source parittion and burn to the 500gb; its only going to
cause an issue when I bur the 500gb back to the source as it will be larger!
What's the best way of approaching this
Duplicated post. Let's focus on this one:
https://sourceforge.net/p/clonezilla/discussion/Open_discussion/thread/6305d1ac48
Steven