Full Client Backup

Discussion in 'Installation/Configuration' started by Tamer.Baset, Jul 15, 2020.

Tags:
  1. Tamer.Baset

    Tamer.Baset New Member

    I am still new to ISPConfig, and it's a wonderful panel.
    I am still evaluating all aspects of the panel before I start using it in my servers, and so far a lot of aspects are very satisfactory, however I am having an issue with finding full client backup.
    What I mean by full client backup, is that I want everything related to a certain client backed up, not only websites, DB and emails, but also ISPConfig data, configurations, passwords, everything. so if I want to move one client from one server to another for example, I just take those backup files, restore them and the client is set up. (This is functionality exists in my current panel).

    Also, I am not able to find backup for ISPConfig itself. so If I need to take periodic backup of ISPConfig, with all clients, resellers, sites, emails, to be able to restore that backup whenever needed. where is this functionality in the panel?

    Thanks
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    What you need to take is a full server backup, you can use any Linux backup software for that. There are even ISPConfig specific backup scripts like this one: https://www.howtoforge.com/community/threads/ispconfig-3-back-res-a-backup-and-restore-script.41609/
     
    ahrasis likes this.
  3. Tamer.Baset

    Tamer.Baset New Member

    But what if I want the backup for only 1 client? consider the scenario that I own several servers, and I want to move a specific client from one server to the other. in this case I don't want the full server backup.
     
  4. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    I copy database dump and tar file of the web directory tree to the other host and restore them there. Works for me.
    Moving e-mails is more work, but there are threads on how to do that on this forum.
     
  5. Tamer.Baset

    Tamer.Baset New Member

    Yes, the user data is easy to backup this way, but what about ISPConfig data for this user (his domains, email accounts, passwords, etc...)?
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    That's part of as full backup of the server, see my post #2 for a script that does a full backup.
     
    ahrasis likes this.
  7. Tamer.Baset

    Tamer.Baset New Member

    Thank I will check it now.
     
  8. nhybgtvfr

    nhybgtvfr Active Member

    if they're all ispconfig servers, the client exists as a user, with access to create sites on every server specified in the client limits.
    if you want to move a client from one server to another, you don't need to backup the client details on one server to restore to another.
    if you want to move a client to another server, just add that server to those listed in client - limits tab - web limits. (and database limits if databases on are the same webservers)
    you can then manually update the server_id in the web_domain table and the web_database table if the database is also moving.
    run a resync for 'websites' and 'client database configs' for the server the client is being moved to. that'll create the website area, and blank database on the new server. (probably want to update server_id for the client in ftp_user and resync ftp accounts as well if ftp users exist, same with shell_user)
    then just copy the website files and database from the old server to the new one, change the dns, and clean up the old sites/databases from the old server.
     
    ahrasis likes this.
  9. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

    This type of backup does not exist in ISPConfig, and I don't remember anyone posting any tools that did that. Aside from the other answers which address some backup/move issues, there is a migration toolkit for purchase which can move I think (not positive) domains (it may be full clients, not individual domains?) between ispconfig servers, but the approach is different, it's not "backup everything including panel metadata to a single file and upload to new server," it sets up the panel info (client, limits, etc.) via an api, and you sync data in a separate step.
     

Share This Page