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)

-  ⇤ ← Revision 4 as of 2009-09-09 01:49:28 → 
  Size: 686
  Editor: c-67-176-12-8
  Comment:
+   ← Revision 11 as of 2009-09-10 06:13:49 → ⇥
  Size: 1502
  Editor: c-67-176-12-8
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 4:
- * Status (Tues 09-0802009)
  * Currently I'm testing the use of the warm standby server as a PITR backup/recovery source (est completion = today)
  * Next step is to finish the WAL backup scripts in a way that allows us to recover in a controlled manner - plus the creation of the backup meta data (est completion = Late tomorrrow)
  * Next I'll coordinate a full xfs backup/restore test on hmidb0/1 with xfsdump as the defined backup command (est completion = ? probably Thurs) 
  * After this I'll start on the "Kevin evaluates our plan to disseminate database data to the public..." task
+= 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)