It looks like you're new here. If you want to get involved, click one of these buttons!
I'm interested in finding out how Sendy is backed up on the Amazon server. I have zero experience with Amazon so your advice would be most welcome.
I'm interested in performing a regular automated backup as I would on my usual web hosting. My websites are backed up daily and I would like to do similar for Sendy and the contacts in the lists. You can imagine losing all of your hard earned contacts due to something going wrong could be devastating.
Does Amazon do an easy to use automated backup and restore?
Many thanks in advance
I am not an expert, but the backup can be just the SQL database as the PHP files can be downloaded from Sendy again at any time (assuming you maintain a license). My limited experience of restoring AWS full server backups is that they do not work, or to get them to work requires extra tech skills beyond those needed to follow the AWS docs. If your other websites are WordPress, then the UpdraftPlus plugin has a useful feature of being able to backup remote SQL databases on a schedule. This feature might be in the Pro version, but is worth considering. Alternatively, searching online for 'SQL backup scripts' may help. You will have to set up a cron job, too.
wonder if this database backup could (should?) be built into sendy -- specify a remote S3 (or similar) location for the SQL file, set a schedule and then manually set the cron job.
I've moved my sendy install from one AWS instance to another and I can confirm @colcol's statement, all that's needed is the SQL DB, at least from what I recall.
I've also had to restore once, unfortunately, from a AWS kernel blow up that happened a few months ago and used the same method, only needing the SQL DB to get back up and running. At least in regards to previous sendy specific info.
All lists, campaigns, templates, settings and the like are store there and will come over once the original configuration / install is completed.
I use a cron job to dump out the db and rely on my host's backup capabilities to backup that file. I've found great value in the past to go back to a prior day's db not so much because of a crash but because of, "mistakes" I've made.