Back to Blog
Syncovery synology5/29/2023 It also had a 2nd USB hard drive attached that we were using for a file-level backup (using Syncovery) while we were working through the Synology ABB issue. The problem VM (with the 20TB / 11TB Used data drive attached) ALSO had an external USB hard drive attached (passed through from the host) that held some old archive data for a several-month long project they are in the middle of. Well it looks like I have a solution at long last. I can't think about this any more today, so I'm just going to let it go overnight again and see where we are tomorrow. Speeds very fast from the 20 minutes in, it had copied a total of 317GB, which works out to 40 minutes in, it had copied a total of 605GB, which works out to 60 minutes in, it had copied a total of 607GB, which means for the last 20 minutes, it was copying at only about 70 minutes in, it had copied a total of 609GB, which means for the last 10 minutes, it was copying at only about 120 minutes in, it had copied a total of 617GB, which means for the last 50 minutes, it was copying at only about 2.7MB/s I restarted the backup and here are the results from the first 2 hours: I normally leave this enabled, but read that this setting WOULD have a definite impact on speed, so disabling it seemed like the right answer. Lastly, I disabled Transport Encryption Mode. I don't think that would affect anything ABB is doing, but it's a standard setting I use, so I enabled it anyway. Next, I went through all of the various Synology settings again and I found that I had NOT enabled Fast File Clone. I know this is a ton of small files, but I was certainly hoping for faster. This took 45 seconds, for an average speed of 35.6MB/s. I tried copying a folder from the VM to the Synology using Windows Explorer - total size 1.6GB, containing 72 subfolders and a total of 2260 files. From the Host, I've averaging 4Gb/s with a single stream and 9Gb/s for 4 streams. Just for fun, I installed the SynoCLI app so I could run some iperf tests. I also added 500MB/s throttling to the ABB settings. Update: I removed compression from the job & rebooted everything this weekend - the Synology, the switch, the individual VMs and the HyperV Host. Now I'm thinking I need to ditch compression. Although I'll admit, I'm surprised at the amount of space saved by dedup alone - The storage tab says 8TB written so far (I've restarted the job 3 times) and 6.3TB saved by deduplication, with only 225GB saved with compression. Lastly, I felt I had to use compression - 11TB dataset going to a 24TB NAS hoping to keep several versions in the retention policy. Speaking of stopping the job.do you know exactly what happens if I cancel a job before it finishes and then start it again? Does it start over from the beginning, or where it left off? I never worried about that before, but with this one, it would be helpful if I knew I wasn't starting all over again from scratch with a restart. Can I do this hot, or should I stop the job make the change, then start the backup again? Does the number matter? I'll just limit it to 500MB/s, then. Doesn't hurt to try it though - I'll try anything at this point. I hate waiting, plus I can't have no backups while we wait, so I've kept the temporary solution going that we had in place while waiting for the new NAS, which is a nightly file-level backup to an external drive using Syncovery - which takes about 30 minutes,, I know you have this setup out there for some clients - do any of them have this much data? And if so, did you also have this agonizingly-slow initial run? Have you found anything you can recommend to speed things along? Synology support says they don't see anything wrong with the setup, so I should just wait it out, but it's driving me crazy - haha. I am doing deduplication & compression, which slows things down, but I'm not encrypting.and I know I get way better performance than this at my other sites that have less network bandwidth and lower-powered equipment. As of this morning, it shows 36% complete, as of yesterday morning, it was 35% complete - so maybe 65 more days until it's done! Plus, now that I'm hyper-focused on this long-running job, I'm noticing how little "in-progress" data you actually get with ABB. At this rate, I'm looking at at least a couple of weeks for the initial backup to finish. Both the NAS and the server VM have lots of horsepower and network bandwidth, but I'm only getting 8MB/s progress after 4 days running the initial backup job. I did a new setup last week for a client with a comparatively large backup footprint about 11TB before dedupe or compression. Seriously, no complaints at all.until now. I've got this solution out there for about a dozen clients and it is working very well.
0 Comments
Read More
Leave a Reply. |