|
Size: 1407
Comment:
|
Size: 1054
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| * Status (Wed 09-09-02009) | |
| Line 6: | Line 5: |
| = Implementation Status = |
= Current Tasklist = == Updated Tues 12-01-2009 == == SLONY == === subscribe_series() === * 80% complete * modifications to get_slony_logs and the slony1 dump scripts are in progress (for integration with subscribe_series) * subscribe series (end2end) should be ready for installation/testing by end of day Wed (12-2-2009) === publish_series() === * Design is complete * on hold until subscribe_series is complete * ETA: Monday 12-14 == WARM Standby == === dcs servers === * initial design / setup in progress * waiting on response to NFS question * Effort to complete is ~2hours once I get a response to the NFS question |
| Line 9: | Line 22: |
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 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) |
* New design doc in place * Code construction on hold until slony is complete == Additional Tasks == * single-command warm standby failover * single-command warm standby re-set * add/drop things from SLONY script * graphing tool to show avg slony load per object * Monitoring |
Kevins's archive
Current Tasklist
Updated Tues 12-01-2009
SLONY
subscribe_series()
- 80% complete
- modifications to get_slony_logs and the slony1 dump scripts are in progress (for integration with subscribe_series)
- subscribe series (end2end) should be ready for installation/testing by end of day Wed (12-2-2009)
publish_series()
- Design is complete
- on hold until subscribe_series is complete
- ETA: Monday 12-14
WARM Standby
dcs servers
- initial design / setup in progress
- waiting on response to NFS question
- Effort to complete is ~2hours once I get a response to the NFS question
Backup / Recovery
- New design doc in place
- Code construction on hold until slony is complete
Additional Tasks
- single-command warm standby failover
- single-command warm standby re-set
- add/drop things from SLONY script
- graphing tool to show avg slony load per object
- Monitoring