Support

I have a Solo profile that does not have a database backup because there is no database.  For some reason, likely because I setup something incorrectly, I get the following message everytime the backup runs: Last Tick   : 2020-09-23 06:30:00 GMT-0500 (CDT)Last Tick   : 2020-09-23 06:30:00 GMT-0500 (CDT)Domain      : PackDBStep        : Substep     : Memory used : 2.14 MBWarnings    : POTENTIAL PROBLEMS DETECTED; 1 warnings issued (see below).Unreadable file /var/www/backup/moodlebackup/b26ff2d0.sql. Check permissions

The debug log is attached.

/var/www/backup/moodlebackup/b26ff2d0.sql is an actual file within your site.  The file is not readable.  Please check the permissions on the file to include it in the backup or just exclude the file from the backup.  Since you have to database for the site, I can't imagine why you need a sql file.

Hi, unfortunately, that sql file seems to be being created by Solo and then removed when the solo back up is done.  When I look for that file in that directory, it doesn't exist.  When I run a little ls every 10 seconds, I can see the file get created and then see it get deleted.  It seems that it's SOLO who is creating the file. 

Ah!  Are you backing up Solo along with your target site?   Solo would use a database and would export it as a sql file.

Hi, yes I am.

So how do I keep this problem from happening other than exclude SOLO from the backup?

Davide is working on another thicket with the same exact problem.  He thinks we may be doing something in the wrong order and it only show up when you're backing up Solo and you're doing a files-only backup, no database.  For now, all you can do is exclude Solo, but this is being looked at from the programming level and we expect a fix shortly.