It's usually easy to get the original resolution shown. Otherwise, the browser does another image scaling on top, somewhat obfuscating the differences these examples are about. The following examples are most clear if the images are viewed in their original resolution. It joined the ranks of the replaying and I started syncing another image.A Sharper Scaling is a free, high quality image scaling technology mainly developed for upscaling. All the while continuing to replay journals from 25 existing images.

So to help put this in perspective, I began syncing a 4T(1.5 used) image on Saturday morning about 9:30a and it finished on Wed about 10p. Then about 08:30 I began syncing another image. The next 5 hours was spent catching up and then back to what I consider normal replaying. The first 8 hours you can seen that the entire allocated amount (currently capped at 80m) of bandwidth is being consumed because an image was doing it's initial sync. In the screenshots below you can see an image in the syncing process, and images replaying from journal after the initial sync. This does not mean that this is a replacement for good backups! In a disaster situation, (Moon fell on HQ) these images can be promoted to primary and brought up in a fraction of the time needed to restore from a backup. What this provides us is very up to date, crash consistent disk images at the remote location. We are currently mirroring 27 disk images totaling about 11T. Communication is via sd-wan and a 150m broadband internet circuit.

We used the excellent wiki article referenced above by Alwin to mirror disk images from our HQ cluster to our DR cluster located at a remote datacenter.

Instal Find.Same.Images.OK 5.31