Yani

There are no changes to the export window in the latest version.
You will need to perform steps to try to isolate the issue:
1. Try your browser in incognito mode
2. Try a different browser
3. Try to disable plugins one by one and then perform the export

AWS EFS has unique characteristics. It differs from traditional storage. There are difference in how it handles metadata and latency. This sometimes causes compatibility issues when the plugin checks disk space.

The button “I have enough disk space” is added for this particular use case. If the restore/import works fine once you click the button, you are good to go.

No, do not share site access with anyone. It is not permitted and it is also not a good idea to do this.
At this point, I will recommend manually to transfer the media files and use the plugin for for everything else.

Currently, import and restore backup work the same way.
There are some differences when importing a website to a different URL.
For the purposes of restoring a backup, you can safely use import from file.
It asks you to overwrite your files and database because it will use the contents of the backup to replace the site with.
You can expect your site to be the same one as what you backed up after using restore/import process.

Hi there,

It seems like the incorrect URL replacement during export may have caused issues with your links and editing.
When you export, do not use find and replace settings. The plugin will handle the replacements for you.
All you have to do is, export to file.

Try to increase max_input_time to 3000 too. Revert it back after exporting.

Hi Owen,

It sounds like Redis Object Cache from the EasyWP setup is embedded into your exported site, and this is causing the issues when trying to import it into another environment that doesn’t support Redis or doesn’t have it enabled.

Here’s how you can try to resolve this:

1. If possible, before exporting from the EasyWP environment, disable the Redis Object Cache plugin at the WordPress level. You can do this by deactivating any Redis-related plugins, either through the WordPress dashboard or by renaming the Redis plugin folder via FTP.

2. You can also try clearing the Redis cache before taking the export. Some caching data might be persisting in your database, which could be causing the issue on import.

3. If Redis-related entries have been added to your database, you can try to manually search and remove these references via phpMyAdmin. Look for Redis-related keys in the wp_options table, such as wp_cache, and delete or reset these entries.

4. Try importing the site into a local environment where you have control over Redis and can enable/disable it to see if the issue persists. This will help pinpoint if the problem is related to Redis or something else in the setup.

I also experienced similar issue like the OP described. www.ads-software.com would load very slow or not load at all. I had to disable QUIC protocol in the browser to access www.ads-software.com normally.

Hi there,

Since you’re experiencing issues with backup retention, I recommend checking your settings and server policies.

For further assistance with this premium feature, please contact our support team directly, as we aren’t able to provide support for premium products on WordPress forums. You can reach us here: https://servmask.com/contact-support

Thank you for your understanding!

It sounds like you’ve taken some solid steps for the import. With a 4GB file, a few additional adjustments can help ensure a smooth import process:

1. Since you’ve already adjusted your php.ini, double-check the following settings:

• memory_limit
• max_execution_time
• post_max_size

• If not all tables were imported, this is likely because they are not using the $wpdb->prefix defined in wp-config.php. The plugin only exports prefixed tables.
• Manually copying plugins and images, as you’ve done, can be a good approach, especially with larger sites. Just ensure that all paths are correctly set and that permissions are set appropriately on your localhost.
• Check PHP and server error logs for any issues that occurred during the import. This can provide insight if any further adjustments are needed.

• This reply was modified 1 month, 1 week ago by Yani.

Hi Petr,

Thanks for reaching out. Since you’re using the Unlimited and OneDrive Extensions, please contact our support team directly for assistance. We aren’t able to provide support for premium products on the WordPress forums.

Our support team will be happy to help you troubleshoot the issue with the wp_postmeta table and get your backup working correctly. You can reach them here: https://servmask.com/contact-support

Handling a large media library, especially one around 133 GB, can be challenging for backups. Here are a few steps you can try to address the export issue:
1. Ensure that your PHP configuration allows for high memory usage and extended processing time:
– memory_limit Set this to at least 512M or higher.
– max_execution_time Increase to 600 seconds or more.

2. With a large media library, it may help to split the export into smaller parts. Try exporting only the database, themes, and plugins first, then export the media library separately

3. Confirm that there is sufficient storage space on your server to handle the backup process, including temporary files.

4. If the plugin log is unavailable, you can check the server’s main error logs via your hosting control panel (e.g., cPanel, Plesk) or through FTP. Look for recent errors during the export process for clues

5. If possible, consider removing any unneeded media files to reduce the size before creating the backup

Hi there,

To migrate a WordPress instance between Microsoft Azure environments, you can use our Unlimited Extension. This extension removes any upload size limits set by your hosting provider and web configuration, allowing you to migrate larger sites without restrictions.

I recommend reaching out to our support team for detailed guidance: https://servmask.com/contact-support

The issue you’re encountering is quite common when dealing with large backups.

1. Large file operations may exceed default script execution times, leading to timeouts. Increase the max_execution_time in your php.ini file:
max_execution_time = 300 // You may need to increase it further depending on the backup size

2. Ensure that your server configuration supports large file operations. This includes settings in php.ini for upload_max_filesize and post_max_size:

upload_max_filesize = 4096M
post_max_size = 4096M

Adjust these values as necessary to accommodate your backup file size.

3. For handling particularly large backups more efficiently, consider using the Unlimited Extension. This extension enhances the plugin’s capabilities, particularly in terms of handling large file sizes and extending execution times, making it ideal for larger backups like yours.

4. Monitor your server resource usage (CPU, RAM) during the restoration process. Insufficient resources can cause the process to halt unexpectedly.

5. If you continue to encounter issues despite these adjustments, I recommend reaching out to a professional for more personalized assistance.

Please contact our support team via this link: https://servmask.com/contact-support , and they’ll assist you promptly.