![]() ![]() If you need to cancel your Crashplan for Small Business subscription, you can find instructions on that here:Ĭancel your CrashPlan for Small Business subscriptionĬrashplan for Small Business does not offer support for CentOS, so I will need to close this support ticket. I understand that our service might not meet your needs. We do not have any plans to begin offering support for CentOS. ![]() We do not have any plans on testing our software with CentOS in the future. We do not troubleshoot issues for issues that occur on CentOS systems. However, as we have already discussed, Crashplan for Small Business simply does not offer support for CentOS. I'm that you were previously able to get our software running on your unsupported system. Here is the final response that I got from their customer service when in reality, the update gave me an installer that explicitly makes their software broken. but that still doesn't make it a good end-user experience to be told I need to re-install my whole OS because my backup software isn't supported on my distro. So it may not be something I need to worry about for those OTHER types of issues i MIGHT run into. I never had their support staff ask me what distro I'm using before, in the rare instances I've had to deal with them in the past. Of course, thus far, I'm only aware of this excuse being given to those of us who are trying to figure out why an update broke our ability to sign into the service. CentOS is.Is.IS RedHat (branding and support contracts do not change functionality), yet (quote from LordPengwin's post) "We do not test our software with CentOS." is, to them, a perfectly reasonable excuse to deny responsibility. are most certainly not) you would have a VERY hard time convincing me that the OS is the culprit, yet they can apparently cling to that excuse to deny responsibility. This installation issue aside, there are other problems one might encounter, and save for perhaps some EXTREME edge-case distros, (which debian/centos/whatever took centos's place/etc. (Technically, this may give SOME validity to their "un-supported" argument, but certainly not in a way that makes me sympathetic.) Despite the fact that I'll obviously be stuck fixing THIS problem on my own, THEIR software is breaking ITSELF in response to the OS, not the other way around. And I stand by that even in this instance with the missing libraries. not vague, cop-out excuses about OS-support, nor an expectation that re-installing the whole OS is a suitable fix for an application. But more to the point.īecause when I'm paying for a service, I expect that when that service isn't working, I'll get a reasonable effort from support staff to resolve the issues with said service. Virtualized/containerized ubuntu is still ubuntu. (at least, no less disingenuous than their support staff clinging to that "not supported" B.S.)įor one, I wouldn't be lying. and also so I don't have to be disingenuous when I say it's running on ubuntu when asking for help. If I had been able to find another unlimited backup provider with any linux support (carbonite doesn't do linux, backblaze only supports it on b2, which is not unlimited), I would have bailed a long time ago.Īt some point, I might experiment with stuffing their app app inside a thin ubuntu chroot or lxc container, and bind-mounting all of my backed-up directories inside of it, just to avoid having to manually work around this every update. "Reinstall your OS and I can help you" is NOT support. Instead, it just gets their customers angry at the support staff because of a refusal to help, or give any useful information whatsoever. other than the fact that drawing attention to their presumably-intentional hostility to non-Ubuntu/RHEL Linux might make their developers look bad. Yeah, and the fact that they can't even explain WHY it doesn't work for us "unsupported linux" users is so absurd. ![]()
0 Comments
Leave a Reply. |