Support

Multi-profile backup is a bad idea for several reasons, most of which have to do with performance, memory usage and host limitations. A --profile=all switch also has a major catastrophic potential. It would be like giving away guns for free, even to children. Bad idea.

Regarding the forum, I ripped it off. I was using NinjaBoard and it has shown no signs of moving forward since last June. Besides, I stopped doing free support since July 2011, for reasons I've already published. That's why I had to create a new, custom ticket system.

Very bad idea. These solutions get triggered with page loads.

Backing up an entire site (database AND files) of any size is a very resource intensive process which lasts a hell of a lot of time. If we were to try backing up your site in a single page load, we would be bound by the following technical limitations:
- PHP timeouts. Hosts don't allow scripts to run forever. They put a time cap. Going beyond that cap causes a blank page or a 500 error to appear on your site.
- Memory limits. Your host doesn't allow scripts to use infinite amounts of a very finite and expensive resource that RAM is. Trying to use more than a few Megabytes at a time causes memory outage errors.
- CPU usage timeouts. Your hosts, in order to ensure that you don't bring down his server, will enforce CPU usage limits. If you use more CPU, they will kill the script. If you do that all the time they will simply block your hosting account.
There are also a few more (much more technical) considerations, but it suffices to say that for these reasons taking a full site backup in a single page load is impossible. Therefore we have to split the process in multiple page loads. Keep that in mind.

Now, computers are not humans. They need a trigger to launch programs. The trigger in web hosts can be either a CRON job or a page load. You are beefed about CRON jobs. OK then. Let's assume you want to use page loads. A full site backup takes anywhere between 30 seconds to 10 hours. Would you expect your site visitor who had the misfortune to come to your site at the time the backup should fire to wait forever for the site to load? Of course not.

There is a hidden danger: if the backup doesn't complete before the next pageload, the extension will run the backup command line again. You don't want to know what happens in that case. It's one of the reasons why I had created the Lazy Scheduling plugin, but it had so many issues I just had to stop supporting it. You know what? webcron.org is just fine for scheduling backups. Daily backups would cost you $2 per site per year. That's, like, half a cup of coffee in a year? I think anyone can afford that – plus it's tested by yours truly and it's rock solid stable :)