|
Size: 1408
Comment:
|
Size: 1494
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) 2.walBackup = 75% complete, completion expected tomorrow (Thurs 9/10/2009) |
1. PitrBackup = 99% complete (currently working on a fix to the routine that updates/inserts the meta data) |
| Line 13: | Line 12: |
| 3.Implement changes based on feedback if needed | 2. walBackup = 75% complete, completion expected tomorrow (Thurs 9/10/2009) |
| Line 15: | Line 14: |
| 4.Unit testing (first round for pitrBackup complete) | 3. Implement changes based on feedback if needed |
| Line 17: | Line 16: |
| 5.Install 'Package” as a directory structure that will contain all future 'tools' | 4. Unit testing (first round for pitrBackup complete) 5. Install 'Package” as a directory structure that will contain all future 'tools' |
| Line 21: | Line 22: |
| 6.Setup at least 2 cron jobs | 6. Setup at least 2 cron jobs |
| Line 25: | Line 26: |
| * not yet implemented, I'd like to wait for the hmidb0 setup to be in place |
Kevins's archive
Implementation Status
Updated Wed 09-09-2009
Backup / Recovery
1. PitrBackup = 99% complete (currently working on a fix to the routine that updates/inserts the meta data)
2. walBackup = 75% complete, completion expected tomorrow (Thurs 9/10/2009)
3. Implement changes based on feedback if needed
4. Unit testing (first round for pitrBackup complete)
5. Install 'Package” as a directory structure that will contain all future 'tools' /bin, /etc, /tmp, /log, ... Installed on hmidb
6. Setup at least 2 cron jobs 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
- not yet implemented, I'd like to wait for the hmidb0 setup to be in place
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
Database Access and Security
* Starting this step tomorrow (09-10-2009)