Sure, good point. To produce a perfect form and function replica would not be practical, you would go broke. Agreed.
All I’m saying is, don’t let the perfect be the enemy of the good.
need to replicate functionality
Not really. I just want to get my company documentation back out. A lot of our people spend a lot of time writing this stuff, and yet it feels uncertain since it can all vanish at any time.
I don’t need automatic table filtering and webhook links to external services and all that jazz. It’s just wiki holding company documentation, and some tables holding project todo lists. Plenty of pictures. It’s a wiki.
It could all render out to dumb ol’ markdown. The worst effect would be, for example, a fancy user pick list column showing “Joe” would revert to simply the text “Joe” Tables would not be sortable, just static rows and columns.
But the data would be there, disaster would be averted. The instructions on how to operate the nitrogen pressurizer, with it’s photos, would be there. The instructions on how to enter an RMA would be there, along with screen shots of the RMA entry screen. The west coast project list would be there. Page links would work. That kind of thing.
The existing Coda backup is awkwardly placed (only one user can do it) and what it produces is unintelligible. The whole-doc PDF export has all the text (yay!), but the links are gone and the pictures are all tiny. The PDF is definitely better than nothing though, and we are glad to have it.
are you worried about Facebook
We don’t store any company resources on facebook. Do companies do that? Maybe some do.
google photos
We don’t store any company resources on google photos.
slack
We don’t use slack, but I understand it to be a type of company chat. I think the need to keep backups of company chat would depend on the business? Maybe lawyers need it? Maybe slack does have backup, I don’t know.
We have a different company chat, and I admit we do not keep backups of it. It would suck a little if we lost it, but not much.
basecamp
same comment as above
gmail
We don’t use Gmail for email, but we use our company mail server, and we keep very good backups of that. We actually needed to use them once, and they worked!
sharepoint
We don’t use sharepoint, but a buddy who does says that he keeps backups of his server.
dropbox
We don’t use dropbox, but we do use google drive, which is similar. It can be instructed to replicate all files locally, so if you back up the local files, you then have a backup copy of the google drive. We do this. But we avoid storing critical company info there – we just use it for easy comms with subcontractors.
etc, etc
We keep backups (on and off site) of our ERP system data, our files and indexed documents, our devops repos, various websites and our application servers.
This is all pretty ordinary. Keeping backups of company resources is just what you do.