I would vote for it too. But as I started commenting here
the whole thing could later be put into a major context:
Moodle admins (and teachers) need facilities to revert back in case they delete a little portion out of their courses, the whole courses, categories or a whole tree of nested categories, etc. to avoid restoring and reverting back the whole system. In old Moodle 1.9 days course-backups could help recover atomic data (whole courses or parts of it on a testserver or on the production server where you would have restored the course backup-file from tape). But as Moodle 2 file system is much more complex and data is becoming bigger and bigger, course-backup-files might not be the good solution in the future. We need other facilities, complementary procedures. Not to be confused with the overall system backup, the one you need in case of a whole system loss.
In the best case and long term development, sort of do-and-undo history could be integrated in the courses and on the whole Moodle system. The do-and-undo history should be available to all teachers/managers/siteAdmins of a course. The do-and-undo history of the whole Moodle system should be available only to site-Admins.
In a compromise and short term development, every "destructive" action inside a course, i.e. changing any bit in it should trigger a course-backup on the fly. No do-and-undo history for the moment, but sort of snapshots BEFORE teachers modify anything. This would be session-based, so as not to trigger more than one backup of the course even if a teacher modifies/edits several sections/activities/resources during one session. If teachers log out and come back to the course for modifications, another backup is triggered.
In a long term solution, nothing should be deleted from the database, only marked as deleted, so as to be able to implement a do-and-undo history. With that the need to create big course-file-backups should disappear, except to export and import Moodle course files on other systems. Maybe instead of a zip-file a tar-file or any other solution might be better, including a very rudimentary directory-tree containing all the uploaded files of a course along with Moodle's xml-file describing the course contents and links to the files. The only difference being that nothing gets zipped as zipping big multimedia-files does not make sense anyway.
The siteAdmin would then set up a retention-time for such "deleted" items as I can do it on my mail-server. "deleted" items could be transferred to a trash-database and files belonging to those items could go into the trashDir, from where everything could be "revived", moved into the production database again, without disrupting anything. And, on the other side, could be safely hard-deleted after the retention period.
Again, this is meant to give facilities on high load servers with lots of courses, data and teachers in which case the server admin has no chance of rewinding back the whole system if a teacher loses a bit in his course.