October is Backup and Recovery month. It is also the month of goblins, ghouls and scary stories. Kurt Struyf tells us that these two themes often go together. Kurt presents a horror story of what can go terribly wrong when you don't have a good backup and recovery strategy.
How many copies of your databases do you have? I’m talking about both how many test databases with test data as well as full copies of your production data. In many shops, developers are well behaved and get along nicely. They share test databases.
Just this week a few customers asked me the same question. “Should we back up our indexes?” As tradition warrants it, I answered with “it depends”. The choice to back up your indexes or not, should be a part of your overall recovery strategy.
I figured it would be a fun little exercise to ensure IDUG’s db2 express-c database is always backed up on S3 as well as our logs. Below is a basic db2 user exit script for UNIX that handles the log archiving communications with S3. It’s not as clean as I would like because the s3cmd command ...