Full disable backups in user and resellers area

castris

Verified User
Joined
Apr 16, 2021
Messages
144
Location
Arcenillas
Hi
I have been looking for how to disable and at the same time remove its presence from the search engine in the user and reseller areas, and from the backup system, since seeing it encourages errors from users and resellers.

A tip but nor work:

Admins Settings > Administrator Settings > Allow Users with less than 0% Disk Usage to create backups

Any ideas?
 
> same time remove its presence from the search engine in the user and reseller areas

important.
 
Thanks for the contribution.

But even so, I don't see the UX.

The user doesn't want to see messages.

The user should not see Backup, but Jetbackup.

Otherwise, it's not a good user experience, nor is it a good thing for support, which is filled with tickets to explain over and over again what was already explained in the welcome email.

I'll look for another way out.

Thanks for everything, friend.
 
I see in first docs, taht is possible remove for all users.

But this doc reclaim a `CDM_` key .
New internal directadmin.conf setting:
never_commands=(NULL)
being fully unset to anything.
The feature allows you to add any CMD_ to this variable, colon separated, so it can never be used on this DirectAdmin server.
For example, if you want to fully prevent the creation of any new Admin account, you can add this to the directadmin.conf:
never_commands=CMD_ACCOUNT_ADMIN:CMD_API_ACCOUNT_ADMIN
in the directadmin.conf.
This is similar to the per-user commands.allow and commands.deny files, which could do this same thing for this example..
However, the feature is global, so it would apply to all accounts, and saves needing to setup the commands.deny multiple times

I'm looking for `CMD_BACKUP` or similar and not see anything.

Do you or anyone know anything about that CMD?
 
login keys should have all possible command API

Code:
:2222/evo/user/login-keys/keys/create
 
1. Not related with you issue: Do not relay only on jetbackup... when I was junior old sys guys always told me 2 is one and 1 is none now days years later I can only say they was right ... ( DrireactAdmin + BorgBackup strategy from the docs is very cost effective way to have second set of backups) not relaying solely on JB which is one jetmongo hangup away of not having recent backups ..

2. Directadmin build in backup maybe not super tool but it allows partial restores (of sites files or db or emails) - so it should be good to encourage customers to take one (backup :)) before doing something important on theirs websites then delete it if not needed ... Recent WP 6.6 upgrade was a good example some people did evening upgrade broke their sites and do full backup restores from JetBackup (without much thinking) which run in the early morning and lost their daily emails ... we got couple of cases...

3. cPanel resellers pay $12 per year for WHMEasyBackup to be able to have offprovider backups ... you have that feature build in in Directadmin backup for resellers (with ftp/ftps) but it is good enough, supports encrypted backups too and you want to stop it - yes I know jetbackup support to add remote location per reseller request but they make it more complicated in 5 than it was in 4 for cPanel you will have more suport load than answer about backup

4. Last but not least - DA build in system offers restores for users / resellers - some power resellers how i called them use it to migrated themselves and also to migrte accounts between servers / accounts - if you block build in backup and start do that for them - worktime spend will be way more than copy paste answe about build in backups...

P.S. Also if you have knowledge base article about that on most moder billing systems when customer start to type ticket about backup it will get them the related articles

P.S.S and I know knowledge base will not help customers that opens ticket with title Question ? but that is part of business :)
 
1. Not related with you issue: Do not relay only on jetbackup... when I was junior old sys guys always told me 2 is one and 1 is none now days years later I can only say they was right ... ( DrireactAdmin + BorgBackup strategy from the docs is very cost effective way to have second set of backups) not relaying solely on JB which is one jetmongo hangup away of not having recent backups ..

...:)
I agree, I continue.

But... I have my own backup strategy based on my own script, which I use both in the hated chapters, as well as in Plesk and now I will use in DirectAdmin, which does not use mondgoDb, nor Mysql.

And yes, after 38 years in the sector, 2 are 1, in terms of efficiency. In fact, one backup is in one country, and another in my office.

My copies are on rented servers with 80TB capacity, and I do not rent them to third parties. The "in home" ones are on a raspberry pi with nas raid.

So I think I am covered on what is and is not a backup system.

But I have also learned one thing. If you leave the user the ability to decide, it makes a mess, and on top of that, they use both.

And both are not a good strategy, because I do not like it.

As for the resellers, they are managed, so with what I charge them, they have covered the migrations between machines when it comes to it. The rest, well, almost all of them have been with me for more than 10 years, so they are not going to migrate much.

Anyway, each business has a scope, a vision.

My happiness is in not having more than 1 ticket a day, and it is usually from new users. So I thank you for the advice, but there are many opinions.

PS: The truth is that more than a response, we have turned this into a thread that got out of hand, and got us talking about more.

PSS: In the end the question was left unanswered.
 
1. Not related with you issue: Do not relay only on jetbackup... when I was junior old sys guys always told me 2 is one and 1 is none now days years later I can only say they was right ... ( DrireactAdmin + BorgBackup strategy from the docs is very cost effective way to have second set of backups) not relaying solely on JB which is one jetmongo hangup away of not having recent backups ..

2. Directadmin build in backup maybe not super tool but it allows partial restores (of sites files or db or emails) - so it should be good to encourage customers to take one (backup :)) before doing something important on theirs websites then delete it if not needed ... Recent WP 6.6 upgrade was a good example some people did evening upgrade broke their sites and do full backup restores from JetBackup (without much thinking) which run in the early morning and lost their daily emails ... we got couple of cases...

3. cPanel resellers pay $12 per year for WHMEasyBackup to be able to have offprovider backups ... you have that feature build in in Directadmin backup for resellers (with ftp/ftps) but it is good enough, supports encrypted backups too and you want to stop it - yes I know jetbackup support to add remote location per reseller request but they make it more complicated in 5 than it was in 4 for cPanel you will have more suport load than answer about backup

4. Last but not least - DA build in system offers restores for users / resellers - some power resellers how i called them use it to migrated themselves and also to migrte accounts between servers / accounts - if you block build in backup and start do that for them - worktime spend will be way more than copy paste answe about build in backups...

P.S. Also if you have knowledge base article about that on most moder billing systems when customer start to type ticket about backup it will get them the related articles

P.S.S and I know knowledge base will not help customers that opens ticket with title Question ? but that is part of business :)
Hello DanielP

Thank you for your honest feedback on JetBackup! We would like to clarify a few items you've mentioned.

Regarding the issue of users losing their daily emails after performing a restore, this could have been averted by enabling the merge flag. The merge option allows JetBackup to restore your backup data while preserving any data on the account not found in the backup avoiding any deletion.

On the third point, you mentioned that JB5 is more complicated than JB4 when supporting remote destinations per reseller request. Can you clarify what feature you found complicated? We highly value our client's opinions and strive to enhance the user experience. If there is any feature that you would like to see on JB5 to make the user experience smoother, feel free to submit a feature request in the link below.

Best Regards,
Trenton V.
JetApps, LLC
 
Back
Top