Best Practices for EasyWorship File Sharing on Network Server or NAS
The goal is to allow several people contribute to content of a schedule for Sunday by adding to the database; and adding recorded media, scriptures, and other slides to the shared schedule. After being bitten a few times trying to have the EasyWorship database and profiles on a network file share, it would be helpful to have others contribute their best practices. The does and don'ts of multiple access file sharing would be very helpful. Here is what I've learned previously:
- Forum Archive: using a shared network drive (August 2015 to March 2019)
- Knowledge Base: Synology NAS Setup (March 2019)
- DON'T put the schedule on a server if it performs backups on recently changed files. We were using Windows Server 2012 and Crashplan Pro. Anytime a schedule changed it created an incremental backup, but locked the file in a way that caused EasyWorship 7 to freeze and not recover. (I'm not certain if the database has this same issue or not.)
- DO schedule server backups to happen when files will not be edited or when in use during worship.
We currently simply use Dropbox as a central shared drive.
Every user configures his/her EW application to the shared database-folder in Dropbox (which is available as a local-map on the PC).
Works just fine for us.
I am now considering migrating to One-Drive.
Good comments, Bill Pritchard.
The network database can be open and edited simultaneously by different computers across the network. However, schedules can only be open in one location at a time. If someone has it open and someone else tries to open it, you will get a message that it's already in use.
@Pauluskerk Gouda, even though Dropbox may be working for you, the way it updates its files when multiple people use it, it will eventually corrupt the database unless absolutely only one person accesses it at a time and it updates online and locally before anyone else accesses it.
If 2 people access it at one time or before it updates, which update will it use? It will create conflicting files and then they won't match with the rest of the database and corrupt it. I hope you are backing it up while it's still working just in case something like this happens.