MQSeries.net :: View topic - DB2 backup before CSQ45ATB on MQ v7.0.1 migration

dogbert64

A question about what some of the other MQ admins are doing about DB2 backups of their QSG datasets before running CSQ45ATB.

I have already upgraded one Queue Manager using QSG on a lightly used test Plex LPAR from MQ v6.0 to 7.0.1. But in that case, I was able to bring down EVERYTHING that used MQ and the DBA was able to take a full, point-in-time backup of schema/data. This was done in conjunction with full MQ log/pageset backups, while the system was entirely quiet from an application standpoint. So if CSQ45ATB somehow mangled the database/tables, we could go back to it with no problem. (definitely went old school backup on that one)

But when it comes to our Production or Development Plexs, I won't be able to do that. We're supposed to keep at least one Plex up and running, which means that DB2 data is changing.

Specifically, I'm interested in the DB2 angle. What do you do to ensure that you get a point-in-time backup of the QSG DB2 database? Or can you if everything is up and running? Or do you even care? Since we have moved to Parallel Sysplex, management has less (almost none) of a tolerance for full application outages for the sake of point-in-time recovery. And I understand their position.

Just trying to see how the other admins handle the DB2 backup, or it is even an issue.