Rigido
ADSM.ORG Senior Member
Hi Backuppers,
I'm not into DB2, I am far away to be a db admin and dba I know is mostly a SAP person so, maybe, I just need a (real) good DB2 dba or someone already faced this type of configuration that could explain how to configure this.
As I wrote I have a customer that wants daily backups (14 versions), weekly (4), monthly (24) and yearly (9999) for its databases.
I thought that best way to configure backups was:
First big problem is that no one asked customer for a backup window to do offline backups so I tried to do full online on Saturday too BUT as I wrote a script to do backups and to delete old full AND RELATED LOGS something doesn't work as I can't find any LOGS with W/M/Y backups:
DAILY - FULL (SID_D node/servername, 7 versions in this case)
Retrieving FULL DATABASE BACKUP information.
1 Time: 20210301203009 Oldest log: S0002457.LOG DB Partition Number: 0 Sessions: 5
2 Time: 20210226203008 Oldest log: S0002449.LOG DB Partition Number: 0 Sessions: 5
3 Time: 20210225203009 Oldest log: S0002447.LOG DB Partition Number: 0 Sessions: 5
4 Time: 20210224203008 Oldest log: S0002443.LOG DB Partition Number: 0 Sessions: 5
5 Time: 20210223203009 Oldest log: S0002440.LOG DB Partition Number: 0 Sessions: 5
6 Time: 20210222203009 Oldest log: S0002437.LOG DB Partition Number: 0 Sessions: 5
7 Time: 20210219203009 Oldest log: S0002430.LOG DB Partition Number: 0 Sessions: 5
DAILY - LOGS
Retrieving LOG ARCHIVE information.
Log file: S0002430.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-19-05.23.48
Log file: S0002431.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-19-17.53.36
Log file: S0002432.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-19-20.39.27
Log file: S0002433.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-20-06.23.52
Log file: S0002434.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-20-18.53.40
Log file: S0002435.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-20-20.34.03
Log file: S0002436.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-21-05.18.49
Log file: S0002437.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-21-17.48.39
Log file: S0002438.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-22-04.13.39
Log file: S0002439.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-22-14.38.46
Log file: S0002440.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-22-20.38.59
Log file: S0002441.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-23-05.13.49
Log file: S0002442.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-23-17.43.42
Log file: S0002443.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-23-20.38.08
Log file: S0002444.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-24-06.47.34
Log file: S0002445.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-24-18.43.42
Log file: S0002446.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-24-20.39.15
Log file: S0002447.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-25-05.08.52
Log file: S0002448.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-25-15.33.45
Log file: S0002449.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-25-20.36.56
Log file: S0002450.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-26-08.13.20
Log file: S0002451.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-26-18.38.48
Log file: S0002452.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-26-20.38.13
Log file: S0002453.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-27-05.03.50
Log file: S0002454.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-27-17.33.41
Log file: S0002455.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-27-20.33.53
Log file: S0002456.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-28-06.03.53
Log file: S0002457.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-28-18.33.39
Log file: S0002458.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-03-01-02.53.53
Log file: S0002459.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-03-01-15.23.43
Log file: S0002460.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-03-01-20.37.33
Log file: S0002461.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-03-02-05.58.47
WEEKLY FULL (SID_W node/servername)
Retrieving FULL DATABASE BACKUP information.
1 Time: 20210227203004 Oldest log: S0002453.LOG DB Partition Number: 0 Sessions: 5
2 Time: 20210220203004 Oldest log: S0002432.LOG DB Partition Number: 0 Sessions: 5
3 Time: 20210213203004 Oldest log: S0002413.LOG DB Partition Number: 0 Sessions: 5
4 Time: 20210130203003 Oldest log: S0002373.LOG DB Partition Number: 0 Sessions: 5
WEEKLY LOGS
Retrieving LOG ARCHIVE information.
No LOG ARCHIVE images found for SID
So, just few questions:
CIAO!
I'm not into DB2, I am far away to be a db admin and dba I know is mostly a SAP person so, maybe, I just need a (real) good DB2 dba or someone already faced this type of configuration that could explain how to configure this.
As I wrote I have a customer that wants daily backups (14 versions), weekly (4), monthly (24) and yearly (9999) for its databases.
I thought that best way to configure backups was:
- Daily FULL ONLINE on weekdays
- Yearly FULL OFFLINE on Saturday if it is the first Saturday of the year or...
- Monthly FULL OFFLINE on Saturday if it is the first Saturday of the month or...
- Weekly FULL OFFLINE on Saturday.
First big problem is that no one asked customer for a backup window to do offline backups so I tried to do full online on Saturday too BUT as I wrote a script to do backups and to delete old full AND RELATED LOGS something doesn't work as I can't find any LOGS with W/M/Y backups:
DAILY - FULL (SID_D node/servername, 7 versions in this case)
Retrieving FULL DATABASE BACKUP information.
1 Time: 20210301203009 Oldest log: S0002457.LOG DB Partition Number: 0 Sessions: 5
2 Time: 20210226203008 Oldest log: S0002449.LOG DB Partition Number: 0 Sessions: 5
3 Time: 20210225203009 Oldest log: S0002447.LOG DB Partition Number: 0 Sessions: 5
4 Time: 20210224203008 Oldest log: S0002443.LOG DB Partition Number: 0 Sessions: 5
5 Time: 20210223203009 Oldest log: S0002440.LOG DB Partition Number: 0 Sessions: 5
6 Time: 20210222203009 Oldest log: S0002437.LOG DB Partition Number: 0 Sessions: 5
7 Time: 20210219203009 Oldest log: S0002430.LOG DB Partition Number: 0 Sessions: 5
DAILY - LOGS
Retrieving LOG ARCHIVE information.
Log file: S0002430.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-19-05.23.48
Log file: S0002431.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-19-17.53.36
Log file: S0002432.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-19-20.39.27
Log file: S0002433.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-20-06.23.52
Log file: S0002434.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-20-18.53.40
Log file: S0002435.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-20-20.34.03
Log file: S0002436.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-21-05.18.49
Log file: S0002437.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-21-17.48.39
Log file: S0002438.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-22-04.13.39
Log file: S0002439.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-22-14.38.46
Log file: S0002440.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-22-20.38.59
Log file: S0002441.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-23-05.13.49
Log file: S0002442.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-23-17.43.42
Log file: S0002443.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-23-20.38.08
Log file: S0002444.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-24-06.47.34
Log file: S0002445.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-24-18.43.42
Log file: S0002446.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-24-20.39.15
Log file: S0002447.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-25-05.08.52
Log file: S0002448.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-25-15.33.45
Log file: S0002449.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-25-20.36.56
Log file: S0002450.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-26-08.13.20
Log file: S0002451.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-26-18.38.48
Log file: S0002452.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-26-20.38.13
Log file: S0002453.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-27-05.03.50
Log file: S0002454.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-27-17.33.41
Log file: S0002455.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-27-20.33.53
Log file: S0002456.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-28-06.03.53
Log file: S0002457.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-02-28-18.33.39
Log file: S0002458.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-03-01-02.53.53
Log file: S0002459.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-03-01-15.23.43
Log file: S0002460.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-03-01-20.37.33
Log file: S0002461.LOG, Chain Num: 0, DB Partition Number: 0, Taken at: 2021-03-02-05.58.47
WEEKLY FULL (SID_W node/servername)
Retrieving FULL DATABASE BACKUP information.
1 Time: 20210227203004 Oldest log: S0002453.LOG DB Partition Number: 0 Sessions: 5
2 Time: 20210220203004 Oldest log: S0002432.LOG DB Partition Number: 0 Sessions: 5
3 Time: 20210213203004 Oldest log: S0002413.LOG DB Partition Number: 0 Sessions: 5
4 Time: 20210130203003 Oldest log: S0002373.LOG DB Partition Number: 0 Sessions: 5
WEEKLY LOGS
Retrieving LOG ARCHIVE information.
No LOG ARCHIVE images found for SID
So, just few questions:
- Why logs are not stored during "not daily backups" under "not daily node" backup?
Backup command is like "db2 -x backup db SID online use tsm open 4 sessions options "-se=SID_W" - IBM DB2 BACKUP command references says that " INCLUDE LOGS is always the default option for any online backup operation" should I try to force it?
- Daily LOG cleanup delete all logs older than the latest "Oldest" needed log (S0002430.LOG in this case) but it shouldn't delete it if they're stored under a different node name.
- Can I restore weekly/monthly/yearly ONLINE images WITHOUT "Oldest log"?
CIAO!