FileBackup 0.1 beta is out

[monghidi]

Hi blast2007,

I am using the filebackup module for the first time, it works great and I'm impressed 

Here are a couple observations if you don't mind:
First, I get this error when saving preferences:

Invalid path to tar utilities tar (GNU tar) 1.15.1

Preferences are set like this:
  Path: /bin
  Backup params: -cpzvf
  Restore params: --directory / -xpzf

Here's the mystery (to me anyway) -- the module seems to work just fine, even when it 'fails' on saving preferences. Is there something I am  misunderstanding about the preferences?

Second, here are some musings on features that might be nice to have.
1. Ability to declare exclusions, maybe by file extension/wildcard, by directory, or both.
2. Ability to set new paths and config items on restore, for a case where you are copying a site to start a new one at a new domain. This isn't thought through on my part. Perhaps this is related to the question about editing the config.php 'from the backend'? Maybe RonnyK could chime in?
3. Links to the .tgz files, but WITH protection unless you're a logged-in admin.

Last thing: could you explain about this please?

If you think to leave backup files in directory you can add .htaccess file for download control.

Thanks!

[blast2007]

Here's the mystery (to me anyway) -- the module seems to work just fine, even when it 'fails' on saving preferences. Is there something I am  misunderstanding about the preferences?

I've tested both on my own server and on my HSP but I can't see an error like that. I'll check.

1. Ability to declare exclusions, maybe by file extension/wildcard, by directory, or both.
2. Ability to set new paths and config items on restore, for a case where you are copying a site to start a new one at a new domain. This isn't thought through on my part.

Editing the first and the second preference field  "Tar backup parameters:"  & "Tar restore parameters:" you can set esclusion and path you prefer. You have to check tar manpage for details.
Instead if you're going to clone a site, you can edit config.php with other module for setting new server parameters just after restoring your tgz file.

3. Links to the .tgz files, but WITH protection unless you're a logged-in admin.
Last thing: could you explain about this please?

If you think to leave backup files in directory you can add .htaccess file for download control.

I've solved permission problems without needing console access copying this simple php script http://www.krizleebear.de/phpaccess/dynamisch/ in directory to protect. It would be possibile in future to extend my module using admin account to protect backup directory.

Thanks a lot for your comments.

Regards
blast

[tigercat]

If you point your browser at http://www.yoursite.com/admin/backup/tg ... _xx_xx.tgz you can download your backup from webpage.

There is a blank index page, but I think that is dangerous to left tgz backup in directory because it could be tracked by spider and /or bot and someone could try with many and many attemps to download it with  "filebackup+random pattern".

If you think to leave backup files in directory you can add .htaccess file for download control.

Is it safe enough to put backup files to any folder using .htaccess for access control?
If not this is quite a risk because people might get raw data of your complete website.

[blast2007]

Is it safe enough to put backup files to any folder using .htaccess for access control?
If not this is quite a risk because people might get raw data of your complete website.

Hi Tigercat,
I agree with you that it's a risk to leave saved backup files on server.
It's a limited risk on intranet server but for production internet server the best option is to backup files (with .htaccess present), download the tgz file on local PC and then delete file from server (from FileBackup webpage) as soon as possible.

Thanks for your comment.
Regards
blast