Using Storage Sync replicates data bi-directionally from Cloud File Server (CFS) to a Local File Server (LFS). However, some users may still choose to backup their data from their Storage Sync shares for added security. This is not uncommon but it is important to understand what triggers synchronizations.
A Storage Sync application watches for data changes through events. Events are triggered by attribute changes to your files.
Understanding the events that can trigger synchronization is key.
- Any modification to a file, including file attributes
- Modification of permissions to a file or directory
- Adding a new file or folder
- Removing a file or folder
- Moving or renaming a file or directory
In summary, any modification to any file, file attribute, or directory attribute triggers an event.
There are many applications that can cause file attribute changes. This is typically not an issue for a small number of files, but can have a severe impact on larger datasets. The effect can be as simple as performance degradation but can escalate to more serious problems such as high network or hardware resource usage, long running syncs, and creation of unwarranted versions on your cloud file server consequently using up more storage.
A few applications are known to change data attributes, which may not be apparent to the user.
- Anti-virus software
- Backup applications (e.g. Symantec Backup Exec)
- 3rd party sync applications (e.g. ViceVersa)
If you are planning on using backup, 3rd party synchronization agents, or anti-virus software that would generate spurious update events, there are several steps you should take.
WARNING: Making the following configuration changes can cause serious system issues or potentially disable your Storage Sync instance. Please contact us if you are not comfortable in making these changes.
1. Backup or create a copy of your current configuration file prior to making the changes.
2. You should designate a particular user that will do the backups or synchronization and elevate that user to an administrator. You can do this by
- In the case of SS VM editing /etc/samba/smb.conf file and adding this user to the verb “admin users =”. In the smb.conf file this would look like
admin users = egnyte_smb_admin_reserved backupuser
- In the case of NETGEAR NAS do the same change in /etc/frontview/samba/addons/addons.conf file
3. Reload the Samba configuration
- In the case of SS VM run /etc/init.d/smb reload
- In the case of Netgear NAS appliance run /etc/init.d/samba reload
You should be fully configured for your backup application now. Note that the above admin user that you designated should only be used for the specific application. This user will have root access and will not be sanctioned by our file system permission enforcement. All file system modifications done by this user will not be tracked by Egnyte file system event monitor and as such will not be synchronized to the cloud.