Hi. Thanks for a great product. However, we are having a problem with Solo on a site which has a quirk. The site has a directory symlink which is not accessible by Apache (a feature of the way the hosting provider manages MySQL backups).
I had thought that I should be able to avoid getting a warning by adding the directory to the exclude list, but it doesn't seem to work.
The backup is executed as a cron job.
I get (with sitebase hidden):
Does the piece of code that checks whether something actually exists run before the exclude list is considered, or have I somehow got something wrong in specifying the exclude?
The backup restores OK but when the cron output is checked we pick up the warning every time, so it would be good if this could be prevented if possible.
I had thought that I should be able to avoid getting a warning by adding the directory to the exclude list, but it doesn't seem to work.
The backup is executed as a cron job.
I get (with sitebase hidden):
Akeeba Solo CLI 2.4.0 (2017-09-12) Copyright (C) 2014-2017 Nicholas K. Dionysopoulos / Akeeba Ltd ------------------------------------------------------------------------------- Akeeba Solo is Free Software, distributed under the terms of the GNU General Public License version 3 or, at your option, any later version. This program comes with ABSOLUTELY NO WARRANTY as per sections 15 & 16 of the license. See http://www.gnu.org/licenses/gpl-3.0.html for details. ------------------------------------------------------------------------------- You are using PHP 5.6.12 (cli) Starting a new backup with the following parameters: Profile ID 1 Description "Command-line backup" Current memory usage: 3.32 MB Unsetting time limit restrictions. Site paths determined by this script: APATH_BASE : <sitebase>/public_html/akeeba Last Tick : 2017-09-25 05:00:26 GMT+0000 (UTC) Domain : init Step : Substep : Memory used : 6.57 MB Warnings : no warnings issued (good) ... Lots of good backup lines ... Last Tick : 2017-09-25 05:00:43 GMT+0000 (UTC) Domain : Packing Step : Substep : Memory used : 7.64 MB Warnings : no warnings issued (good) Last Tick : 2017-09-25 05:01:06 GMT+0000 (UTC) Domain : Packing Step : <sitebase>/vendor/passwordlib/passwordlib/lib/PasswordLib/Random/Source Substep : Memory used : 7.68 MB Warnings : POTENTIAL PROBLEMS DETECTED; 1 warnings issued (see below). The symlink <sitebase>/mysql_backups points to a file or folder that no longer exists and will NOT be backed up. Last Tick : 2017-09-25 05:01:10 GMT+0000 (UTC) Domain : Packing Step : <sitebase>/vendor/erusev/parsedown/test/data Substep : Memory used : 7.69 MB Warnings : no warnings issued (good) ... Lots more good backup lines ... Backup job finished successfully after approximately 8 minutes =============================================================================== !!!!! W A R N I N G !!!!! Akeeba Backup issued warnings during the backup process. You have to review them and make sure that your backup has completed successfully. Always test a backup with warnings to make sure that it is working properly, by restoring it to a local server. DO NOT IGNORE THIS MESSAGE! AN UNTESTED BACKUP IS AS GOOD AS NO BACKUP AT ALL. =============================================================================== Peak memory usage: 11.33 MB
Does the piece of code that checks whether something actually exists run before the exclude list is considered, or have I somehow got something wrong in specifying the exclude?
The backup restores OK but when the cron output is checked we pick up the warning every time, so it would be good if this could be prevented if possible.
