hidden:Database Online Backup: Difference between revisions
From Lsdf
Jump to navigationJump to search
No edit summary |
(remove everything because it is internal docs) Tag: Blanking |
||
| Line 1: | Line 1: | ||
'''A database online backup can be made during normal HPSS operation''' |
|||
'''Online backup on test core''' |
|||
/hpss_src/scripts/db2_fullbackup.ksh -p /db2_backup -t online -b none >>/db2_backup/db2_backup_fullbackup.out |
|||
'''Online DB2 backup on productive core''' |
|||
/hpss_src/scripts/db2_fullbackup.ksh -p / -t online -b none >>/db2_backup1/db2_fullbackup.out 2>&1 |
|||
'''DB2 backup on active core''' |
|||
On the active core server runs every hour a cron job which takes an online DB2 backup: |
|||
0 */1 * * * if [ `hostname` == "hpsscr" ] ; then /hpss_src/scripts/db2_fullbackup.ksh -p /db2_backup1 -t online -b none >> /db2_backup1/db2_fullbackup.out 2>&1 ; fi |
|||
For a DB2 restore see: |
|||
[[hidden:Database Restore exercised on Test Core|Database Restore exercised on Test Core]] |
|||
DB2 backups are saved on /db2_backup1 |
|||
DB2 backups are kept on disks 7 days |
|||
Every day a TSM backup puts the DB2 backups in TSM |
|||
A deleted DB2 backup from local file system remains 60 more days in TSM => we can go back 67 days with a DB2 restore |
|||
'''Notice''' |
|||
It is possible to archive the DB2 backups in TSM if a longer retention time is needed |
|||
----[[ hidden:HPSS|<small>back to HPPS main page</small>]] |
|||
