It's been my experience that folks do not like us changing the behavior of the product in any significant way without a Big Scary Message™ obviating such. I think suspended accounts would continue to be backed up by default on existing installs, but perhaps this could be the new default setting for fresh installs?
Let me just make absolutely certain I got this right before this goes to the developers. Please make any final tweaks/suggestions at this time:
CALL FOR COMMENTS #2
Currently there is no way to disable backups from being made for suspended accounts. This is a potential waste of server resources as undesired additional backups of these suspended are generated. The root user should have a setting that disables backups from being made of suspended accounts. Only a root-level user would be able to set this setting.
It is preferred that this setting be in the Configure Backups screen:
For existing cPanel&WHM installs, the behavior should not change, thus this setting should be set to "Enabled" but for new cPanel&WHM installations, it makes sense to have this "Disabled" by default as not to needlessly waste resources making new backups for an account that hasn't changed since the last backup.Code:Backup Suspended Accounts: ( ) Enabled (o) Disabled
Furthermore, this setting should only apply to the generation of new backups and not influence any existing backups that have been made for this account.
Yes, exactly like that.
I started writing the following quoted text but after finishing it, I realize that it is an unneded annoyance. I'll print it just in case anybody else think the same:
This is nonsense because you suspended an account because it won't be able to be accessed anymore until the owner pay the fee. Thus, it simply doesn't matter if the backup is outdated since it is the responsability of the customer to keep the payments flowing to keep the services online.Code:Hey David, I wonder what would happen if the backup is set to be made weekly, and an account is suspended just 1 or 2 days before the scheduled backup day arrives. This is more likely to be a moral dilemma. Should the system take one last snapshot from this suspended backup before it starts ignoring that account when backing up in the future? or should it ignore it from the start even if the last backup for that account may be out of date.
I'm ok with the call for comments. Anybody else?
Okay, I have submitted this to our developers as case: 52161
+1 for this! Any comments from cPanel?
+1 for this feature request
A case number for a cPanel&WHM (not EasyApache) feature will first enter public view when it enters a pre-production version of cPanel&WHM (the EDGE tier). If you have a spare machine, you can test out that new feature and provide your feedback while this feature is just in EDGE via our edge-users mailing list at: Edge-Users Info Page - this way you can submit final feedback just before development solidifies (completes) on a feature.
You can then learn when that version number (or higher) will propagate to other update tiers via the releases mailing list at: - cPanel Inc.
Sometimes we will announce when features seem imminent to go to the EDGE tier but QA is a bit unpredictable as sometimes major issues are found and sometimes thing actually work right the first time around, so we don't always get an opportunity to give advanced head's up before this feature goes to EDGE. However, once this (or any other) feature goes to EDGE, we update the accompanying forum thread accordingly to note it is now propagating through the update tiers.
Regarding this specific feature, this remains early in the planning stages. I don't even see an ETA yet, but it is on our to-do list and as soon as I am made aware of a version ETA, I will update this thread with that information.
Don't want to be annoying, but this is definitely a feature we would like to have.
+1 from me too
Hope we see it happening soon.
Cheers,
Björn
Just to review something here, if you are using incremental and you backup the suspended account it takes no additional space in your daily backups. At some point it should take space for lets say the next monthly or weekly since this doesn't work like de-duplication and needs to backup the data (correct me if I'm wrong).
My question would be, why keep the account on the server at all if resources are an issue?
Also, would there not be a value if you kept the site to hopefully bring the client back online once they paid up?
If the server crashed and you had all your paying accounts, but not this suspended person, would you really care if it was lost?
Most of the time the answer to that is pretty much no, but if you didn't care then why keep it after lets say 30 days in the frist place?
Just my thinking....
Customers sometimes do things like cancel service and tell you they will re-sign for service if you can restore their files from 3 months ago. This issue isn't so much an issue of space, its about completing the backups sooner and conserving CPU and Mem.
GlowHost.com | Professional Managed Web Hosting Since 2002.
>> Fully Managed Dedicated, Cloud VDS, Reseller & Semi-Dedicated
>> Cloud Servers for Enterprise