Analysis

Overview

This task includes backing-up the project data.

Task requirements

• Analyze the results from the most recent backup
  • See if the created CD contains all needed information.
  • Decide if the server can be actually restored using this CD.
• Review files that should be backed up.
  • Review files that are currently backed up.
  • Consider if new files should be added to the back up.
  • Consider if files should be removed from the back up.
• Review the automatic backup script dan-server:/backup/backup.sh. Modify it to satisfy new requirements from the previous points(if needed).
• Choose a period for the backup - once in a sprint or more frequent.

Task result

Backup of the Community server on a disc. Revisited backup script dan-server:/backup/backup.sh.

Implementation idea

Related

SCS_BACKUP_R0
dan-server:/backup/backup.sh

How to demo

Present dan-server:/backup/backup.sh and describe modified parts (if any). Present implementation section of this document, it should contain description of what is done.

Design

Review the CD - where it is stored, can the server be restored from it? The current script contains all needed information for trac to run. Decided to only execute the backup script because a restructuring of the trac will be done these days. A script should be created when the new structure of dan-server is applied.

Implementation

The script meets requirements for current structure of the server. A backup disc is done (08-10-31) in 12:00h GMT.

Testing

Log

Analyzing: Deyan (done : 35 min)
Review: 3.5 by todor. The analysis is good enough and gives all needed information what should be done in this revision. But didn't mention when the backup should be done. The LOG wasn't included, be more careful.
Design: deyan (done:10m)
Review: 3 by Pav. Added to the design that the current CD must be reviewed.
Implementation: Peko, Deyan 10m (done)
Testing:
Comments: