Reduce backup time for DB2 10.5 database which is 2.7TB in size
Has this been tried before? Any experiences?
The backup time of the current table space will be reduced, and hopefully the new tablespace backup can run in parallel.
There are 3,345 tables with ‘HISTORY’ keyword in table name (all under schema DATA), though only 41 tables have data currently. They are using about 600GB space.
Suggestion is to create new history tablespaces(DATA, INDEX & LOB) and bufferpool, then use DB2 online table move function move these 41 tables one by one to new tablespaces during a weekend maintenance window.
We can monitor backup time after the change. If the new backup time is still not good enough, we can think about move the huge 1.2TB table DATA.PC_DATA_WORKATTACH to a standalone new tablespace.