I have been using EASUS TODO BACKUP (FREE) for several years and recently had a system failure and needed to rebuild. There are image based recovery tools and there is also a file based recovery operation from the backup files that the program creates. The backup format uses the file extension .PDB. There is a windows shell extension that actually lets you browse and open the pdb files much like Windows explorer lets you browse Zip files as if they were folders, along with some "extra delays" as it reads/indexes the pdb content. Right clicking from that explorer extension in windows explorer windows, lets you restore to "original location" or to any designated path. So far so good.
My problem is that when I want to restore the entire disk (330 gb compressed, about 600 gb uncompressed) the restore speeds are glacial. The restore process runs for over 80 hours before even showing any percentage completion, does not actually show the elapsed clock time, I just know I started this operation on Friday at 1 PM and it's now 8 AM monday morning local time, and it's been running, and says "31% complete" and estimates 88 hours remaining. The control panel power settings on this PC are set to never sleep/lock, but the screen is being allowed to go dark to avoid burn-in on the panel.
My question is, has anyone completed large restores to "c:\Recovery" (not original location) with OTHER backup software that offers a hybrid approach (backing up to files similar in nature to the Easus PDB files) that has a less insane restore speed for "restore 600 gb files"? Note that to remove any speed problems CAUSED BY THE EXTERNAL USB disk, I copied all the backups onto my main system SSD, which is a very fast modern NVME ssd. (Samsung 2 tb 970 evo plus). All the slowness is due to the easus program code itself and its navigation of these pdb files. I can restore a set of <1000 files totallying 10 gb or less in minutes. It's just when you start doing the "entire drive C and everything underneath it", it becomes slow.
The actual file restore process is managed by something called TbRestore.exe which seems to burn ONE CORE (on my pc, fixed 8% cpu usage) as if the developers at EASUS are stuck in 1998 and have implemented file restores that are single threaded, synchronous crawls. The disk is barely being read, less than 15 MBytes/sec. In short, I could write a better backup system than this with batch files.
My post has two points:
1. opinion advanced: if file recovery matters to you, avoid Easus TODO if you have 300+ gb of data.
2. question: What has FAST file based recovery for 300+ gb data backups?
My problem is that when I want to restore the entire disk (330 gb compressed, about 600 gb uncompressed) the restore speeds are glacial. The restore process runs for over 80 hours before even showing any percentage completion, does not actually show the elapsed clock time, I just know I started this operation on Friday at 1 PM and it's now 8 AM monday morning local time, and it's been running, and says "31% complete" and estimates 88 hours remaining. The control panel power settings on this PC are set to never sleep/lock, but the screen is being allowed to go dark to avoid burn-in on the panel.
My question is, has anyone completed large restores to "c:\Recovery" (not original location) with OTHER backup software that offers a hybrid approach (backing up to files similar in nature to the Easus PDB files) that has a less insane restore speed for "restore 600 gb files"? Note that to remove any speed problems CAUSED BY THE EXTERNAL USB disk, I copied all the backups onto my main system SSD, which is a very fast modern NVME ssd. (Samsung 2 tb 970 evo plus). All the slowness is due to the easus program code itself and its navigation of these pdb files. I can restore a set of <1000 files totallying 10 gb or less in minutes. It's just when you start doing the "entire drive C and everything underneath it", it becomes slow.
The actual file restore process is managed by something called TbRestore.exe which seems to burn ONE CORE (on my pc, fixed 8% cpu usage) as if the developers at EASUS are stuck in 1998 and have implemented file restores that are single threaded, synchronous crawls. The disk is barely being read, less than 15 MBytes/sec. In short, I could write a better backup system than this with batch files.
My post has two points:
1. opinion advanced: if file recovery matters to you, avoid Easus TODO if you have 300+ gb of data.
2. question: What has FAST file based recovery for 300+ gb data backups?
Last edited: