I did read that BackUp Buddy is experimental for multipress sites, and I wanted some clarification on that line. If someone creates a wordpress site at a subdomain of echosites.com such as myawesomemissiontrip.echosites.comand then wants to 'move' the site from that multisite platform to their own domain name which would (99% surely) NOT be a multisite install such as myawesomemissiontrip.com will Backup Buddy work for that scenario? -moving all links? -menu setting? -hyperlinks within pages?
In other words, the church goes to echosites.com, picks a theme, the hosting is already set up, (kinda like iThemes!) and they start creating their site. Since most churches will already have a site up, they are not going to be willing to take their existing site down as they learn something new like wordpress or their new theme. So they 'sandbox' the theme on a subdomain, and once they've got everything the way they want it, the site gets moved fromsub.echosites.com to their new domain -hopefully w/out losing any settings!
Can this be done w/ Backup Buddy?
Posted 22 July 2013 - 09:59 AM
Posted 23 July 2013 - 09:05 AM
Multisite functionality is experimental with BackupBuddy, so naturally it isn't recommended for live/production sites as standalone sites are preferred on that. But BackupBuddy can export a subsite in a multisite network so that it can be migrated as a standalone site with an importbuddy.php like normal, except for the main site in a network. Anything involving the main site of a network is always a hassle in WordPress Multisite with just how multisite works.
Posted 23 July 2013 - 12:52 PM
Just to clarify
Pardon me for being a dude who likes 'yes' and 'no' answers, I just want to make sure
Posted 23 July 2013 - 02:08 PM
Unfortunately in the world of hosting and WordPress (particularly Multisite) we tend to have to deal with grayscale rather than black & white ;-)
You can export a site from a multisite and migrate it to a new home as a standalone WordPress installation _but_ as Akers mentioned multi-site functionality is experimental (as per the FAQ on the Product Information page here: http://ithemes.com/purchase/backupbuddy/ - "Does BackupBuddy support Multisite?"
Should you choose to go with BackupBuddy I would still caution you on your process of trying to go straight from the site on the multisite to blowing away and replacing any existing (non-WordPress by the sound of it) site. If there has never even been a WordPress installation on the target hosting you may run into problems with the site totally unrelated to whether or not the actual installation migrates correctly or not.
I would strongly recommend that you do a test migration to a subdomain of the target url, e.g., testwp.myawesomemissiontrip.com, in preparation for the migration to the final url. Also consider doing test migrations during the development on the multisite so that you are sure what is being developed will work on the destination server or alternatively do the migration to the test subdomain early after the main choices have been made for the site and then continue the development on the new server under the test subdomain and then when ready to release simply do a migration from the test subdomain to the final domain and this should be the least risky way as it's running on the same server.
Please be aware that I am not trying to specifically discourage you from using BackupBuddy for your multisite exports but just trying to make you aware of the potential for issues and also trying to offer you strategies that can mitigate those issues and risks.
I hope the above is helpful in making your decision and please let us know if you have any additional question or clarification required in this respect, thanks.
"Everything will be all right in the end. If it isn't all right yet then it isn't the end."