A little while ago, I wrote to the PostgreSQL general mailing list that I’d been approached by Packt Publishing to contribute a quick manual on doing PostgreSQL backups: Instant PostgreSQL Backup and Restore How-to. They’re the same guys who published Greg Smith’s PostgreSQL 9.0 High Performance book which everyone seems to swear by.

The goal of the backup book was to distill the PostgreSQL documentation, tools, and Wiki down to a collection of short step-by-step guides much like the O’Reilly nutshell series. A lot of the backup recipes we DBAs trade back and forth as a matter of course may not be so obvious, and I threw a couple tricks in for advanced users, to boot.

Well, here’s your chance to spring a free copy! The marketing folks have given the go-ahead to hold a giveaway, and have set aside four copies for lucky winners. A longer description of the How-to is on their site.

All they want to know is what you, as a prospective reader, find most interesting or potentially useful about the book. My comment section will be open until May 8th for replies along these lines. If you are selected, Packt will email you with information on how to get your free digital copy. If your comment catches our attention, you’re one step closer. If you want a print copy, they’re available from Amazon separately.

So remember:

  • Free book
  • What interests you about it?
  • Submit a comment
  • You’re entered

I look forward to forcing Packt to do some community service by handing out free copies of the book, and you should too. πŸ™‚

Free PostgreSQL Backup Book? Yes Please!
Tagged on:                         

16 thoughts on “Free PostgreSQL Backup Book? Yes Please!

  • You know, this ebook is only $5. I think its better off to just buy a copy and support it rather than trying to get that for free. For anyone it would help, it would be $5 well spent. And even to take a chance, its inexpensive anyway. I bought one as soon as I heard about it.

    1. Hey, I appreciate it. I didn’t really do it for the money, if you’ll believe that. Packt is pretty well known, and it’s a great way to distribute necessary material. If they’re willing to market and get the word out, I can host a giveaway or two on their dime. πŸ™‚

      1. When I said support the book by buying it, I wasn’t just thinking about the author, but also the publisher; I assume Packtd would have spent a reasonable amount of resources in editing and formatting it, and that Shaun didn’t do all that, even if a majority of the overall work was the author.

  • Backups are useless unless they get made. I’ve seen too many sites with complex manual backup strategies wherein people rarely actually do the backups because it’s too hard, and they don’t automate it because the methodology is too complex for their programming abilities. I’d be very interested in seeing strategies for completely automating complex backup plans.

    (This may seem like low-hanging fruit, but I really do believe this is a real need.)

    1. True. Unfortunately though I do mention a couple spots where the commands could be scripted and automated, and even recommend the reader do so, it’s not explicitly described. It’s kinda hard to boil that down into a step-by-step without providing the actual backup scripts. Packt only wanted about 30-ish pages, which to me seems more like a long-ish chapter of a larger book. Automating things in UNIX is kinda beyond the scope of this kind of book.

      At the same time, even the longest and most complex recipes I go over are easily automated. I know because I’ve used these exact techniques since at least 2005. Command-line tools are good for that, at least. πŸ™‚

      The real question is: what to do with the backups after they’re created? Tape magazine? Deduplicated SAN? Offsite? Disaster recovery data center? Pick at least two. We use all four. I strongly urged readers to give it some thought, but hopefully they already have.

    2. Right now the only tool that’s directly addressing the need for plug and play disaster recovery tools is barman. It’s free software. I’m glad that Shaun’s book has documented a lot more of the hard work that goes into doing this yourself. Given how complicated it is though, a lot of people would be way better off to just figure out how to install barman and use it instead. It’s not perfect, but it’s better than you’ll do yourself until you’ve put a lot of work into it.

      1. This is going to sound retarded, but I’ve never heard of barman before. I’ve been “rolling my own” so long, I haven’t even looked for alternatives. I’ll have to check it out.

        Thanks, Greg!

  • Not to say that the official Postgres documentation is not good enough for a typical Postgres DBA to implement the backup and recovery mechanisms. Also, it would be unfair to say there is not much of a support available online, especially when several experts on the IRC (RhodiumToad, Davidfetter, Depesz, Peerce, Andrew and so many more) are almost available 24/7 and offer super elegant custom solutions for free to scores of seekers on several Postgres implementation issues not just limited to backup/recovery. All this truly helps but then a newcomer to Postgres is bogged down by the issue of “a thousand ways to skin a cat” and it is difficult to say which one is best suited to their situation. This is especially true when it comes to physical backups. The “Postgres Backup Book” can help iron out a lot of that confusion by elaborating and throwing in a lot of detail like actual scripts and commands. The book, I believe, must narrow down on a select few standard techniques of skinning the cat and should do so by providing as much detail as possible. It would be nice to aggregate the most common problems encountered during backup/recovery and solutions to fix the same. The book should also support these techniques per supported major version on Postgres because the newer versions have advanced mechanisms to the same things when compared to older versions. I look forward to enjoying more such books in future and hopefully a lot thicker.

    1. Yeah. They specifically asked for about 30-ish pages. Maybe someone else will write a real backup manual, or they’ll have me do a longer one some time later.

  • I’ll be honest, I’m still learning the ropes so any concise information is appreciated. I’ve deployed dozens of PostgreSQL servers these past few months but I’m afraid our backup policy isn’t up to par. Would love to learn straight from the pros!

  • I bought this book two weeks ago.

    When I got the book, I thought it was a total rip-off, I paid $20+ (price+shipping) for a book with effective pages of 34?

    But after I went through the book. I really liked the book. I consider the dollars very well spent, because those step by step instructions are clear, and easy to follow. And the commands are mostly correct.

    To improve it:

    It would be better if you put a backup and restore together. For example, page 14 talk about how to do a simple backup, but, the restore is explained on page 27.

    Also, when you explain advanced topics, I could use more explanations.

    I would put future emphsis in advanced topics, things like pg_dump can be found everywhere.

    I like this focused-topics approach, maybe a book on replication exclusively, more than 2 nodes and how to failover etc.

  • This seems like a nice addition to my collection πŸ™‚ More seriously, summing up in a few pages how to set up streaming replication, how to do pitr… These are things any DBA should have on his desk to help restoring a database after a crash at 2AM.

Comments are closed.