I think it would be great if, say there was an option to NOT backup the DB is there hadn't been any changes since the last backup.
Say I have weekly backups emailed to me, but there hasn't been a post or comment on my blog in a week, it shouldn't back the whole thing up again, right?
It's an interesting idea, but I think it would be difficult to implement. That's because practically every database for a public blog is going to change somewhat all the time: if nothing else, spam or moderated comments will accrue. The trick would be determining what changing things are important to users, and I'm afraid that the potential harms---the wrong decisions about what's important, the processing power used to figure out if the database has changed, the increased likelihood that someone will lose the prior backup, among others---would outweigh any benefits.
Hi,
I think it would be great if, say there was an option to NOT backup the DB is there hadn't been any changes since the last backup.
Say I have weekly backups emailed to me, but there hasn't been a post or comment on my blog in a week, it shouldn't back the whole thing up again, right?
Anyway, just a thought. Thanks!
-joe
It's an interesting idea, but I think it would be difficult to implement. That's because practically every database for a public blog is going to change somewhat all the time: if nothing else, spam or moderated comments will accrue. The trick would be determining what changing things are important to users, and I'm afraid that the potential harms---the wrong decisions about what's important, the processing power used to figure out if the database has changed, the increased likelihood that someone will lose the prior backup, among others---would outweigh any benefits.
RSS feed for this topic
Reply
You must log in to post.