cnlop.blogg.se

Fastcopy tuning
Fastcopy tuning










fastcopy tuning

With a large block size, one disk remains idle while the other is reading or writing. With a small block size, dd wastes time making lost of tiny reads and writes.

fastcopy tuning

The conclusion from this benchmark is that the choice of block size for dd matters (but not that much), and cat automatically finds the best way to make a fast copy: dd can only slow you down. I ran benchmarks a while ago, copying a large file rather than a partition, between two disks (on the same disk, relative timings are different): dd bs=64M 51.3 To copy a partition wholesale, use cat instead of dd. With that in mind, this is what I got (I only tested Write speed to the Device, read is typically higher): Connected Device - Connection Type - Speed (Write Speed) This tests can change depending on Device used, connection type, motherboard, type of connecting cable, filesystem type and more. Doing real tests revealed they are between 40% to 80% of that raw speed. This were my results, but first we need to know that the theoretical speeds for many transfer rates (Raw speeds) are just that, theory.

#Fastcopy tuning pro#

I was using the Asus Z87 Pro and the Intel DZ68DP. I did a couple of tests with the connection types you were using and others I had available. With pv or a very optimized bs parameter, you can do a 4 TB drive in less than 7 Hours (6 Hours 50 Minutes at a current speed of 150 MB/s). In regards to HFS+ I would not know, am just trying to help on the "speed" part.

fastcopy tuning

The nice thing about pv apart from the speed is that it shows the progress, current speed, time since it began and ETA. This has to be done of course from root: pv /dev/sdb There is also pv (Needs to be installed first) that checks for the fastest speed on both drives and then proceeds on cloning. Adjusting the bs parameter can increase the speed, for example, I have 2 HDD that I know have a read/write speed greater than 100 MB/s so I do this: dd if=/dev/sda of=/dev/sdb bs=100M In my experience, I don't think there is something faster in the command line as dd. When I made my first clone, I did all of the partitions except HFS+ and it went very quickly. I have tried Clonezilla (and it was MUCH faster), but it does not support HFS+ smart copying, which I need. I need to clone the following partitions (including UUIDs) Is there a way to run this drive copy that takes less that 96 hours? I am open to using tools other than dd.

  • SATA (If I find/buy a cable, gotta love laptop CD drives).
  • USB3.0 (If I find my other drive caddy).
  • Gigabit Over-The-Network clone (Really do not want to even try this).
  • I might be able to use the following protocols: dev/sda is a local drive and /dev/sdb is a remote caddy. In these scenarios (i.e.I am doing a dd on two identical drives with this command: dd if=/dev/sda of=/dev/sdb bs=4096īoth hard drives are the exact same model number, and both have 1TB of storage space. In addition if fastcopying a single file and the destination file already exists the destination file will be removed and replaced by the result of the fastcopy command. When fastcopying directory trees (or entire mtrees) if the destination directory (or mtree) already exists the destinations current content will be removed and replaced by the results of the fastcopy command.
  • Files created by fastcopy will de-duplicate perfectly against existing data on disk (as they will reference the exact same physical data as source files) - due to this compression statistics for the files may show inflated ratios.
  • Fastcopy of each file is extremely quick (as the operation only involves manipulation of file metadata and no physical backup data is read/written to disk) - it is much faster than using an external client to read source files/write destination files.
  • Cloning the metadata of existing files at the location given as the source to the new files at the destination.
  • Creating a brand new file/set of files at the location given as the destination.











  • Fastcopy tuning