Troubleshooting | WPvivid Plugins Documentation https://docs.wpvivid.com WPvivid Plugins Knowledge Base Thu, 23 Oct 2025 14:39:55 +0000 en-US hourly 1 https://wordpress.org/?v=6.9.4 Backup error: An exception has occurred. class:Google_Service_Exception;msg:{ \”error\”: { \”errors\”: [ { \”domain\”: \”global\”, \”reason\”: \”storageQuotaExceeded\”, \”message\”: \”The user\’s Drive storage quota has been exceeded.\” } ] https://docs.wpvivid.com/backup-error-google_service-error-storagequotaexceeded-message-users-drive-storage-quota-has-been-exceeded.html https://docs.wpvivid.com/backup-error-google_service-error-storagequotaexceeded-message-users-drive-storage-quota-has-been-exceeded.html#respond Tue, 21 Jun 2022 03:27:02 +0000 https://docs.wpvivid.com/?p=1614 The issue occurred due to insufficient Google Drive space. Please free up Google Drive and make sure that there is enough Google Drive space to store backups.

]]> https://docs.wpvivid.com/backup-error-google_service-error-storagequotaexceeded-message-users-drive-storage-quota-has-been-exceeded.html/feed 0 Site migration failed because of the receiving site can’t receive the oversized data chunk during auto-migration. https://docs.wpvivid.com/site-migration-failed-because-of-receiving-site-cant-receive-the-oversized-data-chunk-during-auto-migration.html https://docs.wpvivid.com/site-migration-failed-because-of-receiving-site-cant-receive-the-oversized-data-chunk-during-auto-migration.html#respond Tue, 21 Jun 2022 03:12:36 +0000 https://docs.wpvivid.com/?p=1612 In this case, go to WordPress admin dashboard of target site > WPvivid plugin > Settings > Advanced settings and decrease the value of ‘Chunk size’ to 512 KB and save changes. Then perform an auto-migration task again.

Alternatively, you can migrate your WordPress site by using the upload feature:

  1. Create a backup for your source site and download it to your desktop.
  2. Upload the backup to /wp-content/wpvividbackups directory of your target site by using Upload feature, FTP client or cPanel file manager.
  3. Load the uploaded and received backups to display it in backup list and restore it to your target site.

 

 

]]> https://docs.wpvivid.com/site-migration-failed-because-of-receiving-site-cant-receive-the-oversized-data-chunk-during-auto-migration.html/feed 0 Get error Quota limited reached when backing up to Microsoft OneDrive https://docs.wpvivid.com/quota-limited-reached-onedrive.html https://docs.wpvivid.com/quota-limited-reached-onedrive.html#respond Mon, 20 Jun 2022 10:38:05 +0000 https://docs.wpvivid.com/?p=1610 The issue is usually caused by insufficient OneDrive space. Please check your OneDrive space and make sure it is sufficient for storing the backup.

]]> https://docs.wpvivid.com/quota-limited-reached-onedrive.html/feed 0 Get error Failed to add zip files. status string when making a backup https://docs.wpvivid.com/failed-to-add-zip-files-status-string.html https://docs.wpvivid.com/failed-to-add-zip-files-status-string.html#respond Mon, 20 Jun 2022 10:34:02 +0000 https://docs.wpvivid.com/?p=1608 The error ‘Backup the file ends with an error Failed to add zip files. status string’ is usually caused by insufficient disk space.

Please check the disk space. Generally, the free disk space should be at least twice the size of the backup. Also, in shared hosting, the disk space should be shared as well.

]]> https://docs.wpvivid.com/failed-to-add-zip-files-status-string.html/feed 0 Get the error PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature during migration https://docs.wpvivid.com/pclzip_err_bad_format-10-unable-to-find-end-of-central-dir-record-signature.html https://docs.wpvivid.com/pclzip_err_bad_format-10-unable-to-find-end-of-central-dir-record-signature.html#respond Sat, 07 May 2022 09:55:07 +0000 https://docs.wpvivid.com/?p=1598 This error can occur during a restoration or migration process. When the error occurs, our plugin can not unzip your backup. Because the backup is either incomplete or corrupted. This may happened during the process of downloading/transferring the backup file.

A general solution to this error would be:

1. Removing the backup file from backup list of the target site.

2. Check and free up your source/target server disk space. Generally, in order to backup/restore successfully, the available disk space needs to be at least twice the website size.

3. Create a new backup of the source site, upload it to the destination site and restore. Or, upload the backup to the wp-content/wpvividbackups directory of the target site via an FTP client or a file manager, then click the Scan uploaded backups button on WPvivid to display it on the backup list then restore.

]]> https://docs.wpvivid.com/pclzip_err_bad_format-10-unable-to-find-end-of-central-dir-record-signature.html/feed 0 Why do I get the error “cURL error 28: Operation timed out after 10001/30000 milliseconds with 0 out of 0 bytes received” when backing up to pCloud? https://docs.wpvivid.com/curl-error-28-operation-timed-out-after-10001-30000-milliseconds-with-0-out-of-0-bytes-received-when-backing-up-to-pcloud.html https://docs.wpvivid.com/curl-error-28-operation-timed-out-after-10001-30000-milliseconds-with-0-out-of-0-bytes-received-when-backing-up-to-pcloud.html#respond Mon, 28 Feb 2022 15:19:52 +0000 https://docs.wpvivid.com/?p=1513 This error means uploading the backup to pCloud timed out, which is usually caused by a network connection failure between your web hosting server and the cloud storage provider’s server.

