I get about 4-6 of these pointless messages a week...

<?xml version="1.0" encoding="UTF-8"?>
<execution-result status="success" log-location="/usr/local/psa/PMM/sessions/2016-04-30-033102.974/migration.result"/>

I still get warnings on my backups - perhaps we could have some control over the types of warnings that are given? As is stands I don’t bother checking now because there are *always* warnings even when nothing is wrong. It’s a bit like the Apollo 13 situation where the master caution and warning alarm was turned off on hydrogen tank 2. We know how well that went. We’ll never know if there is a real problem with our backups if pointless warnings remain abundant.

I'm still getting this error in a Plesk 12. It's so frustrating.

Well I do care, otherwise I wouldn't be raising this issue here. And others have discussed this on the forums but it was left unresolved.

Maybe I have been misinformed but the way I understand it is that previously these files were backed up because the backup process ran with a higher permissions group and now it (legitimately) doesn't have sufficient permissions to include those files.

Ideally we need one of two scenarios...
1/ a backup that excludes those files because it respects it has no permission for them
2/ a backup that runs with higher privileges (as it did before) and can legitimately copy those files.

I'm not trying to convince anyone, and my opinions carry little weight. I'm just trying to convey a problem that affects me, a new issue that has come about simply by upgrading, has been discussed by other before me, and is currently addressed.

If you think it's because I can't be bothered to fix something then you've seriously underestimated why I've tried to highlight this issue. I use plesk, I use backups, permissions are correct, I just want this product to work without sending me pointless warnings. I don't want genuine errors to be drowned out by these reports. Warnings are useful if you can act upon them.

From 9 months ago...
http://forum.parallels.com/showthread.php?288782-Backup-Problems-Plesk-11-5-40-MU3
http://forum.parallels.com/showthread.php?287722-quot-Failed-to-pack-files-back-quot-Backup-Error

Well, this system is not about me convinced by your opinion, but about hundreds of people supporting some idea (or not supporting). If we see in the system that most common request is to hide warnings about incomplete backup - we probably reconsider, but till then we continue the policy of warning about non-backed up files.

You can redirect the warning to trash if you don't care. Or you can fix permissions if you care.

Okay, so "misconfigured permissions" caused a trouble free backup.

Now when I backup with corrected "misconfigured permissions" I get warnings.

Warnings I can do nothing about and serve no useful purpose, other than to tell me that files that cannot be reached (and will never be reached) weren't included in the backup.

Why bother trying to include them if the "fixed permissions" mean that you can't ever back them up and it will always generate a warning.

And no, I don't like the idea of the message expanding into a list of all the files that weren't backed up. That doesn't address the issue and only makes things worse in my opinion.

At least give us the option to skip those directories in the backup process

I wouldn't say "worked fine" for a backup missing some files because of misconfigured permissions. Starting next version, the message will list each specific file which cannot be accessed. Apache files are backed up, so just make sure all your files can be read by apache or sys user.

What about removing files you cannot access with the new backup procedure, so that you don't get the warning? There's no point having a warning about something you can do nothing about is there?

Okay so it's not a bug. Lets call it a new feature then. It worked fine and dandy before the upgrade. Now my email inbox is flooded with warnings. How am I supposed to spot a genuine error with all the false flag messages?

Why wasn't this addressed before I upgraded, it was talked about in the forums over six months ago. (before you ask, that only became obvious after trying to find out more about these error messages). Same server, new plesk, new problem, can't see how it is anything but plesk generating this error.