DB2 backup are writing to wrong policy
DB2 backup are going to the wrong policy, for example if backup was initiated from PRD_PORDB2_DB2_D_Full policy. Data will be recieved by PRD_PORDB2_DB2_M_Full.
My goal is to keep different retentions for DB2 backups. And since data is going to the default-applicaiton-backup schedule, multiple policies are requered.
db2.conf
DATABASE JCRDB
OBJECTTYPE DATABASE
POLICY PRD_PORDB2_DB2_M_Full
SCHEDULE Default-Application-Backup
ENDOPER
DATABASE JCRDB
OBJECTTYPE DATABASE
POLICY PRD_PORDB2_DB2_W_Full
SCHEDULE Default-Application-Backup
ENDOPER
DATABASE JCRDB
OBJECTTYPE DATABASE
POLICY PRD_PORDB2_DB2_D_Full
SCHEDULE Default-Application-Backup
ENDOPER
DATABASE JCRDB
OBJECTTYPE ARCHIVE
POLICY PRD_PORDB2_DB2_Arch
SCHEDULE Default-Application-Backup
ENDOPER
DATABASE JCRDB
OBJECTTYPE DATABASE
POLICY PRD_PORDB2_DB2_M_Full
SCHEDULE Default-Application-Backup
ENDOPER
DATABASE JCRDB
OBJECTTYPE DATABASE
POLICY PRD_PORDB2_DB2_W_Full
SCHEDULE Default-Application-Backup
ENDOPER
DATABASE JCRDB
OBJECTTYPE DATABASE
POLICY PRD_PORDB2_DB2_D_Full
SCHEDULE Default-Application-Backup
ENDOPER
DATABASE JCRDB
OBJECTTYPE ARCHIVE
POLICY PRD_PORDB2_DB2_Arch
SCHEDULE Default-Application-Backup
ENDOPER
I believe you can have only one OBJECTTYPE DATABASE and one OBJECTTYPE ARCHIVE per database per db2.conf. So you will capture the very first DATABASE / OBJECTTYPE DATABASE pair and backup to the schedule under that pair.
Since you are running user scripts and doing an Default-Application-Backup schedule type then you could as a part of your cron job copy a db2.conf first to that has the correct DB / Schedule pair in it.
