Buffer size and Transfer speed can also be controlled from the Configuration window. Most actions are accessed from the system tray including adding a new copy task and it has the standard pause / resume / skip buttons in addition to the copy list and several options to deal with errors or file collisions. SuperCopier is an open source transfer utility and is quite similar in looks and functionality to UltraCopier apart from this tool seems to be more stable. It’s a multi threaded program allowing many files to be copied in parallel and has several of the functions you might want from a 3rd party copy program such as pause, resume, verify, profiles, file / directory filtering, multiple sources at once and full command line support. So why do get 3190 MB/s when I backup to a Windows 10 system and only 2333 MB/s when going to a Windows Server 2019 system? I would have expected identical results, perhaps a little faster on the Windows Server 2019.RichCopy is actually a tool developed at Microsoft and was used internally by them to copy files for several years before being made available to download. That's a big difference!Ĭonfused over the speed difference, I ran CrystalDiskMark 6.0 and got almost identical results of 3500MB/s read and 2700MB/s write on the SSD on both systems. Recently I started booting the Eagle system to running Windows Server 2019 and I noticed that I was getting an average speed of 2333 MB/s when I ran the identical backup. ROBOCOPY /MT:1 /MIR /R:0 /W:0 /LOG:G:\files.log /NP /NDL \\Robin\g\HyperV-Exported-Systems \\Eagle\g\HyperV-Exported-Systemsįor several months I have been backing up the Hyper-V systems from the Robin system to the Eagle system and was getting an average speed of 3190 MB/s I use robocopy to backup the SSD, using the command: One system can be dual booted with Windows Server 2019.īoth systems have a separate G: drive consisting of a Samsung 970 Pro 954gb SSD for Hyper-V Linux Systems testing and backup.
I have two Dell 8920 Workstations running Windows 10 Pro for Workstations.
0 kommentar(er)
