Mac Disk Clone Software Free
Clide Birkner
I have read through the support forum and also read Headless backup. The Headless backup seems dated as it was done in 2015 and consists of 22 steps and ends up with the image on a data drive. You then have a number of additional steps to burn that image to an external SSD.
I run OMV5 from a 32GB SSD and have recently purchased 2 identical SSDs. I would like to clone the system SSD to each of the backup SSDs. Having read the Clonezilla Live Doc for this disk-to-disk process (consists of 11 steps) I am unable to see how to do it in OMV using the built in version of Clonezilla?
macom Thanks for the list. However your 8 steps only gets to the first step of Clonezilla - then need to complete the next 8 to actually get a backup.
I had already done your steps, at least up to 7, and after getting Clonezilla Live started I ran into the problem of not finding my backup drive listed in the available options.
So now that I have at least one good backup of the OS drive I will follow your steps to see if I can also do the same from Clonezilla Live. More to follow...
So....I connected the computer to a monitor and a keyboard and everything is still the same, it goes directly to clonezilla and doesn't show me the grub menu. Do I have to press any specific key for the menu to appear? Sorry but this is the first time something like this has happened to me.
PS: sorted out. I created a bootable USB with Super Grub2 Disk and selected the grub corresponding to the OMV. Then I entered the OMV page and set the OMV kernel to default, which strangely was already selected but didn't work. I've done this so many times and it's never happened to me, but there's always a first time.
Yep
Take care about the UUID (fstab and Grub part) if you are using partition and done a simple dd.
Have a look there :
[How-To] Restore OMV system backup made with openmediavault-backup plugin
The share is there, I can see it on any system through SMB. There are other drives present as well but none are showing up when clicking on the pulldown for the destination. They are all present when I click on the Source.
As far as I know, this plugin is used to clone the system disk from the GUI. So I think you need to connect an empty disk/SD card/USB pendrive to be able to clone, that's why the GUI is not showing you possible destinations of the cloned disk. Try it by connecting an empty disk.
There's been a number of questions regarding disk cloning tools and dd has been suggested at least once. I've already considered using dd myself, mainly because ease of use, and that it's readily available on pretty much all bootable Linux distributions.
What is the best way to use dd for cloning a disk? I did a quick Google search, and the first result was an apparent failed attempt. Is there anything I need to do after using dd, i.e. is there anything that CAN'T be read using dd?
Be aware that while cloning every byte, you should not use this on a drive or partition that is being used. Especially applications like databases can't cope with this very well and you might end up with corrupted data.
CAUTION: dd'ing a live filesystem can corrupt files. The reason is simple, it has no understanding of the filesystem activity that may be going on, and makes no attempt to mitigate it. If a write is partially underway, you will get a partial write. This is usually not good for things, and generally fatal for databases. Moreover, if you screw up the typo-prone if and of parameters, woe unto you. In most cases, rsync is an equally effective tool written after the advent of multitasking, and will provide consistent views of individual files.
However, DD should accurately capture the bit state of an unmounted drive. Bootloaders, llvm volumes, partition UUIDs and labels, etc. Just make sure that you have a drive capable of mirroring the target drive bit for bit.
When using dd to clone a disk which may contain bad sectors, use conv=noerror,sync to ensure that it doesn't stop when it encounters an error, and fills in the missing sector(s) with null bytes. This is usually the first step I take if trying to recover from a failed or failing disk - get a copy before doing any recovery attempts, and then do recovery on the good (cloned) disk. I leave it to the recovery tool to cope with any blank sectors that couldn't be copied.
Also, you may find dd's speed can be affected by the bs (block size) setting. I usually try bs=32768, but you might like to test it on your own systems to see what works the fastest for you. (This assumes that you don't need to use a specific block size for another reason, e.g. if you're writing to a tape.)
Of course, make sure that you have proper permissions to read directly from /dev/hdb (I'd recommend running as root), and that /dev/hdb isn't mounted (you don't want to copy while the disk is being changed - mounting as read-only is also acceptable). Once complete, image.img will be a byte-for-byte clone of the entire disk.
There are a few drawbacks to using dd to clone disks. First, dd will copy your entire disk, even empty space, and if done on a large disk can result in an extremely large image file. Second, dd provides absolutely no progress indications, which can be frustrating because the copy takes a long time. Third, if you copy this image to other drives (again, using dd), they must be as large or larger than the original disk, yet you won't be able to use any additional space you may have on the target disk until you resize your partitions.
As far as issues or gotchas go, dd, for the most part, does an excellent job. However, a while ago I had a hard drive that was about to die, so I used dd to try and copy what information I could off it before it died completely. It was then learned that dd doesn't handle read errors very well - there were several sectors on the disk that dd couldn't read, causing dd to give up and stop the copy. At the time I couldn't find a way to tell dd to continue despite encountering a read error (though it appears as though it does have that setting), so I spent quite a bit of time manually specifying skip and seek to hop over the unreadable sections.
I spent some time researching solutions to this problem (after I had completed the task) and I found a program called ddrescue, which, according to the site, operates like dd but continues reading even if it encounters an error. I've never actually used the program, but it's worth considering, especially if the disk you're copying from is old, which can have bad sectors even if the system appears fine.
The reason behind this is that, on read errors, dd keeps trying and trying and trying - potentially waiting for a long time for timeouts to occur. dd_rescue does smart things like reading up to an error, then picking a spot further on on the disk and reading backwards to the last error, and dd_rhelp is basically a dd_rescue session manager - cleverly starting and resuming dd_rescue runs to make it quicker again.
The end result of dd_rhelp is maximum data recovered in minimum time. If you leave dd_rhelp running, in the end it does the exact same job as dd in the same time. However, if dd encountered read errors at byte 100 of your 100Gb disk, you'd have to wait a long time to recover the other 9,999,900 bytes*, whereas dd_rhelp+dd_rescue would recover the bulk of the data much faster.
Note that depending on the size of disk, speed of cpu on source, speed of cpu on destination, speed of network, etc. You may want to skip compression, or do the compression on the remote side, or enable ssh's compression.
Of course, make sure that you have proper permissions to read directly from /dev/hdb (I'd recommend running as root), and that /dev/hdb isn't mounted (you don't want to copy while the disk is being changed). Once complete, hdb.img will be a byte-for-byte clone of the entire disk.
This will do nothing in the watch output window, but back in the original DD shell, DD will start outputting status reports every 10 seconds. You can change the -n 10 in the watch command to any other time frame of course.
It works by storing the pid via file descriptor 3 in /tmp/pid, which is then used for the subsequent kills with signal USR1. A wrinkle was to filter the output of the progress on stderr to only one line via filtering stderr through a subshell.
At first, destination should not be in use, secondly source should be not used, or remounted into read only mode. Otherwise copy will be damaged.If remounting is impossible, please make bootable drive (hdd/ssd/pendrive) any linux live distro. I prever knoppix, but this is your choose. If it is possible, you can boot or change system level into 1, for single user mode, or you can directly reboot system into single user mode, it is distro depended.If you'll clone only one partition, this partition should be unmounted or remounted into RO:
You must identify source and destination device. please look at the dmesg, here is stored all needed info about device, with vendor etc. alternatively identifying can be based on device size, if it is different.Next, destination should be the same or bigger than source. you must calculate source, for example:fdisk -l /dev/sdaexcept partition geometry (there can be GPT), you will fetch:1. total disk size wigh GB and bytes2. historical geometry and total sector number, very important info3. block size in bytes, usually it is 512.
c80f0f1006