![]() To maximize performance and reliability, MirrorSync can be used in a clustering configuration, where two or more servers are running at the same data center and synchronized bidirectionally so that they all contain the same set of data.In this configuration, MirrorSync should be set to sync very often, such as every 30-60 seconds. Each workgroup works at full LAN speed on their own FileMaker Server, and MirrorSync uses a bidirectional sync to take care of keeping the servers in sync with each other, so that each workgroup can see and edit changes made by the other group. ![]() For groups of users at multiple locations, MirrorSync should be used in server-to-server mode, where an identical copy of the database is installed on FileMaker Server in each location.In the event that the production server goes down or suffers database corruption, the backup server will be ready to immediately take over. By installing MirrorSync on two computers running FileMaker Server, you can have your main production server constantly syncing with a backup server with a one-way server-to-server sync. MirrorSync is a great solution when server uptime must be maintained.The user could sync when they first came into the office, work on their local copy throughout the day, and sync at specified times (or on demand) to push and pull the latest data to the server. MirrorSync allows each user to take a local copy of the database which would run on the user's machine and not be affected by the WAN performance. ![]() If, for example, you have multiple users connecting to FileMaker Server over a wide area network (WAN) you could notice a substantial slowdown, as every change is immediately written back to FileMaker Server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |