Did you try to backup your SSD by booting from an external Paragon Rescue media?Good idea to try from rescue media. Maybe "something" interferes with the work of the BR in a Windows environment. In your case, it would norma must be 1-2 minutes or less. At least it's not clear if the slowing down backup bug lies more on the VSS's or Paragon's side. which don't resolve the performance issue for me. There are several solutions to fix VSS problems, eg. From old days I remember that backups in HotCore mode always performed quickly, on the notch of slightly worsen response of other applications, but no serious issue, especially if run scheduled overnight. It's really pity Paragon HotCore driver as an alternative to VSS was abandoned, as VSS seems not perform reliably and may be the culprit of this really annoying performance issue. The archives were never set to split, tho in certain periods performing at full speed from start to finish. After upgrade the system drive to SSD, again readjusted the start offsets, the backups continued at full speeds about three backup cycles, then switched again to the slow mode where it remains till now. Had the issue with Paragon 15.x falling into the slow mode for no apparent reason, later restored the full speed mode after resizing system partitions and adjusting the start offsets accordingly in PSL. Slowing down backups is an old issue of Paragon Backup that seems still not (if ever) handled by Paragon. Seagate USB 3.0 External backup USB 3.0 backup external drive (Backup drive #2) Seagate 3TB 64MB 3"5 Barracuda HDD (backup Drive #1) ![]() backup license wasn't applied but was applied to other 3 parts of the software) * Had issues with Only some of the licensing being applied (ie. Either software says I'm running the basic free (which I purchased the advanced), or doesn't show the option at all (after rep-applying my license) * Unable to create a Linus boot USB/CD recovery. Honestly hate these minimalist interfaces ![]() * I've had issues with the backup software, that if you run a backup (as a non scheduled), and log out of the user, then the backup exits (looks that this sort of backup execution runs the backup within the current user context, and not as a service I'm either re-installing the software as it was MS uninstalled during the upgrade, or have a corrupt license which I have deal with. * Paragon Backup usually doesn't survive the major windows (twice a year) updates. * Detects some external USB drives as internal drives (not so much a issue as an annoyance :-) * Doesn't seem to save my user/password, so need to keep keying it in to check the license status * The GUI is sometime slow, with switching between functionality. The same backup under a older Acronis 2016 takes under 2 hours, and with a better compression ratio (note. With support wearing you out mentally with tasks to wear you down to the point of throwing in the towel and cutting your (time) losses (aka and switch back to a product you should of never left) it definitely looks like they realize that the product is broken, and are trying to play it off as a machine issue verse a paragon backup issue. which most likely wont help and would generate gigs of data. The third had requested that I capture gigs of procmon output while the (24hour ) backup is running. Have had 2 tickets closed on me while I waited on responses. I included PNG picture at start of backup, after 1 hour,after 2 hours, and around 3 hours (canceled the backup after this)ĬPU is under 10%, backup split out disabled, Setting paragon backup task to CPU Priority to High.Īside: Don't waste your time with contacting Paragon Support. Near the end of the 24 hour backup, throughput is somewhere under 1Meg/sec. After 3 hours, backup throughput is at about 17Meg/sec. Over the last few months, have test with at least 5 external backup drives including a 1TB SSDīackup drive throughput starts out around 100Meg/sec but slowly creeps down. Now with V 16.x, take closer on 24 hours. Previously, backups using Paragon 15, took just over an hour for about 800 GIG (details taken from physical file date/times) ![]() The larger the backup source data, the slower the backup becomes. Note: Smaller backups (say in the 80 GIG range) are slower but complete within an hour or so. Latest version of Paragon Backup 16.5 (including earlier 16.x versions I've tested with) seem to be severally hamstrung in the performance category when backing up larger disks. Purchased "Paragon Hard Disk Manager 16 Advanced" which includes the backup
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |