Backup 2.0: Difference between revisions
From MoodleDocs
Line 10: | Line 10: | ||
* One code base both for manual and scheduled backup | * One code base both for manual and scheduled backup | ||
* Scheduled restore? | * Scheduled restore? | ||
* Fileless export/import | |||
* Export/import over mnet | |||
* OOP. | * OOP. | ||
* Secure (don't handle non-allowed data, user matching on restore, salted passwords..) | * Secure (don't handle non-allowed data, user matching on restore, salted passwords..) | ||
* Safe (some sort of "rollback" on failure - requires to have everything annotated somewhere - backup_ids or so). | * Safe (some sort of "rollback" on failure - requires to have everything annotated somewhere - backup_ids or so). | ||
* file-less backups - if you have separate backups, import/export etc. | * file-less backups - if you have separate backups, import/export etc. |
Revision as of 23:16, 4 November 2008
Drop in ideas
- Support incremental backups & restore.
- Support 1-activity backup.
- Support anonymisation of personal data on backup.
- Separate process and progress.
- XML format doesn't need to be radical different (IMO).
- Support restore of old (1.9 only?) backups.
- Hook in backup & restore to intercept & support other formats (BB, IMS-CC...)
- One code base both for manual and scheduled backup
- Scheduled restore?
- Fileless export/import
- Export/import over mnet
- OOP.
- Secure (don't handle non-allowed data, user matching on restore, salted passwords..)
- Safe (some sort of "rollback" on failure - requires to have everything annotated somewhere - backup_ids or so).
- file-less backups - if you have separate backups, import/export etc.