|
Size: 1502
Comment:
|
Size: 1977
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 10: | Line 10: |
| 1. pitrBackup = 99% complete (currently working on a fix to the routine that updates/inserts the meta data) | 1. pitrBackup = 100% complete (We may still find bugs as we engage in further testing) |
| Line 12: | Line 12: |
| 2. walBackup = 75% complete, completion expected tomorrow (Thurs 9/10/2009) | 2. walBackup = 100% complete (We may still find bugs as we engage in further testing) |
| Line 16: | Line 16: |
| 4. Unit testing (first round for pitrBackup complete) | 4. Unit testing - 100% (Basic Unit tests) |
| Line 20: | Line 20: |
| Installed on hmidb | Installed on hmidb (after the move to hmidb0 we'll setup the final packages) |
| Line 22: | Line 22: |
| 6. Setup at least 2 cron jobs | 6. Setup backup jobs (pending move to hmidb0) |
| Line 26: | Line 26: |
| * not yet implemented, I'd like to wait for the hmidb0 setup to be in place | |
| Line 29: | Line 28: |
| Line 39: | Line 39: |
| * walBackup script 100% complete * walBackup Unit Testing - 100% complete (Basic unit tests) |
|
| Line 40: | Line 43: |
| == Database Access and Security == | * Still To Do: Revise / make more clear & easy to follow the recovery plan |
| Line 42: | Line 45: |
| * Starting this step tomorrow (09-10-2009) | == Web db Plan == * Strategy documented - initial pass (100%) == SLONY Plan == * SLONY v2 must be used if we want to use PostgreSQL 8.4 * SLONY-1 2.03 (release Candidate) recommended due to a few key bugs in 2.01 and 2.02 * Next Steps: * Define SLONY Architecture * Define Log Shipping process * Build SLONY scripts/tools |
| Line 44: | Line 65: |
| * Implement & Test |
Kevins's archive
Implementation Status
Updated Wed 09-09-2009
Backup / Recovery
1. pitrBackup = 100% complete (We may still find bugs as we engage in further testing)
2. walBackup = 100% complete (We may still find bugs as we engage in further testing)
3. Implement changes based on feedback if needed
4. Unit testing - 100% (Basic Unit tests)
5. Install 'Package” as a directory structure that will contain all future 'tools' /bin, /etc, /tmp, /log, ... Installed on hmidb (after the move to hmidb0 we'll setup the final packages)
6. Setup backup jobs (pending move to hmidb0) Cron entry to run the base file system backup (I suggest once/quarter) Cron entry to archive the WAL segments (monthly) Optional additional base file system backups to alternate locations
The toolset will be run from the warm standby server
Warm Standby
- Documented strategy
- Strategy fully dependant on the Backup / Recovery strategy and defined manual steps
- We'll need to address the re-setup of SLONY after a fAIL over as part of the upcoming 'Data Replication' strategy
- I successfully tested the backup of a running warm standby server and then recovering from the warm standby base backup and the subsequent archived WAL files from the master
- walBackup script 100% complete
- walBackup Unit Testing - 100% complete (Basic unit tests)
Still To Do: Revise / make more clear & easy to follow the recovery plan
Web db Plan
- Strategy documented - initial pass (100%)
SLONY Plan
- SLONY v2 must be used if we want to use PostgreSQL 8.4
- SLONY-1 2.03 (release Candidate) recommended due to a few key bugs in 2.01 and 2.02
- Next Steps:
- Define SLONY Architecture
- Define Log Shipping process
- Build SLONY scripts/tools
Implement & Test