Hello

We have a MirrorSync installation with 7 configurations and 144 devices syncing. One of the configurations data file is 80gb. So we are using a fair amount of disk space.

We are interested in how we can 'trim' down the files MS generates - *safely*. So, is there any guidance on how to cull these files?

Thanks, Mark

The only way to reduce the size of the mirrorsync.data file is by resetting the sync data.

You can safely delete the .log files (there are probably thousands of them), but keep them for at least a two week previous window. They are necessary if you need to repair the sync data, but only for a week or two (we make a backup every week).

Perfect, thanks.

On 7/11/2017 at 12:22 PM, Jesse Barnum said:

The only way to reduce the size of the mirrorsync.data file is by resetting the sync data.

 

Can you elaborate on this a little more? 

We are running into issues where this file is nearing 2GB. Is that normal?

 

Also, while deleting log files, as you mentioned above, does MS or FMS need to be stopped at all?

Thanks

Edited January 10, 20196 yr by MileFaker3000

2 gigabytes is definitely within normal range for a busy sync configuration.

To reset the sync data, you can right-click on the name of the configuration and select that option - however, I don't recommend it because it will require distributing new offline files to all of your users, and it doesn't sound like your sync data is that big to start with.

When deleting log files, you do not need to stop any processes.

We currently have a mirrorsync.data file that is 106GB, this might be outside that range you mentioned above.

Should we be concerned about this?

 

Thanks.

Edited January 14, 20196 yr by Jason Adams

What version of MirrorSync are you running?

MirrorSync 4

MirrorSync 4 grows sync data at a much faster rate than 5. You can compress the sync data by right-clicking on the name of the configuration, that will probably shrink the size of the file dramatically. Once you've upgraded to 5, you'll probably see that the sync data doesn't grow much at all, and compressing it in version 5 is unlikely to make a significant difference.

Good to know, thanks.

Will compressing the sync data file require redistributing offline files, or is it only "resetting" that requires the re-distribution.  We have a solution with several hundred iPads around the globe using it- so re-distribution is a huge deal.

Compressing the sync data file does not require redistributing new offline files. However, users will not be able to sync while it's compressing, and it can take several hours if you have hundreds of users. If you created your sync data starting with MirrorSync 5, compressing the sync data will have a very minor effect. If you are running version 4, or if you migrated from 4 to 5 and have never compressed or reset the sync data, then it will probably compress the data significantly.