This message was deleted.

Can you clarify what you’re envisioning? We’re using Google Cloud Platform, which handles redundancies, both for connectivity and storage, so what you seem to be describing would be a non-issue (i.e. your workspace/apps are not saved on a NAS in the office).

If we had to restore an Airtable base from a snapshot it would be "restored" into a new table with new IDs, etc - This would then need us to spend considerable time (I presume) setting back up all forms, list views, customisations, etc within Stacker. I wanted to know if there was a way to backup the configuration of Stacker views, forms, etc that would expedite this process should the worst happen.

Hmm. That’s interesting. So, I will double check with the team, but I’m fairly certain that it wouldn’t pose any problem for Stacker as long as the schema remains the same — which sounds to be the case from your description. Deleting a data source in Stacker and setting it up again, even with the same schema, would result in any layouts being lost. But it’s relatively common for customers to replace an existing Airtable connection with a new one using the same schema (duplicating into a new base), thus preserving all the work they’ve done on the app in Stacker — only the destination is different.