Multiple backups

  • DragonZX
    there is also the question if the backupspace should be included in diskspace or not, should it be a free service or a paid service...and so on


    gabesz86
    anyone here is understanding what you like to achieve...but that is what you want.


    i-mscp dev´s allways have to find a balanced way wich will fit for most of theire users not only for one...and just that is not allways easy.


    but to help you further with a quick solution for your needs you just have to multiple
    my "dirty solution" to the amount of days you like. then inside the crons you set wich cron should run on wich day.
    you also have to do a chown/chmod to the backup directories(can eaven be done inside the backup-script) so that they are readable/changeable by user.


    so at this stage you have your backup-strategie.
    then you have to inform the user(s) that they have to rename the related backup-folder to the std. backup-folder(std. backupfolder has to be renamed first)
    so the user can restore any backup wich exists


    in this way you have what you want in about 15min.


  • Hello ;


    And what about a new feature for backup on demand?


    I see something like this:


    1. Admin can allow reseller to activate backup on demand option for their resellers
    2. Reseller can activate backup on demand for their customer and specifies how many demand they can trigger per day?


    Of course, we still have daily backup (one per day).


    It's easy to add so ?


    Thanks for using i-MSCP.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206


  • Yes, backup on demand is not so hard work, but now it can make more questions, then answers.
    - Client must choose what to restore (GUI changes)
    - Reseller or admin must choose how much disk space it wil need to make for backups (it's better to know how many disk space use only site, for example some of my clienst stored there about 40 GB of data).
    In this case we must rewie the backup engine, don't hurry. I think it must be only in 1.2.0


  • Yes, backup on demand is not so hard work, but now it can make more questions, then answers.
    - Client must choose what to restore (GUI changes)
    - Reseller or admin must choose how much disk space it wil need to make for backups (it's better to know how many disk space use only site, for example some of my clienst stored there about 40 GB of data).
    In this case we must rewie the backup engine, don't hurry. I think it must be only in 1.2.0


    Backup on demand button will only trigger the backup script for customer.
    Disk space for user should be based on customer disk space limit (no space for backup then, no backup). Now, if your user are storing about 40GB, it's your problem. You must fire them about your rules or downgrade their space limit to avoid such thing.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206


  • Backup on demand button will only trigger the backup script for customer.
    Disk space for user should be based on customer disk space limit (no space for backup then, no backup). Now, if your user are storing about 40GB, it's your problem. You must fire them about your rules or downgrade their space limit to avoid such thing.


    But it may cause more bugs first of all. It's only a wishlist. I understand what you want, but I disagree with you. First of all we must concentrate on beta testing and fixing existing bugs, not to open new bugs to your own head. It will provide us to release 1.1.0 ASAP.


    Also, for example I said about a problem, that may cause a Critical bug. I have only 2-3 such clients, but some users may have >30 such clients, and they may does't know about it. Don't hurry, we need a review. Also it may cause a server overload.

    Edited once, last by DragonZX ().


  • But it may cause more bugs first of all. It's only a wishlist. I understand what you want, but I disagree with you. First of all we must concentrate on beta testing and fixing existing bugs, not to open new bugs to your own head. It will provide us to release 1.1.0 ASAP.


    Also, for example I said about a problem, that may cause a Critical bug. I have only 2-3 such clients, but some users may have >30 such clients, and they may does't know about it. Don't hurry, we need a review. Also it may cause a server overload.


    Re ;


    Who has says that it will be implemented in 1.1.0 ? Also, you are talking about a critical bug without explain your thinking. Please, take care of my poor head. :D


    Thanks.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

    Edited once, last by Nuxwin ().

  • i implemented this via cron. created "archive" folder in the backup directory, and the cron moved/renamed the backup files to the archive folder for people that requested archiving. this is why the main backup script had to be changed a bit for me so that it did not delete everything in backup directory.


    i do still have plans to completely overhaul the backup system. i cancelled the idea of uncompressed tar + rsync because pbzip2 is much faster now.


    future, i am thinking of using Duplicity. it is compressed with rsync, and incrementals, so it can archive many days with just the incremental backup sizes. it also has very simple commands for restore (files or db or both), that should be easy to initiate from i-MSCP, as well as create a new backup-on-demand.


    new database entries and backup archiving option for how many days to keep, with duplicity referencing that for backup task.


    this is the best option so far, that I have found. it is a good amount of work I have not gotten around to yet... been working on infrastructure and trying to figure out how to manage i-MSCP while it's not actually multi-server yet and i need it to be haha.


    but Duplicity seems to be the best answer for the future...


    Also, I think backups should count towards disk quota. or perhaps have its own disk quota, that is most preferable.

    Edited once, last by anarking ().

  • anarking can u share me how can you do it? :) I want to similar your solution. Or myabe i will make it with cron jobs if anyone help me.



    1. Admin can allow reseller to activate backup on demand option for their resellers
    2. Reseller can activate backup on demand for their customer and specifies how many demand they can trigger per day?


    Of course, we still have daily backup (one per day).


    Nuxwin I want to daily backup too, I just want to keep them couple days like the i-MSCP config backups. If i-MSCP config backup system know what I want, I don't understand some people why told me "this is a big job". Ok I know some of my Idea a part of a bigger job, but NOW I will be happy if I keep daily backup more than 24hour. I have no time to save every customer backup data to my computer evry day. I think easier keep backups more than 24 hour. :D If need more space, I will growing they disk limit. :D

    Edited once, last by gabesz86 ().

  • I would even push this subject further by simply asking: Why is there no backup of the mail boxes?! Imho this is a mandatory feature.


    An why am I only able to choose a whole domain for backups? It would be much better to make an option for every sub-domain.
    I'm hosting a small open source software download site and I don't want to gzip a software repository with 200 isos every night, just because it's in /var/www/virtual/domain/subdomain/htdocs.

  • I wrote a patched version of the imscp backup script. I modified the script to keep the backups for seven days.


    The original file is located at: /var/www/imscp/engine/backup/imscp-backup-all
    Make a backup of the file, before you patch it.