Questions – How it works / Settings

Hi @mwarbinek,
The reason we break up the backups into so many files is to support the many WordPress hosting environments out there. Many are very restrictive with resources so over the years we have had to add configuration options so that WPBackItUp will continue to work even with the very inexpensive hosting providers. We break each portion of the backup process into small workloads driven by these configuration settings and the result are many small files vs 1 large one.

However, if you have an environment with lots of resources then you can change these configuration settings to minimize the number of files generated. Just keep increasing your settings until you receive an error, then back it down to the previous setting.

Additionally, there are settings that allow you to combine both SQL and zip files into a single file but please note these may not work with hosting providers that severely limit memory and processing time.

As for the root files, wp-config and .htaccess. These are very specific to each install so we don’t restore them. I suppose we could back them up for you for reference and manual installs but if we were to replace these files during a one-click restore then its quite possible your site would cease to function, so we do not replace these files currently.

Hope that helps and let me know if you have any additional questions!
Chris

Thanks for the reply.

“db” vs “sql”
You answered Questions 1-3, but as it seems, no clear answer to Question 4 about the SQL database file which shows the extension as “db”.

How is someone to use a “db” file to upload to SQL and restore the SQL database?

Root Files
Ah, yes, both files “htaccess” and “wp-config” contents are “specific” to the WordPress install, that is the point. To not restore these means the recovery of the “specific” WordPress website fails because it cannot access the database.

I have no idea why you would say restoring those files would cause the WordPress site to fail when it is those very files WordPress depends on to give access to the website and connect to its database. To replace “wp-config” with a default copy from a new WordPress install would cause the site to fail because it does not contain the crucial information as stated.

I have migrated and restored many WordPress websites and without those 2 files, the websites would fail.

So your answer about htaccess and wp-config is confusing. The only time that I can see where one does not need to restore htaccess or wp-config is when they are still intact (uncorrupted) and only the rest of the site needs restoration.

• This reply was modified 6 years, 8 months ago by mwarbinek. Reason: added info

Hi again @mwarbinek,
I am not sure I am following your issue with the .db file. If you open it up you should see all the SQL needed to restore your database. If you are unable to upload it because of the extension then try renaming the extension to .sql. If there is an issue with the SQL statements contained in the file then let me know.

My comments about the wp-config.php and .htaccess were based on my assumption that you are trying to migrate your site to a new host. Many of my customers use WPBackItUp to move their site to a new host so I assumed that’s what you were doing. Replacing a wp-config.php and .htaccess files when moving from one host to another would be a bad idea. But if you are restoring your site on the same host then you are correct, replacing the .htaccess and wp-config.php should be fine.

I don’t include them in the backup now but could add them in the next release if you would like. I actually had another request for this recently so was planning to add it anyway.

Hope that helps!
Chris

“db” vs sql file

I was about to ask, since you mention it now. The database file has the extension of “db”. If I change that extension to “sql”, is the file properly formatted and will the SQL database accept it for an upload?

htaccess & wp-config files
To migrate a website with a database means the database username and password are already in the “wp-config” file. To migrate from one server to the next and get the website up, does require the wp-config file from the original install, if a person uses the same database name and password.

I have done it many times, manually. I have migrated the entire WordPress install, root files and all and database. Sometimes there is no need to change core URL’s in the WordPress install so long as the domain URL remains the same (ie: switching host services). If it is changed, then the main domain URL’s require manual changing to the new domain URL’s. – but the original wp-config with its original settings within it, remain the same so long as the database name and passwords are also the same.

For that scenario, the wp-config file is needed.

Moving a WordPress website can be done in various ways, which you know, I have described one way, which is how I have done it before.

To include the root files in the next update version? – sure, you can include it as an option. Otherwise, for me, I can easily download it via FTP and insert it into a ZIP file.

htaccess – Mmm, it is the same no matter where you go, and it can hold special settings that were used in a previous website which can be used again, but the person needs to know how to use it when migrating that. I have done that before too.

Thanks