The failure can be on either end, for example, an outage of the cloud storage provider, or a connection failure to the cloud storage provider from the web hosting’s server.

Also, from what we see, pCloud is unfortunately still using a very outdated PHP SDK for their API which was released in 2017(the latest PHP version supported at that time was PHP 7.1). This can consequentially cause compatibility issues, for example, the upload timeout issue as discussed in this post.

Based on these,the solutions to this problem would be:

  1. Wait a while,e .g., an hour, then try it again, to make sure that it is not a one-off problem.
  2. If the the error persists, you will want to reach out to your web hosting provider, and let them check the connection to the pCloud server.
]]> https://docs.wpvivid.com/curl-error-28-operation-timed-out-after-10001-30000-milliseconds-with-0-out-of-0-bytes-received-when-backing-up-to-pcloud.html/feed 0 Get ERR_TOO_MANY_REDIRECTS (abc.com has redirected you too many times) when connecting cloud storage https://docs.wpvivid.com/too_many_redirects-when-connecting-cloud-storage.html https://docs.wpvivid.com/too_many_redirects-when-connecting-cloud-storage.html#respond Mon, 14 Feb 2022 16:18:40 +0000 https://docs.wpvivid.com/?p=1506 This error is usually caused by redirect plugins, e.g., Really Simple SSL plugin, on your website which has prevented the redirection to the site.

You can try to temporarily deactivate the redirect plugin, then try it again. Normally the redirect plugin should have some settings to allow this redirection.

]]> https://docs.wpvivid.com/too_many_redirects-when-connecting-cloud-storage.html/feed 0 Restore failed, Error Info:An exception has occurred. class: PDOException;msg: SQLSTATE[42000] https://docs.wpvivid.com/restore-failed-error-an-exception-has-occurred-class-pdoexceptionmsg.html https://docs.wpvivid.com/restore-failed-error-an-exception-has-occurred-class-pdoexceptionmsg.html#respond Mon, 14 Feb 2022 14:56:16 +0000 https://docs.wpvivid.com/?p=1503 The full error message is like:

“Oops, The restoration seems to have encountered a problem:(
Please adjust the advanced settings before restoring and retry. Read more…
Error Info:An exception has occurred. class: PDOException;msg: SQLSTATE[42000]: Syntax error or access violation: 1227 Access denied; you need (at least one of) the SUPER privilege(s) for this operation;code: 42000;line: 334;in_file: /var/www/abc.com/htdocs/wp-content/plugins/wpvivid-backup-pro/addons2/backup_pro/class-wpvivid-restore-db-method-addon.php;”
This is usually a database permission issue with PDO method, and this guide can help fix it.
Or, you can ignore it and use the ‘WPDB’ method to run the restore as shown below:
WPDB Restore WPvivid Backup Pro
]]> https://docs.wpvivid.com/restore-failed-error-an-exception-has-occurred-class-pdoexceptionmsg.html/feed 0 Backup/Migration is slow https://docs.wpvivid.com/backup-migration-is-slow.html https://docs.wpvivid.com/backup-migration-is-slow.html#respond Sat, 22 Jan 2022 16:26:18 +0000 https://docs.wpvivid.com/?p=1494 Here are two main causes of a slow backup process:

1. The disk I/O of the web hosting is slow.

We have noticed that the disk IO of many web hosting is only 1MB/s,  then theoretically backing up a 100MB website would require at least 300s. You can check the disk I/O of your web hosting by asking your web hosting provider or through cPanel.

2. Some server-resources-friendly WPvivid settings are enabled.

These options are designed to boost backup/migration success rate on web hosting with inadequate resources. Therefore, backups would be running slower when they are enabled.

With that being said, you can still try to adjust the WPvivid Settings as suggested in this doc to speed up a backup process.

]]> https://docs.wpvivid.com/backup-migration-is-slow.html/feed 0 Backup size is different from the website size https://docs.wpvivid.com/backup-size-is-different-from-website-size.html https://docs.wpvivid.com/backup-size-is-different-from-website-size.html#respond Mon, 20 Dec 2021 11:01:39 +0000 https://docs.wpvivid.com/?p=1471 During the backup process, our plugin will compress your website data into zip files to save storage space. So it is normal that your website is, for example, 5 GB(the calculation result on WPvivid backup page) while the backup will be only 1GB.

You can verify a backup by downloading it to your computer, then upload it to a test site, restore and see if the test site works as expected.

]]> https://docs.wpvivid.com/backup-size-is-different-from-website-size.html/feed 0