Differences between revisions 12 and 24 (spanning 12 versions)
⇤ ← Revision 12 as of 2009-09-16 05:03:52 →
Size: 1896
Editor: c-67-176-12-8
Comment:
← Revision 24 as of 2013-05-01 04:35:27 → ⇥
Size: 1050
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
[[Anchor(mostrecent)]] <<Anchor(mostrecent)>>
Line 5: Line 5:
= Implementation Status =
== Updated Wed 09-09-2009 ==
 = 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
 * NFS mounts complete (setup by Keh-Cheng)
 * ETA: completion should be early/mid this afternoon (12-1-2009)
Line 9: Line 22:

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)



== 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		  * 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
  • NFS mounts complete (setup by Keh-Cheng)
  • ETA: completion should be early/mid this afternoon (12-1-2009)

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

JsocWiki: KevinsProgress (last edited 2013-05-01 04:35:27 by localhost)