Backup Confluence on AWS EC2

[kae001]

I'm new to AWS and looking for an automated production backup strategy for Confluence running on an EC2 instance. I know about the standard documented approach to Confluence backups, but I'm interested in leveraging EC2 to make it faster and easier.

1. Any recommendations on how to go about this? I'm just looking for any ideas as a starting point for my research.
2. Can I keep Confluence running while the backup is in progress? (The database- and filesystem-level backup strategies suggest stopping Confluence to be on the safer side)

[Abhi Vaishnav · Accepted solution]

Hey X,

All our Atlassian products are running in AWS as well and this backup strategy has been tried and tested for us. Our confluence server just crapped out about 2 months ago and bringing up the cold-standby instance was a breeze - with minimal data loss.

We have a production server (in AWS-West) along with a cold-standby (in AWS-East) instance.

Our production database has a read-only slave (using AWS's built-in features - in AWS West) that we take MySQL dumps from and restore to our cold-standby's DB.

We also RSYNC our confluence data and server directory to our cold-standby instance.

This is all done once an hour. Of course, if losing an hours worth of data is unacceptable, you can run the cron jobs more frequently...