1 to 5 of 5
Sort by

Library Entry
SQL: Find Tablespaces without Recent Backups

Using left-outer join, identify any tablespaces or partitions (I don't include code for copyable indexes in this version, sorry) which have not been recently (31 days, in the sample code) backed up, or recently loaded with REPLACE. (Either event will remove a tablespace from this result set.) ...

Blog Entry
Understanding the DB2 LUW Backup Performance Statistics

Understanding DB2’s Backup and Restore Statistics In an effort to help customers determine where performance bottlenecks exist in DB2 backup and restore operations, DB2 has added an extremely useful entry into the db2diag.log file. It was first introduced in v 9.7 under registry variable...

Dale McInnis's profile image

Blog Entry
Do You Really Need That Extra Copy of the Database?

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. If they have to have their own data to play...

Joe Geller's profile image

Library Entry
[F14] Reduce your Application Backup Window with a Snap

In this session we will share our experience on a implementation of a new Application backup Strategy which survives through the years independent of data growth and without increasing the Application Backup window. Objective Describe the different solutions tested The different aspects...


Ruth Soares's profile image

Blog Entry
Show me Your Recovery SLA and I will Tell You Your Backup Strategy

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. The backup strategy of your table spaces and...

Kurt Struyf's profile image