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.
Quote:
|
If this is for a TSM Backup/Archive client and COPYCONTINUE=YES, the backup operation would be retried without the simultaneous write.
|
If anyone could help shed some light on this, I would be very grateful!
Thank you.