wiki:SCS_BACKUP_R4
Last modified 16 years ago Last modified on 07/22/09 09:27:41

Error: Macro BackLinksMenu(None) failed
compressed data is corrupt

Error: Macro TicketQuery(summary=SCS_BACKUP_R4, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed
current transaction is aborted, commands ignored until end of transaction block

Analysis

Overview

As the community server backup is a regular task, it's requirements are not very different from previous revisions' requirements. The regular backup of the project creates two backup CDs that can restore fully the project in case of data loss.

Task requirements

Monthly backups

  • Test if the previous backup contains all needed information for restoring
    • Trac - wiki pages, settings, user accounts.
    • Svn - data, settings, user accounts.
    • Apache configurations
    • Postgres databases.
    • Build server configurations (Hudson)
    • Testlink setup
  • Modify the script if needed
  • Execute the scripts
  • Write the image on TWO dvds
  • Make sure the copies are kept in different locations.

Daily backups

  • According to previous revision of this task, a script backing up the database is done. In implementation section describe where is it, when is executed. Describe how to use this script before modifying database with direct queries.

Task result

Two backup DVDs that are kept in different locations. Daily database backups, location should be listed here. If database is modified, backup before modifications.

Implementation idea

Use previous revisions of this tasks for locations of the scripts.

SCS_BACKUP_R3
Previous revisions of this tasks cannot be used because of the new setup.

How to demo

Explain what is done.

Design

  • Add nexus to the back up script adding the following:

## Trac, testlink and svn
cp -R /home/scs/svn/ /home/scs/backup/all/$dirname
cp -R /home/scs/trac/ /home/scs/backup/all/$dirname
cp -R /home/scs/testlink/ /home/scs/backup/all/$dirname
cp -R /home/scs/nexus/ /home/scs/backup/all/$dirname

  • Verified the contents of the previous back up task.
  • Run the scripts twice and store the 2 DVDs at separate places.

Implementation

  • Previous back up contains all information needed for restore
  • Nexus is added to the back up script according to the design phase
  • The scripts were executed
  • As a result two disks were burned
  • They are kept in different locations
    • one at the office
    • one is kept in the Infrastructure Manager's home aka Pac
  • The script is executed every Sunday at 3 a.m. ЕЕТ. However we burn the DVDs ones a month.
  • The following steps must be used when restoring the database using the back up
    • gunzip /root/backup/postgres/$date.psql.gz | psql -U scs

Testing

(Place the testing results here.)

Comments

(Write comments for this or later revisions here.)