HomeUserBackup Feature Specification

[Sandis Neilands]

Hello Aigars!

On 12/2/05, Aigars Mahinovs <aigarius at debian.org> wrote:
>
> I would be very happy to hear any constructive criticism and feature
> suggestions as I plan to do a slight refactoring of SBackup and thus
> now is the best time to come up with thing that would influence the
> new architecture of the system.



Few suggestions:
1. In case of manual backups, backgrounding process is bad idea. What if it
fails? And even if it won't, i'd like to know, what it is doing and when
will it finish. I can't easily cancel it eihter. Backgrounding should be
optional not default.

2. Stephen Hemminger mentioned already that restore is more important than
backup itself. Sbackup is only usable in gnome, but what if user runs kde?
And lack of CLI is really important, since sbackup is not usable in rescue
mode (in case x or gnome is broken OR machine is server OR machine is
administrated via ssh, etc.)

3. If sbackup worked in CLI it should include itself in every backup, but it
shouldn't be compressed. This would help in situations,  when user decides
to switch to another distro, where sbackup is not included. It would also
help, if /usr/sbin  is (accidentaly) deleted or damaged, but it was included
in last backup.

4. User data should be seperated from system data (seperate archives). When
I'll upgrade to drake or change distro I would like to have an option to
restore only user data, not /bin, /usr, /etc, etc. This would also let me
easily get rid of old system data, which won't be used anyway, but still
keep useful user data archives.

5. Ordinary (non-root/sudo) users should have a right to use this tool too.

Have you checked other backup tools included in ubuntu? I haven't so perhaps
it is  possible to build upon them?

--
Sandis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ubuntu.com/archives/ubuntu-devel/attachments/20051203/8fc275ec/attachment.htm