clone ssd boot disk

Dec 04, 2022 Last reply: 3 years ago 25 Replies

That is a possibility with certain software, so proceed with caution and always check that your backuped files are identical to the originals

*BEFORE* you need to restore from it.

However in practice, there are few problems with this approach. Particularly as frequently changing files such the contents of caches are best excluded from incremental backups, and recreated when needed.

I have dozens of large sqlite databases which are receive updates during backups, and have not suffered any corrupted, verified by checking against remote replicated copies.

---druck

Don't try it with a real database server.

That was clear but what I said also stands. Take one 128 GB drive, resize the file system(s) on it so that they take up at most 120 GB of the drive and dd away. dd will error out when the smaller drive is full but it doesn't matter since everything contained in the file system(s) was copied at that point.

I can see someone else proposed this as well so it shouldn't be a radical concept. Tools to resize common file systems have been around for a few decades now.

You can get away with it on a database server using C-ISAM files provided its relatively quiescent.

the -x option you quoted stops it cross filesystems - so no need to exclude /dev /proc /sys etc

True. I've done that few times. On different architectures. Worked every time. It should even be faster than rsync if one has lamost full partition.

Or he could resize it to the size a bit over the size used in that partition, copy... and than resize to the full size of the partition. Much faster than rsync.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required