| | 1 | [[BackLinksMenu]] |
| | 2 | |
| | 3 | = Analysis = |
| | 4 | == Overview == |
| | 5 | This task includes backing-up the project data. |
| | 6 | == Task requirements == |
| | 7 | * Analyze the results from the most recent backup |
| | 8 | * See if the created CD contains all needed information. |
| | 9 | * Decide if the server can be actually restored using this CD. |
| | 10 | * Review files that should be backed up. |
| | 11 | * Review files that are currently backed up. |
| | 12 | * Consider if new files should be added to the back up. |
| | 13 | * Consider if files should be removed from the back up. |
| | 14 | * Review the automatic backup script [htdocs:backup.sh dan-server:/backup/backup.sh]. Modify it to satisfy new requirements from the previous points(if needed). |
| | 15 | * Choose a period for the backup - once in a sprint or more frequent. |
| | 16 | == Task result == |
| | 17 | Backup of the Community server on a disc. Revisited backup script [htdocs:backup.sh dan-server:/backup/backup.sh]. |
| | 18 | == Implementation idea == |
| | 19 | == Related == |
| | 20 | [wiki:SCS_BACKUP_R0] |
| | 21 | == How to demo == |
| | 22 | Present [htdocs:backup.sh dan-server:/backup/backup.sh] and describe modified parts (if any). Present implementation section of this document, it should contain what is done |
| | 23 | = Design = |
| | 24 | |
| | 25 | = Implementation = |
| | 26 | ^(Implementation results should be described and linked here (from the wiki or the repository)^ |
| | 27 | |
| | 28 | = Testing = |
| | 29 | |
| | 30 | = Log = |
| | 31 | ^(Link the log of the task here)^ |
