![]() ![]() This is because FileSync 4.0.11 and newer works by detecting changes and pushing out changed files, rather than having the secondaries doing a file-by-file comparison and pulling the changes. You can change this time by referring to this document.įor FileSync 4.0.11 and newer, the sync interval is set to 1 minute. For FileSync 3.4.5 and older, wait the default 10 minutes for it to sync over.Create a realm on the secondary server, using the realm management tool.Create a realm on the primary server, using the realm management tool.The proper way to use FileSync is as follows: If the time-stamp on a file is newer on the replica server than the primary server, FileSync 3.4.5 and older will not sync that file FileSync 4.0.11 and newer WILL overwrite the files on the secondary. Keep in mind that in a primary-replica configuration that you should only make changes to the primary server. It's important to know the proper way to use FileSync. So you will need to copy company-logo.jpg to SecureAuth1\Images\ before FileSync will replicate that to all the realms in the secondary server(s). ![]() When you installed Filesync, you specified SecureAuth1 as the Template realm. The "Template" realm is specified when you install FileSync on the primary server.įor example, if you add company-logo.jpg to Images\ and want to sync it. HOWEVER, new files that do not exist previously MUST be placed in the Template realm first before Filesync will start syncing. This will sync files from the Images folder. You can add new folders to sync by adding a new key like this: The SecureAuth0 folder contains a file called Paths.list - this file controls what is actually copied by FileSync. Meaning, if you have SecureAuth6 on your primary appliance, you must create SecureAuth6 using the realm management tool on the replica appliance in order for FileSync to pull the settings.įileSync 4.0.11 and newer do not have the above limitation. Changes are propagated to other servers only after a change is made on the primary (in a primary-replica configuration), or after a change is made in general (in a multi-master configuration.)įileSync 3.4.5 and older cannot create realms/folders. Multi-Master (3.4.5 and older): In a Multi-master configuration, all SecureAuth IdP Appliances are peers a change made on any node of the cluster propagates to the rest of the cluster nodes (this feature was deprecated after 3.4.5).Primary-Replica: In a Primary-Replica configuration, one SecureAuth IdP Appliance is the Primary node and all changes for the cluster are made there.Node: A specific SecureAuth IdP server in a FileSync cluster.Cluster: Two or more SecureAuth IdP servers running the FileSync service.Lets go over FileSync terminology before moving forward. The FileSync service is an add-on to the SecureAuth IdP product that can be used to keep configuration information synchronized between members of a cluster.įileSync can work in either a primary-replica configuration, or a multi-master configuration. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |