The Mailchimp servers have gone down today, so unable to use the API reliably. Obviously, in a worst case scenario we would lose our subscriber base to the system if their data was wiped or the service went down permanently. Everything else is reconstructible quite easily, it is only the subscribers that are a high risk dataset stored on the Mailchimp servers.
Although this is highly unlikely, would be good to have a backup script in src-static that is run every time we update static files, but also running on a CRON job every week or so to create a subscriber backup. It would be very simple, as audience$mc_members() already extracts members in a list from the JSON format and we could just save as a JSON file directly to Azure.
The Mailchimp servers have gone down today, so unable to use the API reliably. Obviously, in a worst case scenario we would lose our subscriber base to the system if their data was wiped or the service went down permanently. Everything else is reconstructible quite easily, it is only the subscribers that are a high risk dataset stored on the Mailchimp servers.
Although this is highly unlikely, would be good to have a backup script in
src-staticthat is run every time we update static files, but also running on a CRON job every week or so to create a subscriber backup. It would be very simple, asaudience$mc_members()already extracts members in a list from the JSON format and we could just save as a JSON file directly to Azure.