Before users can see files and folders in a Net Folder, a synchronization process must be run so that Filr has information about the files in its database.
Figure 4-1 illustrates at a high level the information and content that get synchronized in Filr. The table that follows the figure describes some of the results and implications of the processes that take place.
The figure does not illustrate functional details. For example, it does not attempt to show the flow of LDAP metadata and file/folder metadata to Filr services for storage and indexing.
Figure 4-1 What Gets Synchronized
Letter |
Details |
---|---|
![]() |
Desktop applications for Windows and Macintosh workstations must download local copies of files and folders before accessing them. Before the files and folders in Net Folders (including in Home folders) can be downloaded, their metadata must be synchronized with Filr. (See the metadata synchronization process indicated in letter D.) For this reason, many Filr administrators perform a manual synchronization when initially setting up a Net Folder so that when users access it from their desktops, they can download the files and folders as expected. Note that the arrow that shows files and folders being synchronized from file servers to desktops bypasses the Net Folders icon. This is because Net Folder files and folders are not stored in Filr. Only their metadata is synced. The files and folders that are synchronized to the desktops come directly from the file servers. Net Folders only facilitate the transfer process, as shown by the dotted line. Files and folders in Filr-based personal storage are automatically synchronized to the workstation’s file system. Net Folders are also configured by default to allow data synchronization with desktop applications. After data is synchronized with the desktops, then as long as the desktops are connected with the network, changes to local copies are immediately synchronized with the file server. If the workstation is disconnected, then when the connection is restored, synchronization is automatic. However, Net Folder download functionality can be disabled. If this occurs, then desktop application users will not be able to view or access the files and sub-folders in their assigned Net Folders from their workstations. (Unlike web and mobile access, desktop applications do not provide Net Folder browsing. Browsing within the desktop applications is limited to local downloaded copies of Net Folder files.) One reason that Filr administrators might disable the download functionality would be to prevent anyone from getting a local copy of sensitive files that must be stored only on the organization’s file servers. |
![]() |
The MySQL database, the Lucene indexer, and Net Folders work together to provide access to data through Filr. MySQL houses the Filr database. The Lucene indexer indexes all of the LDAP and file storage metadata so that search functionality is available. It also indexes file content for searching in folders that have indexing enabled. And Net Folders provide users who have authenticated with proper credentials access to files and folders on the network through the file storage metadata that is associated with them. |
![]() |
Regular LDAP synchronization is essential to timely user access to their files and folders. Some organizations find it sufficient to synchronize LDAP once a day. Others require more frequent synchronization to keep Filr abreast of changes in their identity stores. |
![]() |
Because file and folder activity on network file servers can be in constant flux, and because synchronization needs vary greatly from server to server, Net Folder synchronization is multi-faceted and very flexible. You can set synchronization schedules for each Net Folder Server. The Net Folders associated with that server are then synchronized according to the general nature of the volume or share where they reside. You can also set synchronization schedules for individual Net Folders that will override the server schedules and synchronize the folders either more or less frequently than the server schedule dictates. You can perform manual synchronizations, which is a very useful feature when creating Net Folders, to ensure that desktop application users can download local copies for access. You can enable Just-in-Time Synchronization (JITS) so that each time a folder is accessed from the web or a mobile device, its content is synchronized with Filr. (The desktop applications do not trigger JITS.) |
A Net Folder can be synchronized according to a schedule.
When a Net Folder is synced, the following things happen:
The Filr Appliance connects to the specified net folder server (and path).
Filr then walks the directory structure, collecting meta data about each directory and file as it goes.
For example, it collects the name, size, date, and ACL information.
Filr then stores this metadata in the MySQL database.
Next, Filr sends the name (along with ACL info) to the Filr Search appliances to be indexed.
This information is used for future searches, and so forth.
If there are multiple Filr Search appliances, the Filr appliance sends the information to each Search appliance.
The majority of the synchronization work occurs on the Filr appliance.
After the synchronization of metadata is complete, Filr checks whether the Net Folder is configured for content indexing.
If so, Filr then walks the net folder path again, retrieves a copy of each file from the Net Folder, extracts text from each file, and then sends the text to the Filr Search appliance for indexing.
Although indexing is very powerful functionality, it is obviously CPU- and IO-intensive because each file is processed separately.
The next time the Net Folder is synced, Filr follows the same process for any changes that it finds, such as new, modified, or deleted files and folders.
Any form of network-connection latency has an impact on synchronization speeds. Local Net Folders are much faster at synchronization than remote. The speed difference tends not to be limited by the raw network bandwidth, but is more a function of network latency.
The speed difference between OES and Windows 2012 also has an impact.
There are two modes of synchronization:
Full Synchronization
Just In Time Synchronization (JITS)
For information about these synchronization methods, see Planning the Synchronization Method
in the Novell Filr 1.0.1 Administration Guide.
Before Filr clients can see the files and folders inside Net Folders, Filr must synchronize those files and folders.
For web, iOS, and Android clients, synchronization involves transferring file and folder metadata to the Filr appliance either through a scheduled synchronization operation, or by using just-in-time (on-demand) synchronization.
For desktop clients, synchronization involves copying the files and folders to the desktop, which requires enabling Data Sync.
Because of the differences and nuances involved with these various synchronization methods, it is important to understand them and the way they impact the user experience within different Filr clients.
To learn more and devise a synchronization plan that will best meet the needs of your Filr client users, see the following sections in the Novell Filr 1.0.1 Administration Guide:
If content is added to a Net Folder through a Filr client, then the content is automatically visible through Filr. On the other hand, if content is added to the Net Folder target folder on the file server itself (for example, from a mapped drive on a desktop PC), then either a regular sync interval or a JITS request will be necessary before that modified data is reflected in Filr.
This process can be triggered from a Net Folder Server or a Net Folder.
If synchronization is run from a Net Folder Server, then all of the Net Folders connected with the Server are synchronized. Net Folder Server-level synchronization processes can be executed immediately when needed. Net Folder-level synchronizations, on the other hand, happen when the process is scheduled as shown in the following dialog:
NOTE:The synchronization schedule interval should allow enough time for the synchronization process to complete before another process is scheduled to start. There is no harm if that is not the case. The currently running synchronization overrides any synchronizations that are scheduled while it is still running. Still, it doesn’t make sense to make synchronization intervals too short.
JITS is an unscheduled synchronization that is triggered when users access Net Folders through the web or mobile clients. (The Windows desktop client does not currently support JITS.) JITS makes it possible for users to view the content of Net Folders that have not yet been synchronized.
When a user accesses a directory on a Net Folder that is configured for JITS, the files within that directory are synchronized. Subdirectories are not synchronized until they are accessed.
Net Folder JITS processes run in accordance with a global timeout setting. Home Folders JITS processes are individually configurable.
The global setting is configured as shown below:
This setting is found from the Admin Console under Just-In-Time Sync.
As shown, the setting means that JITS will run for 15 seconds and then return as much information as it has been able to gather.
The users sees the directory information after the timeout value has lapsed.
The timeout value can be any number including 0.
If all files and directories are not found in the required time, then an incomplete list is returned to the user.
If the value is 0, then the JITS session runs in the background and a directory listing is returned as soon as possible. A refresh of the directory listing might be required.
Each Net Folder can have additional JITS-related parameters set, as shown below, but the global timeout still applies.
JITS can be enabled or disabled on a Net Folder-by-Net Folder basis. If enabled, you can specify the Maximum Age for Just-In-Time results to control how quickly a file change on a Net Folder from a non-Filr client becomes visible to Filr users. For example, if a user accesses the directory and JITS has run in the last 30 seconds, then existing information is displayed instead of running a new JITS session.
The ACL age parameter serves a similar function. Because ACL data tends to change less frequently than the files themselves, this value can probably be increased to 86400 seconds (1 Day), meaning that JITS ACL information would only be updated to cache once per day.