Hi Boris,
>I'm hoping that you mean the general use of "you"
Rest assured, I was.

>my point was that it is unlikely that something else will get integrated unless
>it is done outside of Mitel
And I believe that this shouldn't be the case. Whenever somebody put together something and advertises it as being capable of doing this and that, you should be able to have a fair expectation that it will do just that (not just some of the time but all of the time -- barring equipment failure, viruses, etc). If Mitel chose to use flexbackup with dump as a means of backup, we as consumers should also be able to expect that the combination should work (not some of the time but all the time). In fact, we should just assume that just setting the options in server-manager should work - and not worry about what goes on behind the scenes.
After all, flexbackup is not tied to dump. Flexbackup can also use tar, etc in place of dump. I would have thought that it would be fairly simple for Mitel to put out an Update (aka Service Pack) to switch to using tar or some other supported engine to drive flexbackup.
> Of course, there are third-party options like Arkeia.
Yes and my gratitude to Shad Lords for his work on this

. However, my opinion that this is a problem that Mitel should address themselves still stands.
PS. By the way, dump has undergone further redevelopment. Whether the current version (not necessarily the one in SME) addresses the problems and concerns raised by Linus or not, I don't know. But since we get hit with comments like "if it isn't supported by RH, then it isn't supported", it would be double standards if it is ok to use something like dump when it is not recommended by RH.
Kelvin