Unable to restore database : zip file too large

Unable to restore database : zip file too large

In oldest versions like 8.0, 8.1. 8.2, 8.3, you may come across restore issues when the backup file is huge (even more than 3 or 4GB). In those cases, this article would be helpful.

Scenario 1:

If you come across this when you are trying to setup UAT environment, then the solution to this would be, to take trimmed backup from PROD server and then try to restore the same in UAT setup. This will have the restore successful. Later you can copy the following folder from PROD to UAT,

Custom, Images, Inline Images and File Attachments under ManageEngine\Servicedesk Plus MSP folder.

Scenario 2:

There may be certain cases say where you do not have UAT and after upgrade failure in PROD, you do not have a trimmed backup or a SQL backup or VM snapshot, but ONLY a full backup which gives you the error mentioned in subject, then, in those cases, you are left with only option i.e. to restore the full backup to get your PROD server up and running. Please refer steps to achieve the same after removing the File Attachments and Inline images which consists of more data.

1. Take a copy of the backup file and store it in a different location. Just for safety so that if there is a trouble in modification, you still have the original backup file.

2. Now, convert the backup file (.Data) by renaming the file as .ZIP.

3. Open a new folder, Unzip the file (Right click->Extract here).

4. Remove the File attachments and Inline images folder and place it outside the new folder. Also, ensure to remove the actual backup file converted as ZIP.

5. Now, copy all the files in the New folder and add them as a Zip file(Copy all files->Right click->7 Zip->Add to New folder.zip)

6. Once the file is zipped, rename it with the original backup file name and change the file extension back to .DATA. Store this in another new folder for easy reference say Modified Backup.

7. Now try restoring the backup from the Modified folder and the restore should work fine now.

8. Login as Administrator and check your data.

9. Once it is fine, copy the Inline images and FileAttachments.zip  to the ManageEngine\Servicedesk Plus MSP folder.

10. Then, ensure to unzip the FileAttachments.zip on to the same location.

If you have any issues, kindly drop an email to sdpmsp@manageengine.com with the steps tried, screenshots of the error message and the Build number which you have issue with.


                  New to ADManager Plus?

                    New to ADSelfService Plus?

                      • Related Articles

                      • How do I restore the backup data?

                        NOTE: For builds > 10.6 While migrating to different database you can use backupdataold.bat / backupdataold.sh. Here backup will be in .data format and this can be restored in across DB platform. While restoring .data file we have to use below ...
                      • How do I convert the database from PGSQL to MSSQL?

                        1. Stop ManageEngine ServiceDeskPlus – MSP service. 2. Take a backup of the existing data and configuration under PGSQL database by following the below steps. Open CMD as an administrator and execute  command to start the data backup. ...
                      • Steps to take PGSQL Dump Backup and Restore

                        PGSQL – DUMP – Backup Procedure : Login to the MSP application server and perform the below steps, 1. Start the application To take Postgres (Psql) Dump : 3. Open a command prompt and navigate into <ServiceDeskPlus-MSP>/pgsql/bin directory. 4. ...
                      • Unable to save Preventive maintenance tasks

                        Issue: Unable to update just one PM task with more than 300 tasks. When tried to save the PM task, it simply throws "User does not have sufficient privilege". Cause: By default we would have restricted for these many tasks added in PM task. We can ...
                      • The transaction log (Servicedesk_log.ldf) for database 'servicedesk' is full

                        There are two methods to fix this issue. Method 1 To fix this issue, we have to detach ServiceDesk database, after detaching we can delete the transaction log ( .LDF log) and attach the ServiceDesk database back. The important part in this process of ...