{"id":879,"date":"2021-07-23T12:40:12","date_gmt":"2021-07-23T12:40:12","guid":{"rendered":"https:\/\/ssdsunucum.com\/blog\/restore-a-full-backup-cpmove-file\/"},"modified":"2021-07-23T12:40:12","modified_gmt":"2021-07-23T12:40:12","slug":"restore-a-full-backup-cpmove-file","status":"publish","type":"post","link":"https:\/\/ssdsunucum.com\/blog\/restore-a-full-backup-cpmove-file\/","title":{"rendered":"Restore a Full Backup\/cpmove File"},"content":{"rendered":"<\/p>\n
\n
\n
\n

Valid for versions 88 through the latest version<\/em><\/p>\n<\/div>\n

\n

Version:<\/h4>\n

82<\/h4>\n

88<\/h4>\n<\/div><\/div>\n
\n

Overview<\/h2>\n
\n
Warning:<\/div>\n
\n

We removed<\/strong> this interface in cPanel & WHM version 90. Use WHM\u2019s Transfer or Restore a cPanel Account<\/em> interface (WHM >> Home >> Transfers >> Transfer or Restore a cPanel Account<\/em>). For more information, read our cPanel Deprecation Plan documentation.<\/p>\n<\/p><\/div>\n<\/div>\n

This feature performs a full restoration of a single cPanel account from a selected backup file. You can also recreate an account from a remote server with a cpmove<\/code> file.<\/p>\n

\n
Warning:<\/div>\n
\n
    \n
  • \n

    The restore system uses multiple applications, such as MySQL\u00ae. Do not<\/strong> shut down or restart any processes on the server during the restore process.<\/p>\n<\/li>\n

  • \n

    Do not<\/strong> use the skip-name-resolve<\/code> setting in your server\u2019s MySQL\u00ae configuration. This setting will<\/strong> cause serious<\/strong> issues with server operations. If you are not<\/strong> an advanced MySQL administrator, expect issues with this setting. For example, you will see issues with account transfers and restoring backups. This setting will also cause issues with phpMyAdmin.<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n

    File formats and locations<\/h2>\n

    The filename of the backup must<\/strong> use one of the following formats:<\/p>\n

      \n
    • cpmove-{USER}<\/code><\/li>\n
    • cpmove-{USER}.tar<\/code><\/li>\n
    • cpmove-{USER}.tar.gz<\/code><\/li>\n
    • {USER}.tar<\/code><\/li>\n
    • {USER}.tar.gz<\/code><\/li>\n
    • backup-{MM.DD.YYYY}{HH-MM-SS}{USER}.tar<\/code><\/li>\n
    • backup-{MM.DD.YYYY}{HH-MM-SS}{USER}.tar.gz<\/code><\/li>\n
    • backup-{MM.DD.YYYY}_{HH-MM-SS}_{USER}.tar<\/code><\/li>\n
    • backup-{MM.DD.YYYY}_{HH-MM-SS}_{USER}.tar.gz<\/code><\/li>\n<\/ul>\n

      In order for this feature to work, the backup or cpmove<\/code> file must<\/strong> reside in one of the following directories:<\/p>\n

        \n
      • \/home<\/code><\/li>\n
      • \/usr\/home<\/code><\/li>\n
      • \/web<\/code><\/li>\n
      • \/home2<\/code><\/li>\n
      • \/home3<\/code><\/li>\n
      • \/root<\/code><\/li>\n
      • \/usr<\/code><\/li>\n<\/ul>\n

        You may also select a file from your local filesystem.<\/p>\n

        \n
        Note:<\/div>\n
        \n

        When you restore a backup, the system expands the backup or cpmove<\/code> file in its current directory. Make certain<\/strong> that the backup file\u2019s directory contains at least double<\/strong> the backup file\u2019s space. The system uses this extra space for the temporary files when it extracts the backups.<\/p>\n<\/p><\/div>\n<\/div>\n

        How to restore a cpmove file<\/h2>\n

        To begin a full restoration from the backup file of the account, perform the following steps:<\/p>\n

          \n
        1. \n

          If you wish to use Restricted Restore, select the Restricted Restore<\/em> checkbox. The Restricted Restore<\/em> feature lets the system perform extra security checks on the archive file. If part of the file has a security issue, the system will not<\/strong> restore that part of the archive file. This helps mitigate the risk of transfers from unfamiliar sources. The system enables this feature by default.<\/p>\n

          \n
          Warning:<\/div>\n
          \n
            \n
          • This feature is experimental<\/strong>. Do not<\/strong> consider it an effective security control. Exercise extreme<\/strong> caution when using the Restricted Restore<\/em> feature.<\/li>\n
          • Before using this feature, read the Warnings about the Restricted Restore feature section below.
            \n<\/li>\n<\/ul><\/div>\n<\/div>\n<\/li>\n
          • \n

            Select whether to restore the backup file by username or by filename.<\/p>\n

              \n
            • \n

              If you select Restore with Username<\/em>, select the username that is associated with the cPanel account that you wish to restore.<\/p>\n<\/li>\n

            • \n

              If you select Restore with File<\/em>, click Choose file<\/em> and select the backup file from your local filesystem.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n

            • \n

              Select whether to replace all instances of the original server\u2019s IP address with the new address or to only replace basic cPanel-provided A records in zone files.<\/p>\n<\/li>\n

            • \n

              If you wish to overwrite the account with the data in the backup file, select the Overwrite existing user<\/em> checkbox.<\/p>\n<\/li>\n

            • \n

              Click Restore<\/em>.<\/p>\n<\/li>\n<\/ol>\n

              After you click Restore<\/em>, the Account Restore<\/em> interface will appear.<\/p>\n

              Warnings about the Restricted Restore feature<\/h3>\n
              \n
              Warning:<\/div>\n
              \n

              This feature is experimental<\/strong>. Do not<\/strong> consider it an effective security control. Exercise extreme<\/strong> caution when using the Restricted Restore<\/em> feature.<\/p>\n<\/p><\/div>\n<\/div>\n

              If you use the Restricted Restore<\/em> feature, be advised that:<\/p>\n

                \n
              • When you restore an account with this feature, the system may leave behind unnecessary account data. This can cause conflicts and leave the account in a broken state. You must remove the account and then restore it without<\/strong> using the Restricted Restore<\/em> feature.<\/li>\n
              • This feature will not<\/strong> restore parked (aliased) or addon domains.<\/li>\n
              • This feature only<\/strong> allows restored accounts to use noshell<\/code> or jailshell<\/code> environments. If the restored account uses another shell, the system will set the account to use noshell<\/code> environment.<\/li>\n
              • If you use this feature to restore an account that contains PostgreSQL\u00ae databases, the target server must<\/strong> use PostgreSQL version 8.4 or newer.<\/li>\n<\/ul>\n

                Compatibility issues<\/h2>\n

                Because of changes to the backup system and other system features (for example, Horde), there are several compatibility issues in the restoration process.<\/p>\n

                PostgreSQL database passwords<\/h3>\n

                In cPanel & WHM version 11.42 and later, the system restores PostgreSQL databases to the account, but does not<\/strong> restore the user\u2019s password. This action locks the user out of the databases.<\/p>\n

                The next time the user manages a database with the phpPgAdmin program, the system refreshes the user\u2019s privileges and restores their access.<\/p>\n

                Horde<\/h3>\n

                You cannot<\/strong> restore Horde data from cPanel & WHM version 11.50 and later to a earlier version of cPanel & WHM version.<\/p>\n

                \n
                Important:<\/div>\n
                \n

                Horde data is not<\/strong> backwards compatible for cPanel and WHM version 11.50 and later.<\/p>\n<\/p><\/div>\n<\/div>\n

                \n
                Note:<\/div>\n
                \n

                In cPanel & WHM version 11.48 or earlier, Horde uses MySQL.<\/p>\n<\/p><\/div>\n<\/div>\n

                Also, backups do not include some global Horde files. For more information, read our Backup Tarball Contents and Guide to Horde Data Behavior documentation.<\/p>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"

                Valid for versions 88 through the latest version Version: 82 88 Overview Warning: We removed this interface in cPanel & WHM version 90. Use WHM\u2019s Transfer or Restore a cPanel Account interface (WHM >> Home >> Transfers >> Transfer or Restore a cPanel Account). For more information, read our cPanel Deprecation Plan documentation. This feature …<\/p>\n","protected":false},"author":1,"featured_media":880,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/879"}],"collection":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/comments?post=879"}],"version-history":[{"count":0,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/879\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media\/880"}],"wp:attachment":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media?parent=879"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/categories?post=879"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/tags?post=879"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}