Support

Akeeba Backup for WordPress

#32119 – Test backup file

Posted in ‘Akeeba Backup for WordPress’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Wednesday, 11 December 2019 10:52 CST
jk15060
First of all, I want to thank Nicolas and his group for creating Akeeba Backup/Admin Tools for WordPress! Yay!

I have a hosting environment on Siteground that has multiple "addon" domains. I want to backup each website (addon domain), including its own DB, to Google Drive. So far, I have all this working at the moment which is fantastic. I have even figured out how to rename those archive files before they get uploaded to Google.

So the root domain for my hosting account is for TechnoToolkit.com. I didn't know if there was a different variable for [HOST], so I simply used TravelTrailerFun in place of [HOST] for the filename. That worked great too.

My question is simple. Aside from restoring the successful backup, is there any way to determine if the backup is valid and includes the proper configurations; files, folders, etc? I did tick the box to include an "integrity test". Any way to verify the backup file other than a restore? It's configuring the different DBs for the different addon domains. I want to make sure it's configured correctly. Restore?

Thanks y'all!
Janis

Custom Fields

WordPress version (in x.y.z format) 5.3
PHP version (in x.y.z format) 7.1
Akeeba Backup version (x.y.z format) 7.0.0b
 
Thursday, 12 December 2019 01:23 CST
nicholas
Regarding the backup naming what you did is correct. Please keep in mind that using Akeeba Backup for Joomla to backup other sites should only be done when the other sites are also Joomla. If you have any WordPress sites there it's best if you install Akeeba Backup for WordPress on them. Otherwise they will only be possible to restore on the same server and add-on domain you backed them up from.

Regarding full backup testing, yes, it is possible. The way to test that is to automatically restore the site on a server and run some automated tests on select pages, making sure they include some text which would mean that the site is restored correctly.

If you're open to paying money for that, BackupMonkey does exactly that actually using our tools in the way that I'm about to explain below. Please note that BackupMonkey is not affiliated with Akeeba Ltd in any way and we do not get any kind of commission or compensation when you use their services.

Otherwise you need to write your own automation. Akeeba UNiTE can handle automatic site restoration and, as I said, it's what these other guys are using for their service. You can then either use something as simple as cURL piping to grep or something as powerful as Selenium to check if select URLs on the restored site contain the expected text. Any failure in restoration or the text tests will tell you that something's gone wrong with the backup.


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Tuesday, 17 December 2019 09:29 CST
jk15060
Hey Nicholas!
Hope this finds you well. :-)

What you describe above, is exactly what i'm doing. My root domain runs WP, and the backups of the addon domains are also running WP. Will I still need to install the Akeeba Backup for WP to ALL addon domains? Seems redundant, but if that's what I must do, then I'll do it.

Not sure about the automation piece. Was more curious about backing up addon domains, also running WP like the root domain, from the root domain. I was just wondering if installing Akeeba Backup to all addon domains was necessary. Sounds like it is.

I'll try restoring backups to see how the addon domains' backup file works having been run from the root domain.

Thanks Nicholas!
Janis
 
Wednesday, 18 December 2019 01:21 CST
nicholas
I just want to clarify an assumption I made. When you say “add-on domains” I understand that you mean separate, full installations of WordPress in different directories, one for each add-on domain. In this case, yes, you need to install Akeeba Backup for WordPress on each different domain. Testing the backups means restoring each individual backup by itself and making sure it works. As far as Akeeba Backup and the process of restoring and testing sites go there is no difference to single site backup.

Another way to implement this is with a single WordPress multi-site installation where instead of sub-directory / sub-domain access for each blog in the network you’ve set up its own domain. In this case you do NOT need to (and really can not) install Akeeba Backup on each different blog on the network since Akeeba Backup for WordPress is only accessible from the Network Administration panel. In this case backing up your sites backs up everything. Restoring it to a set of different domains is possible and tested (it’s part of our automated WordPress restoration tests). In this case, however, you need to either use a live server with multiple (sub)domains attached to it or set up your local server to respond to multiple domains. Both of these are outside the scope of our support.

If you mean something completely different please clarify.


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



Tuesday, 14 January 2020 09:13 CST
jk15060
That's all I needed, Nicholas. You are correct - I have a domain running WordPress and 5 addon domains that also run WordPress. I was, indeed, trying to reduce the amount of space by only installing on the root domain of my hosting account, in hopes of using that single installation of Akeeba Backup to backup all the addon domains.

Because I did not install WordPress Multi-site, it sounds like the only way to install Akeeba one time and backup all the additional websites.

Thank you for your time and very helpful information.

Janis
 
Wednesday, 15 January 2020 01:22 CST
nicholas
You're welcome!


Nicholas K. Dionysopoulos

Lead Developer and Director



🇬🇷Greek: native

🇬🇧English: excellent

🇫🇷French: basic



Please keep in mind my timezone and cultural differences when reading my replies. Thank you!



This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!