Re: [Bobs-devel] work to be done

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

So far, so good..

I've got smb backup and restore working.
Still need to do nfs backup (should be a walk in the park)

Server ini file changes include:
"smb_share" The name of the remote smb share
"backup_method" The method used for making backup. (rsync/smb/nfs)
"restore_method" Method used for restoring files (smb/nfs)
"server_ip" is optional. If used I assume its a static IP.
"share" is now used as a descriptive label for the backup. (eg. 
/backupdir/bobsdata/server/share)
"rsync_share" is the name of the remote rsync share
"password" is now cleartext.

I found what seems to be a bug in filename handling when restoring 
files. I still haven't isolated the precise cause.
The admin interface is broken in regards to creating correct ini files.


Some things to think about:
I've got a share which contains several projects. These files are all 
"linked" together on a project basis. Making backups of individual files 
does not make that much sense since they depend on each other. I was 
thinking something in the line of making a manual "do backup now" button.
Maybe creating a list of the projects and being able to select one (or 
more) of them for a backup.
A set of rules for the list could be an option. eg. each dir in the root 
of the share is a project. Only make full backup of each project.

Any good ideas?

An editor for the exclude lists and the linked files list is needed.
Maybe someone has already made one we can use.

I'll post news as I go along. I'll do a cvs commit of the changes soon.

-Rene




Rene Rask wrote:
> 
> I think the settings system will have to be reimplemented.
> I need some additional settings and options.
> Cleartext passwords are needed for smb access.
> Security must be enabled using .htaccess files to prevent password from 
> being read.
> Files must be chmodded to 0600 to prevent shell users from reading the 
> files.
> 
> I'll begin working on the SMB access method.
> Also an nfs only method would be nice. Rsync is not strictly nessecary 
> to make backups. But it is a nicer way of doing it since it will (I 
> think) use less processor power and consume less bandwidth.
> 
> Basically this can be split into two tasks. A new configuration editing 
> system and a new backup class. (I think I'll rename function.php to 
> class_backup.php)
> A more generic configuration editor would be nice.
> If you want to help break things please let me know. I'll not commit my 
> work to cvs until it works to avoid breaking the cvs tree.
> 
> Please comment on these ideas.
> 
> I've tried to descripe how I think the new settings should be created.
> 
> When clicking on "create new server" the following questions are asked
> - choose backup method:        Smb / Nfs / Rsync
> - choose restore method:    Smb / Nfs
> - choose network address type:    Dns / static Ip
> 
> Based on the above answer the appropriate settings below are shown.
> - Login name:        Login name for this server (the login needed for 
> eg. smb access)
> - Password:        Password (stored as clear text. Needed for smb access.)
> - Server name:        The servers network name
> - Server IP address:    The servers Static IP address
> - Rsync share name:    Rsync share name
> - NFS share path:    NFS share path
> - NFS share name:    Descriptive name for the share (unique name for 
> this server)
> - SMB share name:    SMB share name
> - Active:        Is this server active (do I need to make backups?)
> - Backup days:        Which weekdays to make backups.
> 
>     -- options not implemented yet --
> - Incrementals:        How many incremental backups should there be.
> - Compress:        Should incremental files be compressed?
> 
> 
> 
> -Rene
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Caffeinated soap. No kidding.
> http://thinkgeek.com/sf
> _______________________________________________
> Bobs-devel mailing list
> Bob...@li...
> https://lists.sourceforge.net/lists/listinfo/bobs-devel