Make WordPress Core

Opened 19 years ago

Closed 19 years ago

#3459 closed enhancement (wontfix)

Data Redundancy for WordPress

Reported by: robertaccettura's profile robertaccettura Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Administration Keywords:
Focuses: Cc:

Description

We all suck, and we all make mistakes. One of the big advantages as hosted service like wordpress.com has is infrastructure. Thanks to their millions of dollars they have worldclass datacenters that make Google jealous. Many/most wordpress users host on a simple linux box, with little/no easy backup. Or their provider will only restore if the data loss was the providers fault (otherwise it's a big fee).

This ticket is to propose the idea of adding support for WordPress to backup to Amazon S3 via the backup plugin. Implementation would look like this:

  • user enters their AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY just like they enter their Akismet API key.
  • backup just like normal, but instead of downloading or saving to a directory, it goes to Amazon S3.
  • Could extend to cover the upload directory and wp-content in general (which if your upload directory is in there, would mean pretty much everything that matters).

So for < $5 you can keep complete backups of your blog, including all settings, themes, uploads, comments, posts. Fully automated er auttomated, er... whatever.

Since most servers have much better bandwidth than users have, backups and restores would be lightning fast. Could even save multiple backups so you have snapshots.

You know you like this one.

Change History (1)

#1 @Viper007Bond
19 years ago

  • Keywords backup removed
  • Milestone 2.2 deleted
  • Resolution set to wontfix
  • Status changed from new to closed

The backup plugin has been dropped from WordPress as it was somewhat insecure. It has been replaced by the export feature which will export your entire install to a custom XML file.

As for this Amazon S3 thing, this is plugin territory, not core stuff, so I'm closing this ticket.

Not saying it's a bad idea, just saying it's not something that should go in the core, especially since we already have a backup feature and this Amazon thing costs money apparently. ;)

Note: See TracTickets for help on using tickets.