Content backups
How your content is backed up and recoverable
At Pugpig, we ensure that everything is regularly backed up using AWS Backup. This includes our internal systems, as well as customer data for Express, Pro and Site customers. Customer data can be split into two categories:
1. Editorial Content - this is stored in a database on Amazon Relational Database Storage (RDS)
2. Edition Assets - these are stored on Amazon Elastic File Storage (EFS)
Express Customers:
Express customers are hosted on shared, multi-tenanted infrastructure. This is backed up daily, and we retain 30 days of backups.
As the infrastructure is shared, it takes longer to perform a restore as we need to ensure only one tenant is restored - it can take a couple of days to perform a restore.
Pro and Site Customers:
Each Pro and Site Customer has their own dedicated instance (either Amazon EC2 or Amazon Fargate). However, these servers are ephemeral. All the data is stored on either RDS, EFS or EBS, and all the code is deployed from repositories.
We back up RDS, EFS and EBS daily, and we retain 30 days of backups.
In an emergency, we can restore a certain point in time within one working day.
Off-platform backups
We currently do not provide a way to back up to other external services. However, we can provide exports of the file assets (as a ZIP file) and editorial assets (as a WordPress Database Export) on request.