Welcome to the forum:
Our moderators actively respond to forum support requests during normal business hours which are Monday-Friday, 8am - 5pm Central Standard Time, typically within one business day. Although some moderators choose to work during the weekends, we can not guarantee immediate attention to your requests. Thanks for understanding.
What is included with support:
Premium support includes theme/plugin issues such as: bugs encountered under normal operation, how to use basic features, basic WordPress help, and basic help with customization (meaning we point you to resources and will help in more depth as time allows). More information.
Monday, May 25 2015 is Memorial Day. Please note that the iThemes offices are closed during National Holidays.
Support will resume on Tuesday May 26.
BackupBuddy - Are Multi-Network and domain mapping supported?
Posted 07 September 2011 - 02:10 PM
We are using one Web server and MySQL server as a development environment, where I am constantly testing plugins, themes, etc.
We then have a second set up similar to the development environment that we plan to use for staging; and a third set up that will be used for production.
We intend to use the staging server (which is virtually identical to the production environment, with the exception of the URLs, the database host name and the MySQL user information) to test our code from the development server before pushing it into the production environment.
We will be regularly pushing the entire WordPress installation from production to staging (in order to make sure the two are synced), and then back to production from staging after the changes are tested. We will occasionally push the entire install from production to development (again, to make sure they're synced).
Does BackupBuddy seem like a good solution to this, or should we look elsewhere? Will BackupBuddy be able to handle the mapped domains that are used throughout the installation? Does BackupBuddy handle URLs within serialized information in the database when migrating? Thank you.
Posted 07 September 2011 - 03:52 PM
Thanks for posting this, and welcometo the forums! :)
If I understand your question correctly, yes, BackupBuddy IS/will be a good soluton to this as backupbuddy handles both Multisites and domain mapping (since domain mapping is a plugin). Remember, however, that the new Multisite features are currently still in BETA and will keep improving and developing.
Also, if you have a huge network of sites that take up a lot of memory or space on your server, make sure your server will have enough resources like memory, max execution time and related things to handle such kind of a backup/migration/restore task on a regular basis.
Please let me know if that helps, and if you've any other questions!
Posted 08 September 2011 - 02:51 PM
The main area in which we'd be using this does not have a huge network (there are currently about 30-40 networks setup, and each of those networks has 1-5 sites set up within - for a total of about 150-200 "blogs" within the database). However, each of our servers (development, staging and production) are in their own virtual machines (with the database servers for each on their own VMs, as well) with plenty of resources available to all of them. We do have another system that currently has around 5,500 blogs in it (which also uses domain mapping in places); but we most likely wouldn't be using BackupBuddy nearly as often there as we would for our website.
Our main concern, obviously, is simply being able to basically copy the setup and content from our staging server and push it to our production server efficiently. Since the URLs used on our staging server are different than the URLs used on our production server, we can't simply do a full copy; we'll need something (possibly BackupBuddy) to go into the backup and change the URLs everywhere they occur (including within serialized arrays - since the URLs are not the same length between servers, the length keys need to be updated, which means we can't do a simple search & replace).
Again, thanks for your response.