Skip to content

creoline

My feedback

11 results found

  1. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    This is a valid request, so we'll look into it. There is no ETA at the moment, but we would really appreciate you voting for this request so that we can accurately assess its popularity relative to other features.

    Thanks in advance!

    --

    IG


    I have merged the request by creoline into this existing one. Actually, adding a parameter like --single-transaction requires careful consideration of many side effects that this can have. It is explained well in https://stackoverflow.com/questions/41683158/mysqldump-single-transaction-option and comments. But like IG I also think it is a valid request.


    We will consider this functionality in upcoming releases if it will be popular.

    Everyone, please continue voting for this feature if you consider it important.

    --

    PD

    An error occurred while saving the comment
    creoline commented  · 

    Actually, all database backups are exported with a "LOCK TABLES" operation which seems to be outdated for InnoDB.

    I would suggest allowing users to choose the locking strategy on exporting database dumps in the Plesk GUI.

    There should be options like:
    - Single Transaction (Not supported for MyISAM)
    - Lock Tables

    The export button is very useless for InnoDB users with traffic on their websites because a global READ lock applied also if no MyISAM tables are available.

    creoline supported this idea  · 
  2. 4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    creoline shared this idea  · 
  3. 274 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    creoline supported this idea  · 
  4. 5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    creoline shared this idea  · 
  5. 22 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    creoline supported this idea  · 
  6. 679 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    creoline commented  · 

    Are you planning to add CardDAV and CalDAV support too? If you're just implementing active sync it will be for example a problem on iPhone because the exchange layout shows also Calendars, Contacts and Todos. So in conclusion I would be really happy if there will be a plesk native CardDAV and CalDAV Server too. :)

    creoline supported this idea  · 
  7. 85 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    creoline supported this idea  · 
  8. 574 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    creoline supported this idea  · 
  9. 411 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    creoline supported this idea  · 
  10. 542 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We have serious doubts this function can really increase server security:
    1) Plesk has built-in protection against brute-force on login – it will lock the login form. So no one can try multiple attempts
    2) Arbitrary login name adds very little guess-complexity to a proper password. If you have concerns for your login brute-forced – add another 5-7 characters into your password and feel safe.

    As changed login name is still very likely to be some sort of vocabulary word or derived from your other account name – this function would only give a false sense of better security. Your security strength is in complex password, not in a complex login name. If you have one good password, you don’t need to treat login as your “second password” – one good password is enough.

    As for concerns that default password requirement is set in “weak”, that fail2ban module is not…

    creoline supported this idea  · 
  11. 1,071 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hi all, Thanks for your input, really appreciate this! As you know, in Plesk Onyx 17.8 we made a significant improvement that allows you to use several cloud storages or even SFTP for remote backups. In Plesk Onyx 17.9 we will continue to improve Plesk Backup Manager in general and Flexible Backup Scheduler Manager in particular.

    Based on the initial description and comments I can highlight 3 scenarios in the scope of this request:

    #1. Keep Daily & Weekly & Monthly backups at the same time: (Example: 2 weeks of daily backups + weekly backups by each Monday)

    #2. Backup to different storages (like daily to FTP and monthly to Google Drive)

    #3. Multiple Storages of the same type (like 2 different FTP servers)

    ID in our Issue Tracker: PPM-1701
    -DL

    creoline supported this idea  · 

Feedback and Knowledge Base