Author Topic: NEW Backup: Still in Perpetual Beta? Critical Issues Unresolved for Months (CWP7  (Read 502 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
Hello everyone,

I am a CWP7 Pro user, and I would like to publicly raise an issue that I now consider unacceptable.

For months, I have been reporting problems with the NEW Backup module through the official ticket system, but I have received little to no meaningful response. My support tickets often remain unanswered for more than 15 days, which is simply not the level of support I expect from a Pro service.

The main issue is that the NEW Backup module does not send backup notification emails reliably. On the rare occasions when an email is actually sent, it does not indicate whether it refers to a local backup or a remote backup, nor does it specify which backup jobs completed successfully and which failed.

A backup system should not send a generic "backup completed" email. It should provide a detailed report that clearly identifies the backup type, destination, and the success or failure of every backup task. This is not an optional feature—it is a fundamental requirement for any professional backup solution.

Unfortunately, this is not an isolated incident. In the past, we have already experienced situations where software updates broke the backup module completely, making backups impossible to perform. These issues were caused by the software itself, not by server administrators.

At this point, I respectfully ask the development team to treat these problems as a high priority instead of leaving the NEW Backup module in what increasingly feels like a permanent beta state.

I am posting this here because the official support channel has not provided acceptable response times or meaningful updates regarding these issues. I sincerely hope this post receives the attention it deserves and that the development team can provide concrete information about when these long-standing problems will finally be resolved.

Thank you for taking the time to read this, and I would also appreciate hearing from other CWP users who may have experienced similar issues.

Best regards to everyone in the forum.

Offline
***
Most of the time, they don't bother responding to the support tickets. I have been waiting for my tickets (regarding my affiliate commission) since Feb 2026, but they don't respond even after multiple reminders.

They will fix the bugs when they want to, user-reported bugs are not given importance unless they themselves think about fixing the bugs.

Offline
*
I appreciate your reply, and unfortunately it seems I'm not the only one experiencing long response times from support.

For me, however, the main concern is not just the lack of replies to tickets. It is the current state of the NEW Backup module itself.

After previous forced updates, both local and remote backups were broken for quite some time. Thankfully those issues were eventually fixed, but only after many reports and a long wait.

The remaining issue is, in my opinion, just as important: backup notification emails are still unreliable. Most of the time they are not sent at all, and when they are, they contain almost no useful information. They do not specify whether the notification refers to a local or remote backup, which accounts were successfully backed up, whether any account failed, or if the backup completed with warnings or errors.

This affects both local and remote backups.

A professional backup solution should provide administrators with enough information to immediately verify the outcome of scheduled backup jobs. Instead, I still have to manually log into the server and check every backup to make sure everything completed successfully. That defeats one of the main purposes of having automated backup notifications.

What concerns me even more is that this issue has remained unresolved for months, despite being reported through official support tickets, while the forum has also received no response from the development team.

I am not posting this to criticize anyone personally. I simply hope the developers acknowledge this issue, provide some feedback, and let the community know whether it is already being worked on and when we can reasonably expect a fix.




CWP7 PRO