Backblaze is going to be the last piece of our new system. How do you like it so far Kevin?
We're still on Google Drive. It duplicated thousands of files on us. Now it just duplicates a few folders a week. Recently, they helped us test third party software to seek out the dupes. They told us the duplications are a feature of the program, you know, to duplicate a couple years' worth of art and order information without indicating which files are duplicates of which is a pretty great feature.....then they told me our domain users were doing it manually....eventually, after countless emails and calls I gave up on getting them to cover the costs of the damage to our file structure and we ate a lot of payroll and are still losing some every week on the issue.
Long story short- do not use Drive for actual storage if you are a medium to larger organization.
Web and web app connectivity is very good however. API calls can be used to tie in other apps via triggers and save some duplicate entry work as you process jobs.
Moving forward Drive will only be for jobs in our active pipeline, in order to keep good connectivity to other web apps. Once approved, final files will be stored locally as they are generated. We've begun storing all our RIP'd .tiff files on the server already and will migrate the rest soon.
Our server/backup structure:
1.Mac mini with mirrored platter drives
2. 2x thunderbolt rugged drives, one of which gets swapped out off site, both are carbon cloning the platters
3. web backup at night.
Low footprint/cost and in a pinch we can swap any relatively current gen mini out and clone it back from the thunderbolt drives to function as the server if the whole server computer goes down.
