Backups can be one of the most critical aspects of administering any database, and PostgreSQL is no exception. While the PostgreSQL database is very versatile and resilient, problems can happen. A power failure could occur at worst moment corrupting the database or the hard-drive could fail. You could also have problems with users, authorized or unauthorized, changing or destroying data, we hope by accident, but sometimes malicious people can do bad things when presented the opportunity.
The list really could be limitless, but if you're following ERP Best Practices, then you know the best way to protect yourself is to make regular backups of your database. The depth of the situation you want to safeguard against can dictate your requirements for how often, when, where you store your backups. The first thing is make regular backups. The second is to store them in a safe place. If you are storing your backups on the same server you run your database on it's possible you could lose your database and your backups if the drive fails. Read more »
Have you ever considered compiling xTuple/PostBooks on Windows? Perhaps you tried to set up an environment for our last Bug Derby and ran into problems. Sometimes getting things to work correctly requires arcane rituals or absurdly ridiculous actions. Please don't ask me why I have a jellybean stuck to my forehead. It doesn't have to be that way, and I'm here to share my latest experiences with you. When you're done following the instructions below, you'll have a development environment you can use for our up-coming Bug Derby.
