Sysadmin Wordpress Backup

here's a little hint/tip, the script has defined

Code (Text):

SITESTORE="/var/www"
#create array of sites based on folder names
SITELIST=($(ls -d $SITESTORE/* | awk -F '/' '{print $NF}'))

on some non-centminmod setups /var/www is the upper parent directory for each apache vhost site like centmin mod's /home/nginx/domains. So if you have site called domain.com:

• on non-centmin mod setup, it maybe located at /var/www/domain.com
• on centmin mod setup, it would be located at /home/nginx/domains/domain.com as per outline at https://centminmod.com/configfiles.html

so what that SITELIST is doing is creating an array of sites based on folder names i.e. /var/www/domain.com, /var/www/domain2.com would have SITELIST value = 'domain.com domain2.com' so it treats each folder as a site backup and that is why you see a backup created the way you do as script is treating every folder under /home/nginx/domains/domain.com as a separate site

so one workaround is define SITESTORE correctly as /home/nginx/domains which is parent directory which has each directory name = a nginx vhost site domain name.

Code (Text):

SITESTORE="/home/nginx/domains"

though from what i can see, script will backup everything each /home/nginx/domains/domain.com directory, including the backup directory at /home/nginx/domains/domain.com/backup which you may want to exclude if you have other backup scripts saving backups to /home/nginx/domains/domain.com/backup as it would be doing duplicate backups.

Though the script has no error checking and validation of the backup processes and incorrectly forces --single-transaction option for mysqldump regardless of whether you have non-innodb tables = for non-innodb tables you may not get a safe backup data integrity wise. FYI, proper error checking/validation and conditional mysqldump options and character set determination is built into my dbbackup.sh database backup script for Centmin Mod Premium members

Also chown routine in that script will break sites on Centmin Mod due to files/directories owned by nginx user/group and not www-data. Also chmod recursive commands may break your sites where you have specifically set writable directories with 777 permissions as they would be recursively changed to 755 by that script.

Just my AUD$0.02, rest is up to you and/or other members to chime in

 

yeah totally understand

though strange it required 744 permissions