Backups to the Cloud are great as long as you backup the backup folder and not the live FileMaker database folder. FTP works also or however you want to copy them.
360Works had a nice backup program aimed just at FileMaker called SafetyNet that backs up to the Amazon S3 Cloud (I hear the new version may also back to Glacier).
I've never used BackBlaze, but I've used others like Arq.
TimeMachine is fine for FileMaker backups... just make sure it is of the backups and not that it omits the live FileMaker folder just like with virus scans or any other backups.
Just treat it like any datafile with the exception of live hosted files.
Any type of backup will work.
Wherever you back your files up to, make sure the database you are developing is hosted on FileMaker Server. You can schedule your backup up as regular as you want, then you can decide what you want to do with the backups.
You can use one of many backup programs to copy the files to a NAS or to the cloud, or the NAS first then the cloud.
When developing, it is always a good practice to have a second system as a FileMaker Server, hosting your project. It doesn't need to be powerful, but any crashes or environmental problems with your system, should avoid corrupting your development hosted on the server.
You said "’i've been working on a big system for a longtime. I’m nervous if my computer dies I would need to make sure my back-up is corruption free"...
Suggest that you read up on risk management..
1. Develop a set of risk scenarios from best to worst.
2. Define the impact to the business and recovery cost (time, effort, money, whatever cost has meaning here) if these scenarios actually occurred.
3. Assess the probability of those risk scenarios actually occurring.
4. Make an informed business decision on what risks to mitigate and how to mitigate them.
p.s +1 to the suggestion to develop only on FMS.
To build on what Kris is saying: The answers to 1 through 4 will give you budget to work with to mitigate the risk. In other words: how much would it cost me if I lost everything ==> how much am I willing to spend to avoid it.
off-topic -> on the same subject, in the site of BackBlaze
• Java being responsible for 91% of security attacks comes from a Cisco's 2014 Annual Report.
I use dropbox to backup copies of my databases I'm working on. The issue with a file getting corrupt in the cloud is from multiple users trying to open the file at the same time from the cloud. Another issue that can occur with dropbox is when files are synced to the cloud they are copy to another folder, usually under My Documents on a PC before synced to the cloud. (I'm not sure about Backblaze because I haven't used) This happen with all computers linked to the dropbox account. The problem that can occur is that one computer is syncing, another user access the copy, so this partially sync file from the first user is synced to the second user. Now there are different version (data) of the same file, so no one has the correct file.
You have to use care when backing up your files. I think a service like dropbox is great for backing up files under development, but with a live data system as other users have stated, I would use filemaker server backup then move copies of those backups.
Great info guys,
I’m located in Los Angeles and we are going to have a dedicated server in North Carolina with PointInSpace.
Do you see any issues if I use this remote server for developing? Would distance be an issue ?
Physical distance is not usually an issue but the infrastructure in between physical points is always a concern. Generally a business that provides remote services will have have some kind of service level agreement. But they can not control infrastructure in between their business and yours.
Folks developing on FMPS, would you develop if the server was on a remote location?
It is a lot more risky; especially if a network interruption happens at the time you commit schema (fields, tables, layouts).
I would avoid this setup. Those interruptions are lot more likely across the internet then on a local LAN.
If you can't / won't then do a lot more backups then you would otherwise do (every 5 mins, 10 mins, however much work you are willing to lose).
The only time I develop on a hosted solution is when I have a current backup and the change is very minor OR in the early stages when I'm working with a client on some refinements and they want to know "can you move the field over here a little, etc". I treat that as a test copy knowing I'll do the final work on a local copy. It is much safer to do your development on a local copy then upload it to server.