Hi
well - of course it can be built up to a general backup/restore system for the whole server and all the other things - but I just wanted to discuss the basics - no removal of older backups if the new backup is not finished.
This used to work like this until summer... with beta5 many engine scripts were rewritten and this detail has changed.
imscp-backup-all:
line 108: $rs |= execute("$main::imscpConfig{'CMD_RM'} -rf $bkpDir/*", \$stdout, \$stderr);
line 130: my $rs |= execute(join(' ', @cmd), \$stdout, \$stderr);
where $cmd is the tar command....
I know that if during the backup the (typo3) website is being visited, then it often happens that tar ends with a message
(/bin/tar: ./htdocs/typo3temp: file changed as we read it) which is recognized as error - new backup is removed and a mail is sent.
At least it seems that now this type of "error-"backup is not deleted - and should be usable.
To the other backup wishes:
- How many backups to keep.
-> imscp backups are kept for 14 days.
- Complete and differencial backups.
-> hm... So this looks rather like you want to integrate a full backup software into imscp
- What to backup (only mail, only web, all)
-> maybe an option... - but then with: "mail" every hour, "web" once a day etc...
- Domain backup/Full Server backup (for the full server backup when backing up the domains go backup domains or backup only the backups from the domains)
- Restore option for the domain and for the whole server.
For now a rsync backup makes sense for the parts of the server you wish to have backed up (without the backups made by imscp). For an archive you may need a more sophisticated software.
I included a small feature to let the user define some files/folders which should not be backed up - e.g. for people who have a copy of a dvd on the server...
/J