RossEvans wrote:Technically, using a proper backup server in a remote data center, professionally administered, is a good solution. It seems that the church is moving toward that solution with its own central servers, but that solution is so local backups are still a good idea.
When you say "not yet complete and comprehensive" is it because you don't think once a month is enough or because it's only for MLS?
I was only talking about MLS. There still are some holes in the content being uploaded to headquarters (HT/VT, etc.). And the frequency of the MLS backup-set file monthly is insufficient to be the primary backup, only a last-ditch fallback. We really need daily backups whenever MLS data changes, which is most days that MLS is accessed.
It would be nice if the backup files created by MLS were always uploaded automatically to headquarters servers upon exit from the application. But for whatever reason (growth of that file, server-side bandwidth on Sundays, perhaps?) that solution has not been implemented. So the local backups still fill that void:
1) Backup from MLS to C: to handle simple content-level restores of MLS application data.
2) Copy that to a secured USB drive (in case the C: drive fails).
3) Copy that redundantly to another USB drive carried offsite by a clerk (in case the building burns down).
4) Fall back to the headquarters backups and reenter data as needed (in case that clerk was in the building when it burned down).
But since you mention it, some solution to back up the non-confidential stuff on the C: drive, while not as mission-critical, would also be nice. In our case. we really should at least do a simple copy or zip archive of the relatively small Documents folder to the USB drive, but we haven't been doing that.