Support

I would like to note that the restoration CAN NOT BE negatively affected by archive splitting. Kickstart automatically detects the backup archive parts and uses them when restoring a backup archive. In fact, if the parts are missing or corrupt it cannot proceed with the extraction.

If you think that your problem is that you "can not extract" the .j01 etc files please watch our video tutorials; you are not meant to "extract" these files separately. They are parts of the backup archive. They need to all be present when you run Kickstart. Kicsktart will only show you the .jpa, .jps or .zip file (the last part of the backup archive).

If you have a different restoration issue please file a new ticket in the Site Restoration category explaining what is going on. Ideally, give us screenshots of the error messages you are receiving.

If you really want to change the backup configuration to not create multiple parts, yes, of course it's possible and it's very well documented. You can go to the Configuration page and set the Part Size for Split Archives to 0.

! ! ! W A R N I N G ! ! ! WE VERY STRONGLY ADVISE YOU DO NOT TRY TO DISABLE ARCHIVE SPLITTING.

If your total backup size is over 2147483647 bytes (2GB minus one byte) disabling split archives will cause backup or restoration failures in many cases. This has to do with the way PHP works and how it internally addresses files.

Even if your backup is smaller than 2GB you may need to use part sizes smaller than that, for example in any of the following cases:

• Your host has a limit on the maximum size per file created by PHP scripts. This is rare nowadays and the Configuration Wizard detects it.
• You are uploading your backup archive files to a remote storage that has a per-file size limit. For example, on Amazon S3 this is 5 GB in most cases.
• You are uploading your backup archive files to a remote storage and you are using the backend backup, frontend backup or JSON API backup method. If your file is too large and the remote storage engine does not support chunked uploads (or you have disabled them) you will end up with a timeout which will prevent the backup from running. Please consult our documentation for further information on why this happens and whether your remote storage supports chunked uploads.
• You are uploading your backup archive files to a remote storage as soon as each part is complete because your local storage does not have enough space to hold the backup in its entirety. This case should be self-explanatory. If your backup part size is larger than a third of the available disk space you may run out of disk space while taking a backup causing your site and your backup to fail.