nrobertsudp

Hi there,

No, UpdraftPlus doesn’t interact with the cache. I’m uncertain as to whether there is a conflict.
Despite searching our resources I could not find anything related to the scenario you describe.
You could try a conflict test by temporarily disabling the plugin and monitoring for any change.

Best regards,

Nick

Hi Paal,

The backups are actually stored in their component parts which form a backup set.
This means they do need to be downloaded individually when using the interface.
You can download files at the same time but you must initiate each file download.
The Select option only relates to deletion of files, it does not relate to downloads.

Best regards,

Nick

Hi Paal,

Thank you very much, I’m happy to have helped!

The settings confirmation is a good idea, I will pass this on to the developers.
If you do have any difficulties please feel free to contact us, we’re here to help.

Thank you once again, and have a great day too!

Best regards,

Nick

Hi Paal,

Thank you for clarifying.

In the Settings tab have you configured your file and database backup schedules?
Once you define your schedules you will need to click the ‘Save Changes’ button.

If you haven’t set up a remote storage location the backups will be stored locally.
To confirm the schedules are set you could use WP Crontrol to review the events.

You can install WP Crontrol from the Advanced Tools >> Site Information section.
If you view Cron Events the file and database scheduled events should be shown.

Best regards,

Nick

Hi there,

The backup settings will be used for both the manual and scheduled backups.
You would simply set the schedule and the backups will be stored as defined.

You may want to check your retention settings allow for backups to be stored.
Meaning the retention limit should be considered in relation to your schedule.

Best regards,

Nick

Hi there,

In the process of creating a backup a temporary backup set is created on the local host.
Once these files have been transferred to remote storage they are deleted from the host.

In cases where the option to delete local backups is not selected they remain in the folder.
The updraft folder is also used when users select to store their backups on the local host.

In summary, this is not a fault with the plugin. It is simply a part of the backup processing.
You can find more information on the topic of how the space is being used on this page.

Best regards,

Nick

Hi there,

The problem is not with UpdraftPlus, it is related to the issues with your installation.
The two sets are the cause of the problem and UpdraftPlus did not create these sets.

It’s likely there weren’t duplicates in those previous staging site backups you mention.
The premium plugin offers the option to exclude any specified tables from the backup.

Best regards,

Nick

Hi there,

When you restore from within your new WordPress installation the database will be restored to the database which pertains to that installation. In this case, the new database.

Best regards,

Nick

Hi there,

Thank you for the log file.

Looking at the log file there are duplicate database tables with different prefixes (examples):

4772.472 (8) Table b6x5H11E6_yoast_primary_term: corresponding file already exists; moving on
4772.473 (8) Table b6x5H11E6_yoast_seo_links: corresponding file already exists; moving on
4772.473 (8) Table b6x5H11E6_yoast_seo_meta: corresponding file already exists; moving on

These tables have been backed up successfully. You then have the other tables (examples):

4772.549 (8) Skipping table (lacks our prefix (b6x5H11E6_)): wpstg0_yoast_primary_term
4772.549 (8) Skipping table (lacks our prefix (b6x5H11E6_)): wpstg0_yoast_seo_links
4772.550 (8) Skipping table (lacks our prefix (b6x5H11E6_)): wpstg0_yoast_seo_meta

So the presence of two sets of database tables is causing the problems you’re experiencing.
UpdraftPlus would not delete database tables, this is not a part of the plugin’s functionality.

You could try replacing the database prefix in the wp-config file: $table_prefix = ‘qny3n_’;
I offer this advice with a note of caution as I can’t be certain the wpstg0 tables are complete.

However, you would still need to delete the old database tables to avoid the same problem.

Best regards,

Nick

Hi there,

Your review is incorrect and misleading. The feature is available in the Premium plugin version.

As I pointed out to you in your support request:

The version number of your plugin seems to indicate you are using an old paid version.
The feature you’re referring to still exists in the paid version but is not in the free version.

https://www.ads-software.com/support/topic/no-label-notes-option-of-backup-name/

Best regards,

Nick

Hi there,

Thank you, I’m very happy to have helped!

Best regards,

Nick

Hi there,

With the free plugin version there is no option to save tables in the WordPress core.
Your log file is confirming all the tables in your database have been saved correctly.

Best regards,

Nick

Hi there,

This could well be due to a plugin conflict, you would need to perform a conflict test.
You could first try disabling only the WP Staging plugin and then running your backup.

Ideally, temporarily disabling all plugins and using a default theme is the best method.
If the issue persists after this please provide the log file using PasteBin or similar means.

Best regards,

Nick

Hi there,

The last line of the log files indicates the backup completed correctly:
0410.121 (0) The backup succeeded and is now complete

Best regards,

Nick

Hi there,

The version number of your plugin seems to indicate you are using an old paid version.
The feature you’re referring to still exists in the paid version but is not in the free version.

Best regards,

Nick