DB2 online backups via TSM.

I believe we have a situation like this on three of our production servers.

IBM - CopyContinue not working with DB2 backups using Simultaneous write.

For now, we are going to increase server space and backup to disk on the server.

However, longer term we need to figure out how to fix this and I am sorry to say my DB2 DBA/TSM inexperience is such that I am struggling to interpret exactly what this article is telling me to do to resolve this problem.

I think we need to configure something on the TSM server to not use the simultaneuos write when backing up the database.

If anyone could help shed some light on this, I would be very grateful!

Thank you.

I am looking through the TSM API trace files, comparing a working online backup with one of the ones that has failed.

Keep rooting for me guys!

After a discussion with my manager we have agreed the TSM guys can look into increasing the COPYSTGPOOL size and see if that works.