I would appreciate some help with how to configure backup_migrate with Quickstart.

I am trying to simulate the approach I have used on a server of placing the backup_migrate directory above the webroot for greater security. From what I can figure, and I may be totally wrong, I have done the following:

I have multiple domains that will each be virtual hosts. I have created the domain example.dev and I have created directories for the domain example:

/home/quickstart/websites/files_private/example/backup_migrate/manual

and

/home/quickstart/websites/files_private/example/backup_migrate/scheduled

When I attempt to do a backup I get the error:

    * Unable to create or write to the save directory '/home/quickstart/websites/files_private/example/backup_migrate/manual'. Please check the file permissions that directory and try again.
    * Could not run backup because the file could not be saved to the destination.

I have checked the permissions and they appear to be correct but there must be something I am not understanding, possibly related to the quickstart group configuration.

Any help would be appreciated. Thanks,

Izzy

Comments

MichaelCole’s picture

Status: Active » Fixed

Hi Izzy,

This is really out of my expertise. I would check with backup_migrate and put in a support request there.

Websites installed with drush qc-install have these commands run to set permissions:

// download drupal and modules with drush make command
drush_backend_invoke("make $makefile $codepath");

// set file permissions for all files
quickstart_shell_exec("chown quickstart:www-data -R $codepath");
quickstart_shell_exec("chmod g+w -R $codepath");

//...
// Run drupal installer in web browser here.
// ...

// Next two lines reset the file permissions for security
quickstart_shell_exec("chmod g-w \"$codepath/sites/default/settings.php\"");
quickstart_shell_exec("chmod g-w \"$codepath/sites/default\"");

If you get any feedback from the backup_migrate team, reopen this bug and I'll check it out.

Good luck!

Mike

izmeez’s picture

Mike,

Thanks for the detailed answers in #1. I did get it working but I think I can sort it out better with the details you provided. I'll report back.

Izzy

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.