[Bobs-devel] feature enhancements and some design issues

[Rene R. <re...@gr...>]

Project based backup proposal.

Definition of a project:

- each root directory in a share is a project.

Needed changes:

- To restore a project we need to be able to select an entire project 
easily.

- Full backups. Project files are treated as one file. Incremental 
backups must make an increment of the entire project every time. This 
will take up a lot more space on the disk. Only keeping one copy of 
files that have not changed would be a good idea. This requires a way of 
  checking this. A simple "compare" or an MD5 checksum. This will 
require a way of tracking these files and what backups they belong to. 
Either using a database or a seperate index of these files.

- The ability to manually start a backup from bobs would be a good idea.


Design Issues:

I was originally thinking of backup methods as a sort of plugins to 
bobs. Bobs would be the controller and the plugins would handle the 
actual code in respect to making backup and restoring files.
This still seems to be the way to do it.

I think some of the functions in class_backup and class_restore should 
be extracted to something like backup_smb.php, backup_nfs.php and 
restore_nfs.php.
A clean and well defined data structure should be used to pass data to 
the plugins.

This would make it easier to make stuff like "backup_smb_project.php"

Rene