Differences between revisions 2 and 9 (spanning 7 versions)
Revision 2 as of 2009-09-05 01:52:44
Size: 89
Editor: arta-mbp
Comment:
Revision 9 as of 2009-09-10 06:12:36
Size: 1494
Editor: c-67-176-12-8
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:

= 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)
 

Kevins's archive

Anchor(mostrecent)

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)

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