<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="http://ithemes.com/codex/skins/common/feed.css?303"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://ithemes.com/codex/api.php?action=feedcontributions&amp;user=Dustin&amp;feedformat=atom</id>
		<title>IThemes Codex - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="http://ithemes.com/codex/api.php?action=feedcontributions&amp;user=Dustin&amp;feedformat=atom"/>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/Special:Contributions/Dustin"/>
		<updated>2013-05-26T07:39:12Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.18.1</generator>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy</id>
		<title>BackupBuddy</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy"/>
				<updated>2013-04-19T01:34:13Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: /* Server Recommendations (full functionality) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* '''New to BackupBuddy?''' Check out the [[BackupBuddy:_Getting_Started|Getting Started]] page.&lt;br /&gt;
* '''Problems?''' Check out the [[BackupBuddy:_Frequent_Support_Issues|Frequently Seen Support Issues]] page.&lt;br /&gt;
* '''Need hosting?''' ''Hostgator Coupons'' are available to BackupBuddy customers [http://ithemes.com/forum/index.php?/topic/14012-hostgator-coupons-for-our-community/ here].&lt;br /&gt;
* '''[http://ithemes.com/codex/page/BackupBuddy_Multisite BackupBuddy Multisite Codex]'''&lt;br /&gt;
&lt;br /&gt;
=Tutorials=&lt;br /&gt;
&lt;br /&gt;
===Training Videos===&lt;br /&gt;
For video training including walkthroughs &amp;amp; tutorials please see http://ithemes.com/backupbuddy-training/&lt;br /&gt;
&lt;br /&gt;
===Installing BackupBuddy===&lt;br /&gt;
&lt;br /&gt;
Check out the [[Installing BackupBuddy]] section to see how BackupBuddy can be uploaded and activated on Single sites or Multisite networks or Multisite sites.&lt;br /&gt;
&lt;br /&gt;
===Getting Started===&lt;br /&gt;
Check out the [[BackupBuddy:_Getting_Started|Getting Started]] page to backup your Single sites or Multisite networks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Restore or Migrate===&lt;br /&gt;
Learn to [[BackupBuddy:_ImportBuddy|Restore or Migrate]] your Single sites or Multisite networks with the latest importbuddy.php.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Settings Explained===&lt;br /&gt;
Get in depth information about the various [[BackupBuddy:_Settings|Settings]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Developing Locally===&lt;br /&gt;
See the [[BackupBuddy:_Local_Development|Develop Sites Locally]] page for developing WordPress sites locally on your own computer using something like XAMPP or MAMP.  You can then migrate them to your web host.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Using your HOSTS file for seamless migrations===&lt;br /&gt;
Here's one tutorial that may help:&lt;br /&gt;
http://www.bleepingcomputer.com/tutorials/hosts-files-explained/&lt;br /&gt;
&lt;br /&gt;
The HOSTS file allows you to basically just update the DNS settings for the site ONLY FOR YOU on your computer.  This lets you try out what would happen if you updated the DNS settings for everyone but only locally. The goal is basically to make your own computer think that your website is reached by going to the new IP address instead of the IP address everyone else on the internet goes to by visiting your URL.  This allows you to access the new site before officially pointing everyone on the internet to the new server.&lt;br /&gt;
&lt;br /&gt;
The procedure is basically:&lt;br /&gt;
* Update your computer's HOSTS file to point the new destination server IP address. Leave DNS settings as-is so that everyone else online will continue to see the normal site.&lt;br /&gt;
* Connect to your site.  When you connect to it you should end up on the new server if you've set up your HOSTS file properly. Upload ImportBuddy, your backup file, etc to it.&lt;br /&gt;
* Restore normally.  Verify that it all works properly.&lt;br /&gt;
* Assuming everything is good to go you can then change the DNS so that everyone else online gets switched over to accessing the new server. This results in a seamless launch with no down-time.  Make sure to re-edit your HOSTS file to remove the bypass so you don't forget.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Specifications=&lt;br /&gt;
Server configuration is a very complex topic and varies wildly between hosts, server operating systems, and even the personal preference of the server administrator. Below are the bare minimum requirements for the plugin along with the recommended setup to get the most out of this plugin. You may use [[ServerBuddy]] to help you determine how your server compares to our minimum requirements &amp;amp; recommendations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Server Recommendations (full functionality)===&lt;br /&gt;
* PHP 5.2+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires PHP 5.2+]&lt;br /&gt;
* mySQL 5.x+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires mySQL 5.0.15+]&lt;br /&gt;
** For best results, use MySQL 5.1+&lt;br /&gt;
* WordPress 3.3+ &lt;br /&gt;
* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.&lt;br /&gt;
** Backups will be stored in /wp-content/uploads/backupbuddy_backups/&lt;br /&gt;
** Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)&lt;br /&gt;
* Free disk space equal to or greater than the entire size of your site once compressed.&lt;br /&gt;
** SuPHP or environment so that file operations/zip run as user to prevent permissions issues.&lt;br /&gt;
** PHP exec() function enabled&lt;br /&gt;
** PHP ZipArchive class installed&lt;br /&gt;
* Linux (Apache; Some Litespeed server setups have broken performance inhibiting BackupBuddy):&lt;br /&gt;
** Command-line zip installed and accessible via exec().&lt;br /&gt;
* Windows (only supported for local development via Apache; IIS is not officially supported):&lt;br /&gt;
** Windows zip executable (available [http://pluginbuddy.com/wp-content/uploads/2010/05/backupbuddy_windows_unzip.zip here])&lt;br /&gt;
*** You must have the ability to configure your server to allow execution of this zip.exe file for it to function.&lt;br /&gt;
*** File permissions must also be set to allow access and execution of the zip executable.&lt;br /&gt;
* wp-config.php file must be in WordPress installation directory OR (starting with BackupBuddy v3.0) in the parent directory.&lt;br /&gt;
&lt;br /&gt;
===Minimum Server Requirements (reduced functionality)===&lt;br /&gt;
'' NOTE: Some features of BackupBuddy will be unavailable or limited if running on minimum requirements without recommendations. Large sites may not be able to be backed up with these minimum features.'''&lt;br /&gt;
* PHP 5.2+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires PHP 5.2+]&lt;br /&gt;
* mySQL 5.x+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires mySQL 5.0.15+]&lt;br /&gt;
* WordPress 3.2+&lt;br /&gt;
** We are trying to maintain bare minimum backup functionality for legacy versions as far back as WordPress v2.6 (though it's not pretty nor guaranteed to work perfectly at this time; we recommend only performing backups &amp;amp; direct restores for older versions and use it for safety while upgrading to the latest WordPress).&lt;br /&gt;
* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.&lt;br /&gt;
* BackupBuddy requires the uploads directory to be in the standard WordPress location.&lt;br /&gt;
** Backups will be stored in /wp-content/uploads/backupbuddy_backups/&lt;br /&gt;
** Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)&lt;br /&gt;
* Free disk space equal to or greater than the entire size of your site once compressed.&lt;br /&gt;
* wp-config.php file must be in WordPress installation directory OR (starting with BackupBuddy v3.0) in the parent directory.&lt;br /&gt;
&lt;br /&gt;
===Host Compatibility===&lt;br /&gt;
Compare various [[BackupBuddy:_Hosts|Hosts &amp;amp; Hosting Environments]] to see how your host/potential host compares.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Misc. Information===&lt;br /&gt;
Find out some [[BackupBuddy:_Misc_Information|Miscellaneous Information]] about BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
	&lt;br /&gt;
=Troubleshooting=&lt;br /&gt;
&lt;br /&gt;
===Frequently Seen Support Issues===&lt;br /&gt;
''Problems?'' We have compiled a list of issues and solutions to many problems that we have seen encountered before. [[BackupBuddy:_Frequent_Support_Issues|Frequently Seen Support Issues]] to attempt to narrow down your problem and find a solution.&lt;br /&gt;
&lt;br /&gt;
===BackupBuddy: Error Codes===&lt;br /&gt;
Receive an error code? Check out the [[BackupBuddy:_Error_Codes|Error Codes]] page for explanations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Manual Migration===&lt;br /&gt;
Import fails on file extraction? Learn how to perform a [[BackupBuddy:_Manual_Migration|Manual Migration]] ... it's easier than you'd think!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
&lt;br /&gt;
'''Tools'''&lt;br /&gt;
&lt;br /&gt;
* [http://ithemes.com/codex/page/File:Zip_test.zip Manually test command line zip functionality]&lt;br /&gt;
&lt;br /&gt;
=Multisite=&lt;br /&gt;
&lt;br /&gt;
BackupBuddy supports the following Multisite functionality:&lt;br /&gt;
* Export a Multisite subsite to standalone&lt;br /&gt;
* Import an exported Multisite subsite into an existing Network&lt;br /&gt;
* Import a standalone WordPress site into an existing Network&lt;br /&gt;
* Backup entire Network (backup/restore only; no migration to new URL)&lt;br /&gt;
* Restore entire Network WITHOUT URL migration for subsites within if migrating to a new URL (URL changes have limitations. Please see Multisite page for details)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://ithemes.com/codex/page/BackupBuddy_Multisite Check out the BackupBuddy Multisite Codex] and [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite Beta Today!]&lt;br /&gt;
&lt;br /&gt;
BETA indicates that Multisite functionality has known issues and is not reccomended for production use except at your own risk.  We do NOT guarantee its functionality or provide guaranteed support for beta products.&lt;br /&gt;
&lt;br /&gt;
'''Links'''&lt;br /&gt;
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]&lt;br /&gt;
# [http://ithemes.com/codex/page/BackupBuddy_Multisite BackupBuddy Multisite Codex]&lt;br /&gt;
# [http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy beta Multisite support announcement]&lt;br /&gt;
# [http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ BackupBuddy beta Multisite key points everyone is raving about!] &lt;br /&gt;
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]&lt;br /&gt;
# [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
# [http://pluginbuddy.com/support/ Support Forums]&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy</id>
		<title>BackupBuddy</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy"/>
				<updated>2013-04-11T02:06:59Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* '''New to BackupBuddy?''' Check out the [[BackupBuddy:_Getting_Started|Getting Started]] page.&lt;br /&gt;
* '''Problems?''' Check out the [[BackupBuddy:_Frequent_Support_Issues|Frequently Seen Support Issues]] page.&lt;br /&gt;
* '''Need hosting?''' ''Hostgator Coupons'' are available to BackupBuddy customers [http://ithemes.com/forum/index.php?/topic/14012-hostgator-coupons-for-our-community/ here].&lt;br /&gt;
* '''[http://ithemes.com/codex/page/BackupBuddy_Multisite BackupBuddy Multisite Codex]'''&lt;br /&gt;
&lt;br /&gt;
=Tutorials=&lt;br /&gt;
&lt;br /&gt;
===Training Videos===&lt;br /&gt;
For video training including walkthroughs &amp;amp; tutorials please see http://ithemes.com/backupbuddy-training/&lt;br /&gt;
&lt;br /&gt;
===Installing BackupBuddy===&lt;br /&gt;
&lt;br /&gt;
Check out the [[Installing BackupBuddy]] section to see how BackupBuddy can be uploaded and activated on Single sites or Multisite networks or Multisite sites.&lt;br /&gt;
&lt;br /&gt;
===Getting Started===&lt;br /&gt;
Check out the [[BackupBuddy:_Getting_Started|Getting Started]] page to backup your Single sites or Multisite networks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Restore or Migrate===&lt;br /&gt;
Learn to [[BackupBuddy:_ImportBuddy|Restore or Migrate]] your Single sites or Multisite networks with the latest importbuddy.php.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Settings Explained===&lt;br /&gt;
Get in depth information about the various [[BackupBuddy:_Settings|Settings]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Developing Locally===&lt;br /&gt;
See the [[BackupBuddy:_Local_Development|Develop Sites Locally]] page for developing WordPress sites locally on your own computer using something like XAMPP or MAMP.  You can then migrate them to your web host.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Using your HOSTS file for seamless migrations===&lt;br /&gt;
Here's one tutorial that may help:&lt;br /&gt;
http://www.bleepingcomputer.com/tutorials/hosts-files-explained/&lt;br /&gt;
&lt;br /&gt;
The HOSTS file allows you to basically just update the DNS settings for the site ONLY FOR YOU on your computer.  This lets you try out what would happen if you updated the DNS settings for everyone but only locally. The goal is basically to make your own computer think that your website is reached by going to the new IP address instead of the IP address everyone else on the internet goes to by visiting your URL.  This allows you to access the new site before officially pointing everyone on the internet to the new server.&lt;br /&gt;
&lt;br /&gt;
The procedure is basically:&lt;br /&gt;
* Update your computer's HOSTS file to point the new destination server IP address. Leave DNS settings as-is so that everyone else online will continue to see the normal site.&lt;br /&gt;
* Connect to your site.  When you connect to it you should end up on the new server if you've set up your HOSTS file properly. Upload ImportBuddy, your backup file, etc to it.&lt;br /&gt;
* Restore normally.  Verify that it all works properly.&lt;br /&gt;
* Assuming everything is good to go you can then change the DNS so that everyone else online gets switched over to accessing the new server. This results in a seamless launch with no down-time.  Make sure to re-edit your HOSTS file to remove the bypass so you don't forget.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Specifications=&lt;br /&gt;
Server configuration is a very complex topic and varies wildly between hosts, server operating systems, and even the personal preference of the server administrator. Below are the bare minimum requirements for the plugin along with the recommended setup to get the most out of this plugin. You may use [[ServerBuddy]] to help you determine how your server compares to our minimum requirements &amp;amp; recommendations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Server Recommendations (full functionality)===&lt;br /&gt;
* PHP 5.2+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires PHP 5.2+]&lt;br /&gt;
* mySQL 5.x+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires mySQL 5.0.15+]&lt;br /&gt;
** For best results, use MySQL 5.1+&lt;br /&gt;
* WordPress 3.3+ &lt;br /&gt;
* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.&lt;br /&gt;
** Backups will be stored in /wp-content/uploads/backupbuddy_backups/&lt;br /&gt;
** Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)&lt;br /&gt;
* Free disk space equal to or greater than the entire size of your site once compressed.&lt;br /&gt;
** SuPHP or environment so that file operations/zip run as user to prevent permissions issues.&lt;br /&gt;
** PHP exec() function enabled&lt;br /&gt;
** PHP ZipArchive class installed&lt;br /&gt;
* Linux (Apache):&lt;br /&gt;
** Command-line zip installed and accessible via exec().&lt;br /&gt;
* Windows (only supported for local development via Apache; IIS is not officially supported):&lt;br /&gt;
** Windows zip executable (available [http://pluginbuddy.com/wp-content/uploads/2010/05/backupbuddy_windows_unzip.zip here])&lt;br /&gt;
*** You must have the ability to configure your server to allow execution of this zip.exe file for it to function.&lt;br /&gt;
*** File permissions must also be set to allow access and execution of the zip executable.&lt;br /&gt;
* wp-config.php file must be in WordPress installation directory OR (starting with BackupBuddy v3.0) in the parent directory.&lt;br /&gt;
&lt;br /&gt;
===Minimum Server Requirements (reduced functionality)===&lt;br /&gt;
'' NOTE: Some features of BackupBuddy will be unavailable or limited if running on minimum requirements without recommendations. Large sites may not be able to be backed up with these minimum features.'''&lt;br /&gt;
* PHP 5.2+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires PHP 5.2+]&lt;br /&gt;
* mySQL 5.x+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires mySQL 5.0.15+]&lt;br /&gt;
* WordPress 3.2+&lt;br /&gt;
** We are trying to maintain bare minimum backup functionality for legacy versions as far back as WordPress v2.6 (though it's not pretty nor guaranteed to work perfectly at this time; we recommend only performing backups &amp;amp; direct restores for older versions and use it for safety while upgrading to the latest WordPress).&lt;br /&gt;
* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.&lt;br /&gt;
* BackupBuddy requires the uploads directory to be in the standard WordPress location.&lt;br /&gt;
** Backups will be stored in /wp-content/uploads/backupbuddy_backups/&lt;br /&gt;
** Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)&lt;br /&gt;
* Free disk space equal to or greater than the entire size of your site once compressed.&lt;br /&gt;
* wp-config.php file must be in WordPress installation directory OR (starting with BackupBuddy v3.0) in the parent directory.&lt;br /&gt;
&lt;br /&gt;
===Host Compatibility===&lt;br /&gt;
Compare various [[BackupBuddy:_Hosts|Hosts &amp;amp; Hosting Environments]] to see how your host/potential host compares.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Misc. Information===&lt;br /&gt;
Find out some [[BackupBuddy:_Misc_Information|Miscellaneous Information]] about BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
	&lt;br /&gt;
=Troubleshooting=&lt;br /&gt;
&lt;br /&gt;
===Frequently Seen Support Issues===&lt;br /&gt;
''Problems?'' We have compiled a list of issues and solutions to many problems that we have seen encountered before. [[BackupBuddy:_Frequent_Support_Issues|Frequently Seen Support Issues]] to attempt to narrow down your problem and find a solution.&lt;br /&gt;
&lt;br /&gt;
===BackupBuddy: Error Codes===&lt;br /&gt;
Receive an error code? Check out the [[BackupBuddy:_Error_Codes|Error Codes]] page for explanations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Manual Migration===&lt;br /&gt;
Import fails on file extraction? Learn how to perform a [[BackupBuddy:_Manual_Migration|Manual Migration]] ... it's easier than you'd think!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
&lt;br /&gt;
'''Tools'''&lt;br /&gt;
&lt;br /&gt;
* [http://ithemes.com/codex/page/File:Zip_test.zip Manually test command line zip functionality]&lt;br /&gt;
&lt;br /&gt;
=Multisite=&lt;br /&gt;
&lt;br /&gt;
BackupBuddy supports the following Multisite functionality:&lt;br /&gt;
* Export a Multisite subsite to standalone&lt;br /&gt;
* Import an exported Multisite subsite into an existing Network&lt;br /&gt;
* Import a standalone WordPress site into an existing Network&lt;br /&gt;
* Backup entire Network (backup/restore only; no migration to new URL)&lt;br /&gt;
* Restore entire Network WITHOUT URL migration for subsites within if migrating to a new URL (URL changes have limitations. Please see Multisite page for details)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://ithemes.com/codex/page/BackupBuddy_Multisite Check out the BackupBuddy Multisite Codex] and [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite Beta Today!]&lt;br /&gt;
&lt;br /&gt;
BETA indicates that Multisite functionality has known issues and is not reccomended for production use except at your own risk.  We do NOT guarantee its functionality or provide guaranteed support for beta products.&lt;br /&gt;
&lt;br /&gt;
'''Links'''&lt;br /&gt;
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]&lt;br /&gt;
# [http://ithemes.com/codex/page/BackupBuddy_Multisite BackupBuddy Multisite Codex]&lt;br /&gt;
# [http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy beta Multisite support announcement]&lt;br /&gt;
# [http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ BackupBuddy beta Multisite key points everyone is raving about!] &lt;br /&gt;
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]&lt;br /&gt;
# [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
# [http://pluginbuddy.com/support/ Support Forums]&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy</id>
		<title>BackupBuddy</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy"/>
				<updated>2013-04-11T02:06:17Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* '''New to BackupBuddy?''' Check out the [[BackupBuddy:_Getting_Started|Getting Started]] page.&lt;br /&gt;
* '''Problems?''' Check out the [[BackupBuddy:_Frequent_Support_Issues|Frequently Seen Support Issues]] page.&lt;br /&gt;
* '''Need hosting?''' ''Hostgator Coupons'' are available to BackupBuddy customers [http://ithemes.com/forum/index.php?/topic/14012-hostgator-coupons-for-our-community/ here].&lt;br /&gt;
* '''[http://ithemes.com/codex/page/BackupBuddy_Multisite BackupBuddy Multisite Codex]'''&lt;br /&gt;
&lt;br /&gt;
=Tutorials=&lt;br /&gt;
&lt;br /&gt;
===Training Videos===&lt;br /&gt;
For video training including walkthroughs &amp;amp; tutorials please see http://ithemes.com/backupbuddy-training/&lt;br /&gt;
&lt;br /&gt;
===Installing BackupBuddy===&lt;br /&gt;
&lt;br /&gt;
Check out the [[Installing BackupBuddy]] section to see how BackupBuddy can be uploaded and activated on Single sites or Multisite networks or Multisite sites.&lt;br /&gt;
&lt;br /&gt;
===Getting Started===&lt;br /&gt;
Check out the [[BackupBuddy:_Getting_Started|Getting Started]] page to backup your Single sites or Multisite networks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Restore or Migrate===&lt;br /&gt;
Learn to [[BackupBuddy:_ImportBuddy|Restore or Migrate]] your Single sites or Multisite networks with the latest importbuddy.php.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Settings Explained===&lt;br /&gt;
Get in depth information about the various [[BackupBuddy:_Settings|Settings]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Developing Locally===&lt;br /&gt;
See the [[BackupBuddy:_Local_Development|Develop Sites Locally]] page for developing WordPress sites locally on your own computer using something like XAMPP or MAMP.  You can then migrate them to your web host.&lt;br /&gt;
&lt;br /&gt;
=Specifications=&lt;br /&gt;
Server configuration is a very complex topic and varies wildly between hosts, server operating systems, and even the personal preference of the server administrator. Below are the bare minimum requirements for the plugin along with the recommended setup to get the most out of this plugin. You may use [[ServerBuddy]] to help you determine how your server compares to our minimum requirements &amp;amp; recommendations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Using your HOSTS file for seamless migrations==&lt;br /&gt;
Here's one tutorial that may help:&lt;br /&gt;
http://www.bleepingcomputer.com/tutorials/hosts-files-explained/&lt;br /&gt;
&lt;br /&gt;
The HOSTS file allows you to basically just update the DNS settings for the site ONLY FOR YOU on your computer.  This lets you try out what would happen if you updated the DNS settings for everyone but only locally. The goal is basically to make your own computer think that your website is reached by going to the new IP address instead of the IP address everyone else on the internet goes to by visiting your URL.  This allows you to access the new site before officially pointing everyone on the internet to the new server.&lt;br /&gt;
&lt;br /&gt;
The procedure is basically:&lt;br /&gt;
* Update your computer's HOSTS file to point the new destination server IP address. Leave DNS settings as-is so that everyone else online will continue to see the normal site.&lt;br /&gt;
* Connect to your site.  When you connect to it you should end up on the new server if you've set up your HOSTS file properly. Upload ImportBuddy, your backup file, etc to it.&lt;br /&gt;
* Restore normally.  Verify that it all works properly.&lt;br /&gt;
* Assuming everything is good to go you can then change the DNS so that everyone else online gets switched over to accessing the new server. This results in a seamless launch with no down-time.  Make sure to re-edit your HOSTS file to remove the bypass so you don't forget.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Server Recommendations (full functionality)===&lt;br /&gt;
* PHP 5.2+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires PHP 5.2+]&lt;br /&gt;
* mySQL 5.x+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires mySQL 5.0.15+]&lt;br /&gt;
** For best results, use MySQL 5.1+&lt;br /&gt;
* WordPress 3.3+ &lt;br /&gt;
* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.&lt;br /&gt;
** Backups will be stored in /wp-content/uploads/backupbuddy_backups/&lt;br /&gt;
** Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)&lt;br /&gt;
* Free disk space equal to or greater than the entire size of your site once compressed.&lt;br /&gt;
** SuPHP or environment so that file operations/zip run as user to prevent permissions issues.&lt;br /&gt;
** PHP exec() function enabled&lt;br /&gt;
** PHP ZipArchive class installed&lt;br /&gt;
* Linux (Apache):&lt;br /&gt;
** Command-line zip installed and accessible via exec().&lt;br /&gt;
* Windows (only supported for local development via Apache; IIS is not officially supported):&lt;br /&gt;
** Windows zip executable (available [http://pluginbuddy.com/wp-content/uploads/2010/05/backupbuddy_windows_unzip.zip here])&lt;br /&gt;
*** You must have the ability to configure your server to allow execution of this zip.exe file for it to function.&lt;br /&gt;
*** File permissions must also be set to allow access and execution of the zip executable.&lt;br /&gt;
* wp-config.php file must be in WordPress installation directory OR (starting with BackupBuddy v3.0) in the parent directory.&lt;br /&gt;
&lt;br /&gt;
===Minimum Server Requirements (reduced functionality)===&lt;br /&gt;
'' NOTE: Some features of BackupBuddy will be unavailable or limited if running on minimum requirements without recommendations. Large sites may not be able to be backed up with these minimum features.'''&lt;br /&gt;
* PHP 5.2+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires PHP 5.2+]&lt;br /&gt;
* mySQL 5.x+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires mySQL 5.0.15+]&lt;br /&gt;
* WordPress 3.2+&lt;br /&gt;
** We are trying to maintain bare minimum backup functionality for legacy versions as far back as WordPress v2.6 (though it's not pretty nor guaranteed to work perfectly at this time; we recommend only performing backups &amp;amp; direct restores for older versions and use it for safety while upgrading to the latest WordPress).&lt;br /&gt;
* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.&lt;br /&gt;
* BackupBuddy requires the uploads directory to be in the standard WordPress location.&lt;br /&gt;
** Backups will be stored in /wp-content/uploads/backupbuddy_backups/&lt;br /&gt;
** Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)&lt;br /&gt;
* Free disk space equal to or greater than the entire size of your site once compressed.&lt;br /&gt;
* wp-config.php file must be in WordPress installation directory OR (starting with BackupBuddy v3.0) in the parent directory.&lt;br /&gt;
&lt;br /&gt;
===Host Compatibility===&lt;br /&gt;
Compare various [[BackupBuddy:_Hosts|Hosts &amp;amp; Hosting Environments]] to see how your host/potential host compares.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Misc. Information===&lt;br /&gt;
Find out some [[BackupBuddy:_Misc_Information|Miscellaneous Information]] about BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
	&lt;br /&gt;
=Troubleshooting=&lt;br /&gt;
&lt;br /&gt;
===Frequently Seen Support Issues===&lt;br /&gt;
''Problems?'' We have compiled a list of issues and solutions to many problems that we have seen encountered before. [[BackupBuddy:_Frequent_Support_Issues|Frequently Seen Support Issues]] to attempt to narrow down your problem and find a solution.&lt;br /&gt;
&lt;br /&gt;
===BackupBuddy: Error Codes===&lt;br /&gt;
Receive an error code? Check out the [[BackupBuddy:_Error_Codes|Error Codes]] page for explanations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Manual Migration===&lt;br /&gt;
Import fails on file extraction? Learn how to perform a [[BackupBuddy:_Manual_Migration|Manual Migration]] ... it's easier than you'd think!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
&lt;br /&gt;
'''Tools'''&lt;br /&gt;
&lt;br /&gt;
* [http://ithemes.com/codex/page/File:Zip_test.zip Manually test command line zip functionality]&lt;br /&gt;
&lt;br /&gt;
=Multisite=&lt;br /&gt;
&lt;br /&gt;
BackupBuddy supports the following Multisite functionality:&lt;br /&gt;
* Export a Multisite subsite to standalone&lt;br /&gt;
* Import an exported Multisite subsite into an existing Network&lt;br /&gt;
* Import a standalone WordPress site into an existing Network&lt;br /&gt;
* Backup entire Network (backup/restore only; no migration to new URL)&lt;br /&gt;
* Restore entire Network WITHOUT URL migration for subsites within if migrating to a new URL (URL changes have limitations. Please see Multisite page for details)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://ithemes.com/codex/page/BackupBuddy_Multisite Check out the BackupBuddy Multisite Codex] and [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite Beta Today!]&lt;br /&gt;
&lt;br /&gt;
BETA indicates that Multisite functionality has known issues and is not reccomended for production use except at your own risk.  We do NOT guarantee its functionality or provide guaranteed support for beta products.&lt;br /&gt;
&lt;br /&gt;
'''Links'''&lt;br /&gt;
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]&lt;br /&gt;
# [http://ithemes.com/codex/page/BackupBuddy_Multisite BackupBuddy Multisite Codex]&lt;br /&gt;
# [http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy beta Multisite support announcement]&lt;br /&gt;
# [http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ BackupBuddy beta Multisite key points everyone is raving about!] &lt;br /&gt;
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]&lt;br /&gt;
# [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
# [http://pluginbuddy.com/support/ Support Forums]&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy:_Local_Development</id>
		<title>BackupBuddy: Local Development</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy:_Local_Development"/>
				<updated>2013-04-11T02:05:52Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''SUPPORT DISCLAIMER: As running a local development environment is in fact running a server, you - the user - are expected to have an understanding of how a server is configured and operated and that iThemes / PluginBuddy cannot be expected to diagnose and fix server issues in the same way that we would not diagnose and fix commercial host server issues - these development environment have their own support offerings and they should be used.'''&lt;br /&gt;
&lt;br /&gt;
Windows ZIP.exe &amp;amp; UNZIP.exe files: http://pluginbuddy.com/wp-content/uploads/2010/05/backupbuddy_windows_unzip.zip&lt;br /&gt;
&lt;br /&gt;
==XAMPP==&lt;br /&gt;
&lt;br /&gt;
XAMPP for Windows: http://www.apachefriends.org/en/xampp.html&lt;br /&gt;
&lt;br /&gt;
==MAMP==&lt;br /&gt;
&lt;br /&gt;
* To modify your php.ini file please see the Mamp documentation. Recommended changes can be see under the Mamp Pro section below.&lt;br /&gt;
&lt;br /&gt;
===MAMP PRO===&lt;br /&gt;
* To modify your php.ini file, select File -&amp;gt; Edit Template -&amp;gt; PHP -&amp;gt; PHP (version) ini&lt;br /&gt;
** See the below defaults and the recommended changes below.&lt;br /&gt;
&lt;br /&gt;
''Mamp php.ini defaults''&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
max_execution_time = 30     ; Maximum execution time of each script, in seconds&lt;br /&gt;
max_input_time = 60	; Maximum amount of time each script may spend parsing request data&lt;br /&gt;
memory_limit = 32M      ; Maximum amount of memory a script may consume (8MB)&lt;br /&gt;
magic_quotes_gpc = On&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''Mamp php.ini recommendations''&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
max_execution_time = 60     ; Maximum execution time of each script, in seconds&lt;br /&gt;
max_input_time = 60	; Maximum amount of time each script may spend parsing request data&lt;br /&gt;
memory_limit = 256M      ; Maximum amount of memory a script may consume (8MB)&lt;br /&gt;
magic_quotes_gpc = Off&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy</id>
		<title>BackupBuddy</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy"/>
				<updated>2013-04-11T02:05:38Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: /* Developing Locally */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* '''New to BackupBuddy?''' Check out the [[BackupBuddy:_Getting_Started|Getting Started]] page.&lt;br /&gt;
* '''Problems?''' Check out the [[BackupBuddy:_Frequent_Support_Issues|Frequently Seen Support Issues]] page.&lt;br /&gt;
* '''Need hosting?''' ''Hostgator Coupons'' are available to BackupBuddy customers [http://ithemes.com/forum/index.php?/topic/14012-hostgator-coupons-for-our-community/ here].&lt;br /&gt;
* '''[http://ithemes.com/codex/page/BackupBuddy_Multisite BackupBuddy Multisite Codex]'''&lt;br /&gt;
&lt;br /&gt;
=Tutorials=&lt;br /&gt;
&lt;br /&gt;
===Training Videos===&lt;br /&gt;
For video training including walkthroughs &amp;amp; tutorials please see http://ithemes.com/backupbuddy-training/&lt;br /&gt;
&lt;br /&gt;
===Installing BackupBuddy===&lt;br /&gt;
&lt;br /&gt;
Check out the [[Installing BackupBuddy]] section to see how BackupBuddy can be uploaded and activated on Single sites or Multisite networks or Multisite sites.&lt;br /&gt;
&lt;br /&gt;
===Getting Started===&lt;br /&gt;
Check out the [[BackupBuddy:_Getting_Started|Getting Started]] page to backup your Single sites or Multisite networks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Restore or Migrate===&lt;br /&gt;
Learn to [[BackupBuddy:_ImportBuddy|Restore or Migrate]] your Single sites or Multisite networks with the latest importbuddy.php.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Settings Explained===&lt;br /&gt;
Get in depth information about the various [[BackupBuddy:_Settings|Settings]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Developing Locally===&lt;br /&gt;
See the [[BackupBuddy:_Local_Development|Develop Sites Locally]] page for developing WordPress sites locally on your own computer using something like XAMPP or MAMP.  You can then migrate them to your web host.&lt;br /&gt;
&lt;br /&gt;
=Specifications=&lt;br /&gt;
Server configuration is a very complex topic and varies wildly between hosts, server operating systems, and even the personal preference of the server administrator. Below are the bare minimum requirements for the plugin along with the recommended setup to get the most out of this plugin. You may use [[ServerBuddy]] to help you determine how your server compares to our minimum requirements &amp;amp; recommendations.&lt;br /&gt;
&lt;br /&gt;
===Server Recommendations (full functionality)===&lt;br /&gt;
* PHP 5.2+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires PHP 5.2+]&lt;br /&gt;
* mySQL 5.x+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires mySQL 5.0.15+]&lt;br /&gt;
** For best results, use MySQL 5.1+&lt;br /&gt;
* WordPress 3.3+ &lt;br /&gt;
* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.&lt;br /&gt;
** Backups will be stored in /wp-content/uploads/backupbuddy_backups/&lt;br /&gt;
** Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)&lt;br /&gt;
* Free disk space equal to or greater than the entire size of your site once compressed.&lt;br /&gt;
** SuPHP or environment so that file operations/zip run as user to prevent permissions issues.&lt;br /&gt;
** PHP exec() function enabled&lt;br /&gt;
** PHP ZipArchive class installed&lt;br /&gt;
* Linux (Apache):&lt;br /&gt;
** Command-line zip installed and accessible via exec().&lt;br /&gt;
* Windows (only supported for local development via Apache; IIS is not officially supported):&lt;br /&gt;
** Windows zip executable (available [http://pluginbuddy.com/wp-content/uploads/2010/05/backupbuddy_windows_unzip.zip here])&lt;br /&gt;
*** You must have the ability to configure your server to allow execution of this zip.exe file for it to function.&lt;br /&gt;
*** File permissions must also be set to allow access and execution of the zip executable.&lt;br /&gt;
* wp-config.php file must be in WordPress installation directory OR (starting with BackupBuddy v3.0) in the parent directory.&lt;br /&gt;
&lt;br /&gt;
===Minimum Server Requirements (reduced functionality)===&lt;br /&gt;
'' NOTE: Some features of BackupBuddy will be unavailable or limited if running on minimum requirements without recommendations. Large sites may not be able to be backed up with these minimum features.'''&lt;br /&gt;
* PHP 5.2+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires PHP 5.2+]&lt;br /&gt;
* mySQL 5.x+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires mySQL 5.0.15+]&lt;br /&gt;
* WordPress 3.2+&lt;br /&gt;
** We are trying to maintain bare minimum backup functionality for legacy versions as far back as WordPress v2.6 (though it's not pretty nor guaranteed to work perfectly at this time; we recommend only performing backups &amp;amp; direct restores for older versions and use it for safety while upgrading to the latest WordPress).&lt;br /&gt;
* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.&lt;br /&gt;
* BackupBuddy requires the uploads directory to be in the standard WordPress location.&lt;br /&gt;
** Backups will be stored in /wp-content/uploads/backupbuddy_backups/&lt;br /&gt;
** Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)&lt;br /&gt;
* Free disk space equal to or greater than the entire size of your site once compressed.&lt;br /&gt;
* wp-config.php file must be in WordPress installation directory OR (starting with BackupBuddy v3.0) in the parent directory.&lt;br /&gt;
&lt;br /&gt;
===Host Compatibility===&lt;br /&gt;
Compare various [[BackupBuddy:_Hosts|Hosts &amp;amp; Hosting Environments]] to see how your host/potential host compares.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Misc. Information===&lt;br /&gt;
Find out some [[BackupBuddy:_Misc_Information|Miscellaneous Information]] about BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
	&lt;br /&gt;
=Troubleshooting=&lt;br /&gt;
&lt;br /&gt;
===Frequently Seen Support Issues===&lt;br /&gt;
''Problems?'' We have compiled a list of issues and solutions to many problems that we have seen encountered before. [[BackupBuddy:_Frequent_Support_Issues|Frequently Seen Support Issues]] to attempt to narrow down your problem and find a solution.&lt;br /&gt;
&lt;br /&gt;
===BackupBuddy: Error Codes===&lt;br /&gt;
Receive an error code? Check out the [[BackupBuddy:_Error_Codes|Error Codes]] page for explanations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Manual Migration===&lt;br /&gt;
Import fails on file extraction? Learn how to perform a [[BackupBuddy:_Manual_Migration|Manual Migration]] ... it's easier than you'd think!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
&lt;br /&gt;
'''Tools'''&lt;br /&gt;
&lt;br /&gt;
* [http://ithemes.com/codex/page/File:Zip_test.zip Manually test command line zip functionality]&lt;br /&gt;
&lt;br /&gt;
=Multisite=&lt;br /&gt;
&lt;br /&gt;
BackupBuddy supports the following Multisite functionality:&lt;br /&gt;
* Export a Multisite subsite to standalone&lt;br /&gt;
* Import an exported Multisite subsite into an existing Network&lt;br /&gt;
* Import a standalone WordPress site into an existing Network&lt;br /&gt;
* Backup entire Network (backup/restore only; no migration to new URL)&lt;br /&gt;
* Restore entire Network WITHOUT URL migration for subsites within if migrating to a new URL (URL changes have limitations. Please see Multisite page for details)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://ithemes.com/codex/page/BackupBuddy_Multisite Check out the BackupBuddy Multisite Codex] and [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite Beta Today!]&lt;br /&gt;
&lt;br /&gt;
BETA indicates that Multisite functionality has known issues and is not reccomended for production use except at your own risk.  We do NOT guarantee its functionality or provide guaranteed support for beta products.&lt;br /&gt;
&lt;br /&gt;
'''Links'''&lt;br /&gt;
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]&lt;br /&gt;
# [http://ithemes.com/codex/page/BackupBuddy_Multisite BackupBuddy Multisite Codex]&lt;br /&gt;
# [http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy beta Multisite support announcement]&lt;br /&gt;
# [http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ BackupBuddy beta Multisite key points everyone is raving about!] &lt;br /&gt;
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]&lt;br /&gt;
# [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
# [http://pluginbuddy.com/support/ Support Forums]&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy:_Local_Development</id>
		<title>BackupBuddy: Local Development</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy:_Local_Development"/>
				<updated>2013-04-11T02:02:20Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''SUPPORT DISCLAIMER: As running a local development environment is in fact running a server, you - the user - are expected to have an understanding of how a server is configured and operated and that iThemes / PluginBuddy cannot be expected to diagnose and fix server issues in the same way that we would not diagnose and fix commercial host server issues - these development environment have their own support offerings and they should be used.'''&lt;br /&gt;
&lt;br /&gt;
Windows ZIP.exe &amp;amp; UNZIP.exe files: http://pluginbuddy.com/wp-content/uploads/2010/05/backupbuddy_windows_unzip.zip&lt;br /&gt;
&lt;br /&gt;
==XAMPP==&lt;br /&gt;
&lt;br /&gt;
XAMPP for Windows: http://www.apachefriends.org/en/xampp.html&lt;br /&gt;
&lt;br /&gt;
==MAMP==&lt;br /&gt;
&lt;br /&gt;
* To modify your php.ini file please see the Mamp documentation. Recommended changes can be see under the Mamp Pro section below.&lt;br /&gt;
&lt;br /&gt;
===MAMP PRO===&lt;br /&gt;
* To modify your php.ini file, select File -&amp;gt; Edit Template -&amp;gt; PHP -&amp;gt; PHP (version) ini&lt;br /&gt;
** See the below defaults and the recommended changes below.&lt;br /&gt;
&lt;br /&gt;
''Mamp php.ini defaults''&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
max_execution_time = 30     ; Maximum execution time of each script, in seconds&lt;br /&gt;
max_input_time = 60	; Maximum amount of time each script may spend parsing request data&lt;br /&gt;
memory_limit = 32M      ; Maximum amount of memory a script may consume (8MB)&lt;br /&gt;
magic_quotes_gpc = On&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
''Mamp php.ini recommendations''&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
max_execution_time = 60     ; Maximum execution time of each script, in seconds&lt;br /&gt;
max_input_time = 60	; Maximum amount of time each script may spend parsing request data&lt;br /&gt;
memory_limit = 256M      ; Maximum amount of memory a script may consume (8MB)&lt;br /&gt;
magic_quotes_gpc = Off&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==HOSTS FILE==&lt;br /&gt;
Here's one tutorial that may help:&lt;br /&gt;
http://www.bleepingcomputer.com/tutorials/hosts-files-explained/&lt;br /&gt;
&lt;br /&gt;
The HOSTS file allows you to basically just update the DNS settings for the site ONLY FOR YOU on your computer.  This lets you try out what would happen if you updated the DNS settings for everyone but only locally. The goal is basically to make your own computer think that your website is reached by going to the new IP address instead of the IP address everyone else on the internet goes to by visiting your URL.  This allows you to access the new site before officially pointing everyone on the internet to the new server.&lt;br /&gt;
&lt;br /&gt;
The procedure is basically:&lt;br /&gt;
* Update your computer's HOSTS file to point the new destination server IP address. Leave DNS settings as-is so that everyone else online will continue to see the normal site.&lt;br /&gt;
* Connect to your site.  When you connect to it you should end up on the new server if you've set up your HOSTS file properly. Upload ImportBuddy, your backup file, etc to it.&lt;br /&gt;
* Restore normally.  Verify that it all works properly.&lt;br /&gt;
* Assuming everything is good to go you can then change the DNS so that everyone else online gets switched over to accessing the new server. This results in a seamless launch with no down-time.  Make sure to re-edit your HOSTS file to remove the bypass so you don't forget.&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy:_Error_Codes</id>
		<title>BackupBuddy: Error Codes</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy:_Error_Codes"/>
				<updated>2013-04-03T04:34:05Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==3382==&lt;br /&gt;
&amp;lt;strong&amp;gt;Backup FAILED. Unable to successfully generate ZIP archive. Error #3382.12:20:04: Failed function backup_zip_files. Backup terminated.&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* The 3382 error literally means that both command line zip AND pclzip were unable to create a .zip file and failed for some reason.&lt;br /&gt;
* Possible causes:&lt;br /&gt;
** There are file(s)/folder(s) in your site installation directory that the server process building the backup zip archive file is unable to access and hence the backup will be halted rather than be created with the possibility of content that you have requested to be included not actually being able to be included. The Status Log of the manual backup will include log entries related to the problem files and you can investigate these identified files to determine what the problem may be with the site and resolve it so that either the files can be included or not based upon the result of your investigation. If you are seeing the error code in an email in relation to a scheduled backup then as the email suggests you should run a manual backup to check as noted above.&lt;br /&gt;
** Command line zip is being actively killed. (Cheapest packages at Godaddy kill off exec() within about 10 seconds, throwing the user into compatibility mode which cannot handle larger sites).&lt;br /&gt;
** Permissions may be blocking backup file creation. Make sure permissions are set to 755 for the /wp-content/uploads/ directory recursively.&lt;br /&gt;
** Your hosting account may not have enough free space to create the backup file.&lt;br /&gt;
** There may be one or more files/folders being included in the backup which neither the native zip command nor the pclzip function are able to access, e.g., unreadable files or broken symbolic links&lt;br /&gt;
* Possible solutions:&lt;br /&gt;
** If you have BackupBuddy Version 3.1.8.3 or later then the Status Log of a manual backup will contain detailed information concerning the problem, which may be just an exit code or an exit code and information on files and may indicate problems such as the file being unreadable - you should check the file(s) noted and determine what the file(s) are so that you can determine how to proceed.&lt;br /&gt;
*** If you do not require the file then you can simply delete it&lt;br /&gt;
*** If you require the file and it should be included in the backup then you must change the ownership/permissions such that it is readable in the same way as other files on the site&lt;br /&gt;
*** If you require the file but do not want it in the backup then you must tell BackupBuddy to exclude it using the Exclusions on the Settings page&lt;br /&gt;
*** Remember that BackupBuddy is a WordPress site backup tool and not a hosting backup tool so ideally you should exclude everything from your backup that isn't required for the operation of your WordPress site and that includes any directories that your host may have created in your site installation directory, e.g., a cgi-bin directory is common but this is hosting specific and not a component of a WordPress site and should be restored by the host if required. There may be other such directories dependent on your host and it is very worthwhile becoming familiar with your site, what is there and why, so that you can more easily spot stuff that shouldn't be there. Please note that we cannot advise of the particulars of any specific site as we do not know the details of your site or your hosting but your host support should certainly be able to help you with information on whether and what files/folders they may put in the directory where you might have your site installed.&lt;br /&gt;
*** If you are having trouble interpreting the diagnostic information in the Status Log then please create a topic in the BackupBuddy Forum and we can help explain it to you - however, this doesn't mean to say that we can resolve the issue as it relates to your files and server.&lt;br /&gt;
** If you have BackupBuddy Version 2.2.29 up until  Version 3.1.8.2 then visit the Settings page and enable the Alternative Zip System option and save. Then repeat a Full backup and study the Advanced Details for indications of failure.&lt;br /&gt;
*** For the native zip command alternatives there will usually be an exit code followed by some general descriptive text concerning the reason for failure (such as being unable to read a file, lack of disk space, etc.).&lt;br /&gt;
*** If the failure is file based then unfortunately at present we are unable to isolate the specific file details from this command. However, the backup will fall back to the Compatibility Mode and the failure indication from that will almost certainly provide a specific indication of the file (including the absolute file path) that is causing the issue. In such a case you must correct the issue by making the file readable if that is appropriate for the file or alternatively use the Exclusions on the Settings page to exclude the folder that contains the bad file.&lt;br /&gt;
*** If you cannot make the file readable and you cannot exclude the folder (because it contains other files that you need) then you will need to consult your host support to try and resolve what is the issue with the file.&lt;br /&gt;
*** If you are having trouble interpreting the diagnostic information in the Advanced Details then please create a topic in the BackupBuddy Forum and we can help explain it to you - however, this doesn't mean to say that we can resolve the issue as it relates to your files and server.&lt;br /&gt;
** Verify permissions are set correctly for /wp-content/uploads/ and all subdirectories/files therein - the server process running the backup needs to be able to access the directories and read/write files/directories - commonly this may mean 755 permissions for directories and 644 permissions for files.&lt;br /&gt;
** Verify allowed disk usage isn't close or exceeded. (ie Your hosting account is limited to 5GB and you've used 4.95GB.)&lt;br /&gt;
** Reducing backup size often helps. (directory exclusion, etc)&lt;br /&gt;
** Turning Zip Compression on or off may help.&lt;br /&gt;
** Have at least double the amount of defined storage quota available (or the same amount of free space as your used disk space) so that the backup can be created.&lt;br /&gt;
* Related link:&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/17953-backup-failure/#p85314&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/20145-another-solution-to-error-3382/&lt;br /&gt;
&lt;br /&gt;
==9001==&lt;br /&gt;
'''Unable to read database table wp_redirection_logs. Your backup will not include data from this table (you may ignore this warning if you do not need this specific data). This is due to the following error: MySQL client ran out of memory in /www/wp-content/plugins/backupbuddy/backupbuddy.php  on line 1757'''&lt;br /&gt;
&lt;br /&gt;
* '''MySQL client ran out of memory'''&lt;br /&gt;
** This is typically caused by your PHP memory limit being low, resulting in part of the data returned being clipped.  If you do not need the data from this specific table of the database to be backed up then you may safely ignore this.  Some tables, such as wp_redirection_logs, contain logs that you most likely do not need.&lt;br /&gt;
** BackupBuddy attempts to increase the PHP memory limit on runtime but many hosts block this.&lt;br /&gt;
** Add/modify this line in your php.ini with a higher number than the default, such as: php_value memory_limit 128M&lt;br /&gt;
** PHP memory is separate from mysql memory. Your host has to up the mysql memory as it is not possible for you the client to do so at all. &lt;br /&gt;
* '''Unable to save result set'''&lt;br /&gt;
** This is typically caused by a corrupt database/table. [http://textpattern.com/faq/36/warning-unable-to-save-result-set/ Citation of problem.]&lt;br /&gt;
** Repair the database/table using a tool such as phpMyAdmin or the free plugin [http://wordpress.org/extend/plugins/wp-dbmanager/ WP-dbManager]&lt;br /&gt;
** Add this line to wp-config.php to allow WordPress to repair tables: define('WP_ALLOW_REPAIR', true)&lt;br /&gt;
* '''MySQL server has gone away'''&lt;br /&gt;
** MySQL server is dying, this is mostly a host issue. Probably need to contact host to get them to fix the issue.&lt;br /&gt;
* WordPress Revisions may also be clogging up the system&lt;br /&gt;
** Disabling WordPress' automatic revisions, or at least limiting how many to keep, can help with this error&lt;br /&gt;
** http://codex.wordpress.org/Editing_wp-config.php#Post_Revisions&lt;br /&gt;
&lt;br /&gt;
==9002==&lt;br /&gt;
'''Unable to create temporary storage directory ((/www/wp-content/uploads/temp_xxxxxxxxxx)'''&lt;br /&gt;
&lt;br /&gt;
*This error means that BackupBuddy was unable to create a temporary storage directory at the location listed in the error message.  BackupBuddy must temporarily create this directory to place temporary files to be backed up into the ZIP file.&lt;br /&gt;
* Adjust permissions to allow write &amp;amp; directory creation access to your uploads folder. ie: /www/wp-content/uploads/&lt;br /&gt;
&lt;br /&gt;
==9003==&lt;br /&gt;
&lt;br /&gt;
'''BackupBuddy data file (backupbuddy_dat.php) missing or unreadable. There may be a problem with the backup file, the files could not be extracted (you may manually extract the zip file in this directory to manually do this portion of restore), or the files were deleted before this portion of the restore was reached. Start the import process over or try manually extracting (unzipping) the files then starting over. Restore will not continue to protect integrity of any existing data.'''&lt;br /&gt;
&lt;br /&gt;
* This error is often caused by the importbuddy.php script being replaced by an older version during the unzip step. See [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Old_importbuddy_overwriting_on_unzip importbuddy overwriting on unzip]&lt;br /&gt;
* This error is often caused by the server timing out before zip file extraction could complete.&lt;br /&gt;
** Manually extract files using either cPanel or extracting (unzipping) the files locally then uploading them &amp;amp; selecting the importbuddy.php advanced option to skip file extraction.&lt;br /&gt;
** Ask your server host to extend the maximum script execution time.&lt;br /&gt;
** Create a custom php.ini file if your host allows for this.&lt;br /&gt;
*** Tutorial: Create custom php.ini &amp;amp; enable in cPanel: http://pluginbuddy.com/tutorials/custom_php_ini/&lt;br /&gt;
*** Dreamhost users may use this tool if they do not want to use the above method: http://sxi.sabrextreme.com/dh-phpini&lt;br /&gt;
*** Increase php.ini max_execution_time&lt;br /&gt;
** Change hosts &amp;amp; let your current host know why you changed.&lt;br /&gt;
* Additional potential causes (very rare):&lt;br /&gt;
** File permissions not allowing reading of the backupbuddy_dat.php file.&lt;br /&gt;
** Incomplete backup. Verify the backup is marked as Good on the source site.&lt;br /&gt;
&lt;br /&gt;
==9004==&lt;br /&gt;
&lt;br /&gt;
'''Error! The unzip process reported success but the backup data file, backupbuddy_dat.php was not found in the extracted files. The unzip process either failed (most likely) or the zip file is not a proper BackupBuddy backup.''' (importbuddy.php)&lt;br /&gt;
&lt;br /&gt;
* Manually extract backup ZIP. This usually resolves this issue.&lt;br /&gt;
* Force compatibility mode to see if it able to unzip to completion.&lt;br /&gt;
* Contact the host to see if they can verify that the Linux command line ZIP is set up properly.&lt;br /&gt;
&lt;br /&gt;
==9005==&lt;br /&gt;
&lt;br /&gt;
'''File extraction process did not complete successfully. Unable to continue to next step. Manually extract the backup ZIP file and choose to &amp;quot;Skip File Extraction&amp;quot; from the advanced options on Step 1.''' (importbuddy.php)&lt;br /&gt;
* This ZIP file was unable to be extracted for some reason.&lt;br /&gt;
** Unzipping may have taken too long and the PHP process halted.&lt;br /&gt;
** Server memory usage may have been exceeded.&lt;br /&gt;
** Server configuration may be blocking extracting of ZIP files.&lt;br /&gt;
&lt;br /&gt;
* Attempt manual extraction &amp;amp; disable File Extraction from the advanced debugging options of Step 1.&lt;br /&gt;
&lt;br /&gt;
==9006==&lt;br /&gt;
'''ERROR: Unable to connect to database server and/or log in. Verify the database server name, username, and password.''' (importbuddy.php)&lt;br /&gt;
* Verify the server address, your username, and your password. One of these settings is wrong.&lt;br /&gt;
* cPanel sometimes prefixes your username with a prefix. Check if this exists.&lt;br /&gt;
&lt;br /&gt;
==9007==&lt;br /&gt;
'''Unable to select your specified database. Verify the database name and that you have set up proper permissions for your specified username to access it.''' (importbuddy.php)&lt;br /&gt;
* Verify the database name exists.&lt;br /&gt;
* Verify the mysql username has been granted ALL permissions to this database.&lt;br /&gt;
&lt;br /&gt;
==9008==&lt;br /&gt;
'''ERROR: A database prefix is required for importing.''' (importbuddy.php)&lt;br /&gt;
* You must specify a WordPress database table prefix. Default is &amp;quot;wp_&amp;quot; without quotes.&lt;br /&gt;
&lt;br /&gt;
==9009==&lt;br /&gt;
'''ERROR: Unable to find any database backup data in the selected backup.''' (importbuddy.php)&lt;br /&gt;
* Database file is missing from the backup.&lt;br /&gt;
&lt;br /&gt;
==9010==&lt;br /&gt;
'''ERROR: Unable to import SQL query:''' (importbuddy.php)&lt;br /&gt;
* Something went wrong attempting to import this row into the database.&lt;br /&gt;
* If it says duplicate table or row then the user is importing/migrating into a database that has an existing WordPress installation with the same prefix. This could cause problems if it's a different install or a lot has changed.&lt;br /&gt;
&lt;br /&gt;
==9011==&lt;br /&gt;
'''ERROR #9011.  FTP/FTPs login failed on scheduled FTP. Credentials: username:password@server.com.'''&lt;br /&gt;
* Unable to log in to FTP or FTPs server due to a problem with the login credentials. Verify your username and password.&lt;br /&gt;
&lt;br /&gt;
==9012==&lt;br /&gt;
'''FTP/FTPs file upload failed. Check file permissions &amp;amp; disk quota. Details: [additional details here]'''&lt;br /&gt;
* BackupBuddy was able to connect to the FTP server but was not able to upload the file.&lt;br /&gt;
* Verify file permissions allow writing and that enough disk space is available.&lt;br /&gt;
&lt;br /&gt;
==9013==&lt;br /&gt;
'''Sorry! PHP version x.x or newer is required for BackupBuddy to properly run. You are running PHP version x.x.x.'''&lt;br /&gt;
* BackupBuddy currently requires PHP 5.x.  See the Sales page or [[BackupBuddy]] codex page for the latest version requirements.&lt;br /&gt;
* Most hosts allow you to change the PHP version from their control panel.&lt;br /&gt;
&lt;br /&gt;
==9014==&lt;br /&gt;
'''Fatal error. The database already contains a WordPress installation with this prefix (27 tables). Restore has been stopped to prevent overwriting existing data. Please go back and enter a new database name and/or prefix OR clear our your database prior to restoring again.'''&lt;br /&gt;
* WordPress already exists in the database/prefix combo entered.&lt;br /&gt;
* Choose a new prefix, database, or delete the existing WordPress tables from the database.&lt;br /&gt;
&lt;br /&gt;
==9015==&lt;br /&gt;
'''Temp data directory is not writable. Check your permissions. (#directory#)'''&lt;br /&gt;
* Verify user permissions for this directory. Make sure the user can create &amp;amp; write files.&lt;br /&gt;
* Use SUPHP so PHP will run as your user.  This insures it will have proper file/directory permissions.&lt;br /&gt;
&lt;br /&gt;
==9016==&lt;br /&gt;
'''Archive file is not writable. is not writable. Check your permissions. (#directory#)'''&lt;br /&gt;
* Verify user permissions for this directory. Make sure the user can create &amp;amp; write files.&lt;br /&gt;
* Use SUPHP so PHP will run as your user.  This insures it will have proper file/directory permissions.&lt;br /&gt;
&lt;br /&gt;
==9017==&lt;br /&gt;
'''Temp data file is not creatable/writable. Check your permissions. (#directory#)'''&lt;br /&gt;
* Verify user permissions for this directory. Make sure the user can create &amp;amp; write files.&lt;br /&gt;
* Use SUPHP so PHP will run as your user.  This insures it will have proper file/directory permissions.&lt;br /&gt;
&lt;br /&gt;
==9018==&lt;br /&gt;
'''Database file is not creatable/writable. Check your permissions. (#directory#)'''&lt;br /&gt;
* Verify user permissions for this directory. Make sure the user can create &amp;amp; write files.&lt;br /&gt;
* Use SUPHP so PHP will run as your user.  This insures it will have proper file/directory permissions.&lt;br /&gt;
&lt;br /&gt;
==9019==&lt;br /&gt;
'''Invalid or corrupt AJAX data. (#DATA#)'''&lt;br /&gt;
* The backup data sent by the browser was invalid. Refresh and try again.&lt;br /&gt;
* Make sure you are using a modern browser on a stable internet connection.&lt;br /&gt;
&lt;br /&gt;
==9020==&lt;br /&gt;
'''Unable to write to file [.htaccess/wp-config.php]. Permissions are preventing this file from being modified.'''&lt;br /&gt;
* Verify write permissions are properly configured for this file. Suggestion: 755.&lt;br /&gt;
* For .htaccess: Another option is to delete the .htaccess file &amp;amp; in the WordPress admin navigate to Settings: Permalinks &amp;amp; click the Save button to regenerate the file.&lt;br /&gt;
&lt;br /&gt;
==9021==&lt;br /&gt;
'''PHP Timeout or Fatal Error Occurred'''&lt;br /&gt;
* &amp;quot;The page did not finish loading as expected. The most common cause for this is the PHP process taking more time than it has been allowed by your host (php.ini setting max_execution_time). If a PHP error is displayed above this can also cause this error. &amp;quot;&lt;br /&gt;
* Increase the maximum allowed PHP runtime by contacting your host or creating a php.ini file to override host settings (if allowed).&lt;br /&gt;
* If on the unzip step, manually extract the ZIP file on your local PC then upload or use another server-based software such as cpanel.&lt;br /&gt;
&lt;br /&gt;
==9022==&lt;br /&gt;
'''Error: Unable to create backup storage directory `/www/wp-content/uploads/backupbuddy_backups/`. Please verify that proper write permissions are enabled to create this directory. You may also manually create this directory. If you do so make sure to give permissions to allow writing backups into this directory.'''&lt;br /&gt;
&lt;br /&gt;
*This error means that BackupBuddy was unable to create a storage directory at the location listed in the error message.  BackupBuddy must create this directory to place backup files into.&lt;br /&gt;
* Adjust permissions to allow write &amp;amp; directory creation access to your uploads folder. ie: /www/wp-content/uploads/&lt;br /&gt;
&lt;br /&gt;
==9023==&lt;br /&gt;
'''The backup is of a full Multisite Network. You cannot import a Network into a Network. You may only import standalone sites and sites exported from a Multisite.'''&lt;br /&gt;
* If you want to import a site from a Multisite Network you must first use BackupBuddy to export a site from it.  You can then import that individually exported site into another Multisite Network using BackupBuddy's Multisite Import or even as a standalone site with importbuddy.php.&lt;br /&gt;
&lt;br /&gt;
==9024==&lt;br /&gt;
'''ERROR #9024: Connected to Amazon S3 but unable to put file. There is a problem with one of the following S3 settings: bucket, directory, or S3 permissions. Details: ...'''&lt;br /&gt;
* In the destination settings page click the button to test the connection to verify the settings.&lt;br /&gt;
* Try manually sending a backup.&lt;br /&gt;
* See the Details portion of this error at the end for advanced troubleshooting information. This may be helpful for support or the developers.&lt;br /&gt;
&lt;br /&gt;
==9025==&lt;br /&gt;
'''ERROR #9025: Connected to Rackspace but unable to put file. Verify Rackspace settings included Rackspace permissions, etc.'''&lt;br /&gt;
&lt;br /&gt;
==9026==&lt;br /&gt;
'''ERROR #9026: The mySQL server went away unexpectedly during database dump. This is almost always caused by mySQL running out of memory. The backup integrity can no longer be guaranteed so the backup has been halted. 'Last table dumped before database server went away: `wp_#####`.'''&lt;br /&gt;
* Ask host to increase mysql memory.&lt;br /&gt;
* Reduce database [table(s)] size.&lt;br /&gt;
&lt;br /&gt;
==9027==&lt;br /&gt;
'''ERROR #9027: The mySQL server went away and was unavailable for scheduling the next cron step. This is almost always caused by mySQL running out of memory. The backup integrity can no longer be guaranteed so the backup has been halted.'''&lt;br /&gt;
* This is the same issue as 9026 except that it may have happened after a different step than the database dump.&lt;br /&gt;
* See 9026.&lt;br /&gt;
&lt;br /&gt;
==9028==&lt;br /&gt;
'''ERROR #9028: Based on your backup archive limits (size limit) the backup that was just created would be deleted. Skipped deleting this backup. Please update your archive limits.'''&lt;br /&gt;
* Your archive size limit is less than the backup file size. This would result in all backup files being deleted, including the latest, which would result in zero backups. The last backup has been kept for safety.&lt;br /&gt;
* Adjust the backup size limit to a larger value or reduce the size of your backups by deleting files or excluding directories.&lt;br /&gt;
&lt;br /&gt;
==9029==&lt;br /&gt;
'''Error #9029: Table `TABLE_NAME` does not contain a primary key; BackupBuddy cannot safely modify the contents of this table. Skipping migration of this table. ([serialized()|bruteforce_table()])'''&lt;br /&gt;
* This table is not set up properly. All tables should have a PRIMARY key and/or a UNIQUE key. Mysql automatically returns the first fully unique key if available if a primary key does not exist.&lt;br /&gt;
* If a plugin created the reported table contact the author to have this corrected.&lt;br /&gt;
&lt;br /&gt;
==9030==&lt;br /&gt;
'''mysqlbuddy: Error #9030. Command did not exit normally. Falling back to database dump compatibility modes.'''&lt;br /&gt;
* Occurs when command line mysql is reported to be available but still failed. BackupBuddy cannot always capture command line mysql error messages.&lt;br /&gt;
* Common causes:&lt;br /&gt;
** One or more tables that was attempted to be imported already existed.&lt;br /&gt;
&lt;br /&gt;
==9031==&lt;br /&gt;
&amp;quot;Error #9031. Invalid backup serial (xxxxxxxxxx). Please check directory permissions and your PHP error_log as an early backup function (such as pre_backup) may have failed. Fatal error.&amp;quot;&lt;br /&gt;
* This is a fatal error which will halt the backup process. You must fix whatever is causing it before BackupBuddy can continue.&lt;br /&gt;
* This basically means that when BackupBuddy tried to load backup information for the unique backup your browser requested information on, no information was found. Please try the following fixes:&lt;br /&gt;
**1 : Fix the file and folder permissions on all your BackupBuddy folders and the wp-content/uploads folder to allow proper writing permissions. &lt;br /&gt;
**2 : Make sure you have plenty of free disk space.&lt;br /&gt;
**3 : Upgrade to the latest version of BackupBuddy to make sure you are not encountering any old bugs or we have improved workarounds for your server issue.&lt;br /&gt;
&lt;br /&gt;
*Related forum threads&lt;br /&gt;
**[http://ithemes.com/forum/index.php?/topic/13796-error-5445589-invalid-backup-serial/ File permissions causing 5445589 error]&lt;br /&gt;
**[http://ithemes.com/forum/index.php?/topic/14834-error-5445589-invalid-backup-serial-0i64w23keq-fatal-error/ Increase the available disk space]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==9032==&lt;br /&gt;
''BackupBuddy Error #9032: You have not set a password to download this script yet. Please do so on the Settings page. You should have been prompted for a password when you clicked to download this script. If you are seeing this then most likely another plugin is loading its javascript on our plugin page causing it to break. Try disabling all other plugins to see if that fixes it. If so then turn them back on one by one until you find the offending plugin. You may also view your browser javascript error console to check for any script errors to help diagnose the issue.''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==9033==&lt;br /&gt;
&amp;quot;Error #9033: The pre-backup initialization did not fully complete. Check for any errors above or in logs. Verify permissions &amp;amp; that there is enough server memory. See the BackupBuddy &amp;quot;Server Information&amp;quot; page to help assess your server.&amp;quot;&lt;br /&gt;
* One known cause: Server ran out of memory at some point during the pre_backup() initialization procedure, possibly during importbuddy generation.  Check PHP error log for memory errors.  Increase server memory for probably fix.&lt;br /&gt;
&lt;br /&gt;
==9034==&lt;br /&gt;
* Check file permissions on the reported file and its directory.  If still experiencing problems verify ownership and/or that suphp is installed and properly configured on the server. Contact host for details.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==3488439==&lt;br /&gt;
'''Error scheduling event with WordPress. Your schedule may not work properly. Please try again. Error #3488439.'''&lt;br /&gt;
* This means the built-in WordPress function wp_schedule_event() is returning false. The only thing that can cause that is another plugin or something filtering/blocking scheduling of events. So can try deactivating/disabling all other plugins and then see if it clears it up. If it does then one of them was conflicting and can reactivate the plugins one at a time to find which one causes it again.&lt;br /&gt;
** Letting the conflicting plugin's author know about the conflict is good to do as well so they can update their plugin and fix it&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==5445589==&lt;br /&gt;
'''Error #5445589 – Invalid b/u serial Verify b/u directory writer permission'''&lt;br /&gt;
* SEE ERROR #9031 ABOVE.&lt;br /&gt;
&lt;br /&gt;
==4543849498==&lt;br /&gt;
'''Error #4543849498. Missing old home URL.&lt;br /&gt;
Failed. Your current backup does not include a home URL. Make a new backup with the latest BackupBuddy before migrating.'''&lt;br /&gt;
* Error means that the backup file being used for the migration/restore is much older than the importbuddy version being used.&lt;br /&gt;
** Use a backup .zip file created from an up to date BackupBuddy (or at least a version not as old)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==8438934984==&lt;br /&gt;
'''Error #8438934984: dbimport class missing option in constructor $options variable.'''&lt;br /&gt;
* Error means that at the point of starting the database import importbuddy is missing one of the following: backup file identifier (the random 10 character string at the end of the backup file name); the database server address; the database name; the database user; the database password; the table prefix to use; or the table prefix that was previously used.&lt;br /&gt;
* Especially for the cases where migrating to a local server with root having no password&lt;br /&gt;
** For that case then the resolution is to create a database user and associated password and associate these with the specific database (as would be the case on a commercial host) and then use that user rather than &amp;quot;root&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
* Related forum threads:&lt;br /&gt;
** [http://ithemes.com/forum/topic/21500-restore-error-8438934984/page__p__100824#entry100824 Restore Error 8438934984]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Additional Resources==&lt;br /&gt;
# [[BackupBuddy: Advanced Debugging]]&lt;br /&gt;
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]&lt;br /&gt;
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]&lt;br /&gt;
# [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
# [http://pluginbuddy.com/support/ Support Forums]&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues</id>
		<title>BackupBuddy: Frequent Support Issues</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues"/>
				<updated>2013-03-30T02:41:32Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: /* 500 Server Errors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Backing Up=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==HTTP Loopback Connections Disabled==&lt;br /&gt;
* Also known as '''Endless Ping'''.&lt;br /&gt;
* This usually happens before the second Scheduled Cron in your backup is run. You can see the number of times &amp;quot;Scheduled Cron&amp;quot; is mentioned in the Advanced Logs shown on the backup page to see if this is the case.&lt;br /&gt;
* If your Server Information page reports that HTTP Loopback Connections are disabled or the following occurs (see below), you need to either enable HTTP Loopback Connections or enter the WordPress Alternate Cron setting in your wp-config.php file. This is caused if your host is blocking loopback connections within their firewall. You will need to request that your host change this (this is very standard to have this available), enable the alternate cron method in your wp-config.php (as Solution below - often the '''only''' solution for those in a shared environment), or move to a new host. &lt;br /&gt;
** If your backup progress (as detailed in the Advanced Details area) consistently '''never''' progresses beyond this point except for the continuous &amp;quot;pings&amp;quot;:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Backing up with BackupBuddy v2.1.8...&lt;br /&gt;
20:35:15: Setting greedy script limits.&lt;br /&gt;
20:35:15: Set memory limit to 256M. Previous value &amp;lt; 256M.&lt;br /&gt;
20:35:15: Finished greedy script limits.&lt;br /&gt;
20:35:15: Full backup mode.&lt;br /&gt;
20:35:15: Performing pre-backup procedures.&lt;br /&gt;
20:35:15: Backup serial: pyisomo736&lt;br /&gt;
20:35:15: Creating import data file.&lt;br /&gt;
20:35:15: Finished creating import data file.&lt;br /&gt;
20:35:15: Finished pre-backup procedures.&lt;br /&gt;
20:35:15: Scheduling Cron for pyisomo736.&lt;br /&gt;
1307910918|ping&lt;br /&gt;
1307910922|ping&lt;br /&gt;
1307910926|ping&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
* Solution:&lt;br /&gt;
** Add define('ALTERNATE_WP_CRON', true); to your wp-config.php&lt;br /&gt;
*** Open your wp-config.php in a text editor. This file is located in the root of your site.&lt;br /&gt;
*** Add the line somewhere between the first ( &amp;lt;?php ) and last line of the file (but before the line that says /* That's all, stop editing! Happy blogging. */)&lt;br /&gt;
*** &amp;lt;pre&amp;gt;define('ALTERNATE_WP_CRON', true);&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Deactivate all other plugins and see if it works then, if so then make sure you don't have a plugin that may apply a maintenance mode&lt;br /&gt;
*** This is because maintenance mode plugins rarely, if ever, take into account WordPress scheduling crons&lt;br /&gt;
* See also&lt;br /&gt;
**[http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Endless_Ping_on_second_Scheduling_Cron Endless Ping on Second Scheduling Cron in BackupBuddy Codex]&lt;br /&gt;
**[http://codex.wordpress.org/Editing_wp-config.php#Alternative_Cron WordPress Codex / Alternative Cron on WordPress.org]&lt;br /&gt;
&lt;br /&gt;
* Related threads with same/similar solutions:&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/17385-backupbuddy-doesnt-backup-at-all-infinite-ping/&lt;br /&gt;
** http://ithemes.com/forum/backupbuddy/endless-pinging-v2-2-14&lt;br /&gt;
&lt;br /&gt;
=== On Linux Systems ===&lt;br /&gt;
On Linux systems, be sure you have your /etc/hosts file correctly setup as problems here can cause loopback not to work.&lt;br /&gt;
&lt;br /&gt;
==Compatibility Mode==&lt;br /&gt;
* If your server does not support command line Zip then BackupBuddy will fall back into a compatibility mode to help aid you in creating a backup. This mode is significantly slower and less reliable.  It is not intended for persistent use and is provided to aid you in backing up in poor hosting environments, for instance to move to another host.&lt;br /&gt;
* Directory exclusion is not available in this mode.  Even existing backups will be backed up, resulting in rapidly growing backup file sizes.&lt;br /&gt;
* If you are running on a Windows server (or developing locally, ie on Xampp) you will need to install the [http://pluginbuddy.com/wp-content/uploads/2010/05/backupbuddy_windows_unzip.zip Windows zip.exe executable] (we do not provide support for setting this up, though the readme.txt in the file does help).&lt;br /&gt;
* Solutions:&lt;br /&gt;
** If you are running CentOS on a VPS or similar type of server then running the command &amp;lt;pre&amp;gt;yum install zip&amp;lt;/pre&amp;gt; as root will install the zip package and any dependencies. This may also apply to other environments using rpm packages and the yum package manager front-end. The yum manager can also be used to query installed packages and update packages, etc. If you have any issues with this then please consult your host support for additional assistance.&lt;br /&gt;
** for Debian-based Linux (including Ubuntu) run the following at the command line: &amp;lt;pre&amp;gt;sudo apt-get install zip unzip&amp;lt;/pre&amp;gt;&lt;br /&gt;
** If you are operating a Media Temple DV server then please make sure you have the Developer Tools installed as this contains the package necessary to provide zip capability.&lt;br /&gt;
** If your server is configured to disable access to the PHP exec() function and if you have access to configure your server then remove any blocking of the PHP exec() function in php.ini and configure permissions to allow running the Linux command line function `zip`.&lt;br /&gt;
** If your server is operating in safe_mode then either turn safe_mode off (if you can) or make sure that the safe_mode_exec_dir configuration parameter includes the directory which contains the `zip` command (please consult your host support for this information)&lt;br /&gt;
** Ask your host to enable access to the Linux command line Zip command via PHP's exec() function.&lt;br /&gt;
*** Example message to send to your host:&lt;br /&gt;
&amp;lt;pre&amp;gt;Dear Sir/Madam,&lt;br /&gt;
&lt;br /&gt;
I am attempting to use the highly popular WordPress backup software, BackupBuddy by PluginBuddy.com.&lt;br /&gt;
BackupBuddy requires the ability to use the Linux command line Zip command via PHP's exec() function.&lt;br /&gt;
BackupBuddy is reporting that it is unable to access this functionality on my server hosting environment.&lt;br /&gt;
Please enable this functionality for me so that I may use this backup solution in combination with your hosting.&lt;br /&gt;
These are commonly available features of many popular hosting providers such as HostGator.com so it is&lt;br /&gt;
not unreasonable to request it nor is it a security risk IF it is properly configured.&lt;br /&gt;
&lt;br /&gt;
Please verify access to the following features:&lt;br /&gt;
1) PHP's exec() function.&lt;br /&gt;
2) Permission to run Linux's `zip` command.&lt;br /&gt;
3) The directory containing the `zip` command is included in the PATH environment variable&lt;br /&gt;
available to the process executing the command passed to the exec() function &lt;br /&gt;
&lt;br /&gt;
Thank you for your time and consideration.&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Also possible that even though that zip via exec() is enabled it still may not work if host does not have zip's path location currently as a part of PATH (or the path is not one of the &amp;quot;well known&amp;quot; locations that more recent versions of BackupBuddy with search). The below code is an example of how to add the directory of the zip executable to PATH after you ask your host where it is being kept and whether this is the correct way to do it on their servers or if not what is the preferred way (please note the colon that precedes the path being added):&lt;br /&gt;
*** &amp;lt;pre&amp;gt;putenv( &amp;quot;PATH=&amp;quot; . getenv( 'PATH' ) . &amp;quot;:directory zip exe is&amp;quot; );&amp;lt;/pre&amp;gt;&lt;br /&gt;
*** The line has to be added anywhere in the wp-config.php file after the first line ( &amp;lt;?php ) but at least before the line that says /* That's all, stop editing! Happy Blogging */&lt;br /&gt;
** If all of the above are either impossible or unsuccessful and you absolutely must have the native zip command capability then you only option is to move your site to an alternative server or host that provides this capability.&lt;br /&gt;
&lt;br /&gt;
==Unable to create directory /public_html/yourdomain/wp-content/uploads/2012/03. Is its parent directory writable by the server?==&lt;br /&gt;
Happens when trying to activate/install BackupBuddy.&lt;br /&gt;
* Check in WordPress admin Settings-&amp;gt;Media under the Uploading Files heading and see if there is anything there. Generally if you are using the default location for wp-content they would be left blank.&lt;br /&gt;
* Also make sure there are not any references to another site in the wp-config.php file, some 1-click WordPress installers add definitions in there other servers don't like&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Warning: exec() has been disabled for security reasons in /www/wp-content/plugins/backupbuddy/lib/zip/zip.php on line ###==&lt;br /&gt;
* exec() is disabled somewhere in PHP configuration. Ask the host to correct this or use cPanel to edit PHP settings to enable it if possible. See 'Fallback to Compatibility Mode' above.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Warning: mysql_query() [function.mysql-query]: Unable to save result set in /www/wp-content/plugins/backupbuddy/backupbuddy.php on line 1673==&lt;br /&gt;
* See [http://ithemes.com/codex/page/BackupBuddy:_Error_Codes#9001 BackupBuddy Error Code 9001]&lt;br /&gt;
&lt;br /&gt;
==Godaddy Related==&lt;br /&gt;
* The bottom tier of Godaddy hosting services are known for not being able to complete backups within the maximum PHP runtime configured on their servers (usually 30 seconds), causing backups to fail.&lt;br /&gt;
* Solutions:&lt;br /&gt;
** Choose another quality hosting provider such as Hostgator.com (recommended)&lt;br /&gt;
** Upgrade to a higher tier of Godaddy hosting (not recommended as even better Godaddy servers are poor performers)&lt;br /&gt;
&lt;br /&gt;
==.htaccess 404 / Addhandler Warning==&lt;br /&gt;
* Some hosts use a line at the top of the .htaccess file in the root of the site to configure some server settings such as enabling PHP support for that site. When used on a host that does not need this it can break PHP or other functionality.  When migrating to a new site this can break the migration process. This often causes URLs to give 404 Not Found errors after migrating/restoring.&lt;br /&gt;
* Solution:&lt;br /&gt;
** Remove the Addhandler line from the .htaccess file before backup or open the backup ZIP archive and remove the line within the file within the ZIP.&lt;br /&gt;
&lt;br /&gt;
==Backup marked as bad==&lt;br /&gt;
* Backups are verified by verifying the following criteria:&lt;br /&gt;
** The ZIP file is not corrupt and is openable.&lt;br /&gt;
** The database (.sql) file exists.&lt;br /&gt;
** The wp-config.php file.&lt;br /&gt;
** The backupbuddy_dat.php file.&lt;br /&gt;
* Potential causes:&lt;br /&gt;
** The backup timed out and did not complete within the PHP maximum runtime (usually 30 seconds)&lt;br /&gt;
*** Solution: Reduce the backup size by deleting files or excluding one or more directories. You may use the `Server Information` page's Directory Size browser to find large directories/files.&lt;br /&gt;
** Your hosting account does not have enough free space available.&lt;br /&gt;
** You may have the backupbuddy_temp directory excluded.&lt;br /&gt;
&lt;br /&gt;
==Database backup succeeds, full fails==&lt;br /&gt;
* This is almost exclusively due any single step of the backup process not completing within the maximum PHP runtime (usually 30 seconds).&lt;br /&gt;
* If you are in compatibility mode then backups are significantly slower and less likely to complete in time.&lt;br /&gt;
* Solution:&lt;br /&gt;
** Ask your host to enable command line ZIP via exec() if you are in compatibility mode.&lt;br /&gt;
** Reduce the size of your backups by deleting files or excluding large directories.&lt;br /&gt;
&lt;br /&gt;
==Directories not being excluded==&lt;br /&gt;
* Directories are not excluded if BackupBuddy is being forced to fall into compatibility mode.  This is expected behaviour. This happens if command line Zip is unavailable via the PHP exec() function.&lt;br /&gt;
* Solutions:&lt;br /&gt;
** Contact your host and ask them if they can enable command line ZIP via exec() if using Linux. For Windows servers a zip.exe file is available by downloading it from the `Getting Started` page of BackupBuddy when running on a Windows host.&lt;br /&gt;
** Continue using compatibility mode. If you do this you will not be able to exclude directories, including the backups directory.  Because of this even backups will be backed up. We recommend not storing any backups locally in this case as your backup file sizes will increase exponentially.&lt;br /&gt;
&lt;br /&gt;
==Tempory files in directories/root==&lt;br /&gt;
* BackupBuddy creates several temporary files within the directory `/wp-content/uploads/backupbuddy_temp/` while generating a backup.  Some of these may remain temporarily after backups complete though most are cleaned up immeditately.  BackupBuddy will automatically clean up any remaining temporary files within 12 hours. This is an automated process.&lt;br /&gt;
* While in compatibility mode large sites can create temporary .gz files in the site root.  Sometimes these may be left behind and require manual cleanup at this time.  This is uncommon and is a result of not having command line ZIP via exec() available. Ask your host to enable this.&lt;br /&gt;
* Solution:&lt;br /&gt;
** Wait ~12 hours or delete the file(s) manually.&lt;br /&gt;
&lt;br /&gt;
==Backups Time Out / Marked as Bad==&lt;br /&gt;
* Backup file size is too large so it takes too many resources or too much time to finish so the process is killed.&lt;br /&gt;
* The maximum PHP runtime is typically 30 seconds so backups must finish within this time period.&lt;br /&gt;
* Try reducing backup size, excluding directories, disabling compression to speed up zip file generation, or getting host to enable native zip compression if not already enabled.&lt;br /&gt;
* Backup completed but backup ZIP is incomplete / bad: exec() shares the maximum allowed memory usage with PHP. If this memory limit is met the exec() / proc() will be killed and return to PHP. The symptoms of this are a bad / incomplete ZIP file despite the backup fully completing successfully. Try increasing `memory_limit` to a larger size.&lt;br /&gt;
** &amp;lt;table border=&amp;quot;1&amp;quot;&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;&amp;amp;nbsp;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;exec()&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;proc()&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Maximum PHP Runtime Timeout&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Zip file size stops increasing.&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Zip file size stops increasing&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Memory Limit Hit&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Zip creation completed but ZIP file&amp;lt;br&amp;gt;incomplete &amp;amp; marked as bad&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Zip file size stops increasing.&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Zip File Creation Dies at 2GB==&lt;br /&gt;
* The limit of some file systems on a 32bit server can create a file is 2GB.&lt;br /&gt;
** Ask host to user a better file system that allows for the creation and handling of files bigger than 2GB.&lt;br /&gt;
*** Large File Systems (LFS) don't technically have limits on how big they can support, they are designed to expand.&lt;br /&gt;
&lt;br /&gt;
==Zip File Creation Dies at ~4GB==&lt;br /&gt;
* On a 32bit server the limit for Zip Archive is about 4GB.&lt;br /&gt;
** Ask host to upgrade to 64bit.&lt;br /&gt;
** Host may be able to use better configurations or software for the server to up this while staying on 32bit though I am unsure on the details&lt;br /&gt;
&lt;br /&gt;
==Remote Transfers Fail==&lt;br /&gt;
* Login credentials are wrong. Test them to be sure that they have not changed.  This is exceedingly common.&lt;br /&gt;
* The path entered is incorrect or the directory has not been created.  BackupBuddy requires the path/bucket to already exist in some cases.&lt;br /&gt;
* Some hosts block outgoing connections. Try another remote destination if possible. Most remote destinations transfer over the HTTP port 80.&lt;br /&gt;
** Amazon S3: port 80&lt;br /&gt;
** Dropbox: port 80&lt;br /&gt;
** Rackspace Cloud: port 80&lt;br /&gt;
** FTP: port 21 (unless overridden)&lt;br /&gt;
** Email: port 25 (if using external mail server)&lt;br /&gt;
&lt;br /&gt;
==Scheduled Events Fail to Trigger/Using Real Cron to Trigger==&lt;br /&gt;
* The scheduled date is wrong and has not passed.&lt;br /&gt;
* Not enough visitors are visiting to trigger the schedule.  Someone must visit any page on the WordPress site on or after the scheduled time for the event to occur.  If no one visits during the time-frame then the event may be missed or occur at an unscheduled time.&lt;br /&gt;
** Can force a cron job to run in Cpanel by adding this line of code to a cron job if really need to: &amp;lt;pre&amp;gt; wget -q -O - http://DOMAIN/wp-cron.php 2&amp;amp;&amp;gt;1 /dev/null &amp;lt;/pre&amp;gt;&lt;br /&gt;
*** Source: http://www.siteground.com/tutorials/cpanel/cron_jobs.htm&lt;br /&gt;
* The backup is failing. Test manual backups.&lt;br /&gt;
&lt;br /&gt;
==Files not being sent remotely==&lt;br /&gt;
* Files may fail remote sending for two possible reasons:&lt;br /&gt;
** Files are too large to be transferred during the alotted PHP maximum runtime (usually 30 seconds).  This is defined by your host.&lt;br /&gt;
** Your host's firewall is blocking outgoing HTTP connections / transfers.&lt;br /&gt;
** The backup itself isn't completing - verify that they work manually.&lt;br /&gt;
* Solutions:&lt;br /&gt;
** Reduce backup file size by deleting files or excluding directories.&lt;br /&gt;
** Contact your host to increase PHP's maximum allowed runtime.&lt;br /&gt;
** Contact your host to unblock their firewall to allow outgoing HTTP connections.&lt;br /&gt;
&lt;br /&gt;
==Error 3382==&lt;br /&gt;
Check out [http://ithemes.com/codex/page/BackupBuddy:_Error_Codes#3382 Error 3382 Details]&lt;br /&gt;
&lt;br /&gt;
==Backup failure running function `` in email==&lt;br /&gt;
* Usually due to sending remote backups/databases failed due to permissions/path if ftp.&lt;br /&gt;
** If sending the files by email, then files are probably too large for email(typically up to 10mb by email allowed by most places)&lt;br /&gt;
&lt;br /&gt;
==Endless Ping on second Scheduling Cron==&lt;br /&gt;
* Database may be too large, lot of times this would be the wp_posts table.&lt;br /&gt;
** See if can lower size of database. The database size may be too big for your site/host/server to handle properly.&lt;br /&gt;
** Use Server Info inside BackupBuddy ( '''BackupBuddy --&amp;gt; Server Info.''' ) to check where the most disk space is being used.&lt;br /&gt;
** Increase available runtime. Your server may be timing out too quickly or having other issues related to not being allowed enough time to run scripts or specific commands.&lt;br /&gt;
** What revision retention policy do you operate on the posts? It may be that you have a lot of revisions stored in the database that you could safely remove. The WordPress Codex gives some information on controlling revisions (http://codex.wordpress.org/Editing_wp-config.php#Post_Revisions) but I don't think this acts retrospectively so you might need to find a method to prune any revisions you currently have.&lt;br /&gt;
** Many plugins tend to leave a lot of data behind even after they have been de-activated and deleted in WordPress. This can result in very large BackupBuddy backups.&lt;br /&gt;
***Example: A famous example of this is Statpress, which has been publicly known to leave massive amounts of data behind in the WordPress database tables even after the plugin was deactivated and deleted.&lt;br /&gt;
***Solutions: &lt;br /&gt;
**** Use Server Info inside BackupBuddy ( '''BackupBuddy --&amp;gt; Server Info.''' ) to check where the most disk space is being used in different WordPress database tables.&lt;br /&gt;
**** Another way to see if such plugins may be affecting and causing your Backup to fail is to look through the database and see where the most db space is being used. If any table with a lot of data exists and is related to a plugin you no longer use, you can drop or empty that table with something like phpMyAdmin.&lt;br /&gt;
****Also, if you have a &amp;quot;maintenance mode&amp;quot; plugin active, this can cause endless pinging as well. Deactivating this plugin solved the problem for some users.&lt;br /&gt;
***Make full Database backup with BackupBuddy before making any Database changes. :D&lt;br /&gt;
*Related links:&lt;br /&gt;
**[http://ithemes.com/forum/index.php?/topic/18066-backup-not-working-keepings-pinging/#p85085 Database size causing endless pings on second scheduling cron]&lt;br /&gt;
&lt;br /&gt;
==Fatal Error: Call to undefined function home_url()==&lt;br /&gt;
* Full error will be  Fatal Error: Call to undefined function home_url() in /wp-content/plugins/backupbuddy/classes/backup.php on line x&lt;br /&gt;
** BackupBuddy requires at least WordPress version 3.0, make sure you don't have an older version of WordPress.&lt;br /&gt;
&lt;br /&gt;
==Parse Error, unexpected T_VARIABLE in .../backupbuddy.php on line xxx==&lt;br /&gt;
* Usually will come up during activation of BackupBuddy&lt;br /&gt;
** Make sure you are using PHP5 and not PHP4.&lt;br /&gt;
** If you are installing by downloading BackupBuddy, unzipping, and then using FTP the directory in the site plugins directory sometimes the configuration of the FTP transfer mode can cause issues. You can try deleting the existing plugin files with the plugin admin and then install through WordPress admin by going through Plugins -&amp;gt; Add New -&amp;gt; Upload -&amp;gt; and use the backupbuddy.zip file. Be sure to do this with a copy of backupbuddy.zip that has not been unzipped.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Backed up files link shows 404 error==&lt;br /&gt;
&lt;br /&gt;
* This error is shown when you click on the generated backed up files. There is no error shown on the Backup page or in the logs, yet clicking the backup links show a 404 error or result in you not being able to download them because the files don't exist. This could be caused by several things. Mainly, this has been known to be caused by the following:&lt;br /&gt;
** There is an Archive limit set on the BackupBuddy --&amp;gt; Settings page. If this is being exceeded, the extra archives will be deleted. Try setting this to something higher.&lt;br /&gt;
** Set the total size limit ( max file size ) to a higher setting.&lt;br /&gt;
** See if any other plugin may be causing the issue. Disable other plugins and try starting the backup process again.&lt;br /&gt;
** Make sure you have the necessary permissions to the downloads folder where the file is being saved.&lt;br /&gt;
** Check with host to make sure they don't have an over-zealous security system or error in it&lt;br /&gt;
** Make sure the Advanced Log file in BackupBuddy is not showing any errors. If it is, post on the [http://ithemes.com/forum/backupbuddy/ forums] so that the error can be looked at.&lt;br /&gt;
&lt;br /&gt;
* Other threads with solutions listed above:&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/17196-full-backup-completes-but-does-not-go-to-backup-archives/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/17624-backupbuddy-full-backup-is-deleting-backup-file-after-creating-it/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/15013-download-error-message/&lt;br /&gt;
&lt;br /&gt;
==Change backups folder/file permissions or verify it is writable==&lt;br /&gt;
BackupBuddy needs the backups folder in your '''wp-content/uploads''' directory on your site to be writable so that BackupBuddy can easily create and modify backup and related files in that directory. If those permissions are not setup properly, either automatically or manually, you'll run into the &amp;quot;'''Unable to create backup storage directory'''&amp;quot; or similar errors.&lt;br /&gt;
*To verify and change any file or folder permissions:&lt;br /&gt;
**Easily and quickly learn what permissions are and how to change them in the official [http://codex.wordpress.org/Changing_File_Permissions WordPress File Permissions page]&lt;br /&gt;
**Ask your host to verify or do it for you.&lt;br /&gt;
**Make sure your backups folder directory in '''wp-content/uploads''' is set to 755 (permission).&lt;br /&gt;
**Make sure your '''wp-content/uploads''' folder and everything under/in it is set to 755 also (called recursive permissions OR changing permissions recursively).&lt;br /&gt;
*Support thread with detailed info&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/5270-backupbuddy-setting-permissions-and-security-implications/#p24242&lt;br /&gt;
&lt;br /&gt;
==Big backup files with both &amp;quot;Force Compatibility Mode&amp;quot; and PHP exec() function enabled==&lt;br /&gt;
*If PHP exec() function is enabled on your server AND you have &amp;quot;Force Compatibility Mode&amp;quot; setting enabled, you may run into backup file size issues. The compatibility mode does NOT support folder exclusions, and thus your backups may be very big.&lt;br /&gt;
*Solution:&lt;br /&gt;
**If your server has '''PHP exec() enabled''', go into '''BackupBuddy --&amp;gt; Settings''' and '''disable &amp;quot;Force Compatibility Mode&amp;quot;''' option.&lt;br /&gt;
*Related links with solution:&lt;br /&gt;
**http://ithemes.com/forum/index.php?/topic/18007-utterly-botched-wordpress-migration/&lt;br /&gt;
&lt;br /&gt;
==Dropbox Backups Not Arriving==&lt;br /&gt;
Sometimes, backups sent to Dropbox never arrive (meaning they never show up) in Dropbox.&lt;br /&gt;
*'''Possible reasons:'''&lt;br /&gt;
**Due to the Dropbox API limits, each backup file has to be loaded into your server's memory and then sent to Dropbox. Dropbox requires PHP oAuth. Because of that, your server may run out of the required memory to do other things at the same time. When your server does not have enough memory to do multiple things at once, it may take longer than usual to complete each task, and the Dropbox process may take longer than the allowed time in PHP maximum_execution_time. This will simply result in the Dropbox process to time out and cancel. Since the limitation is because Dropbox requires PHP oAuth, there is no current workaround other than more memory.&lt;br /&gt;
**BackupBuddy can only transfer full backup files that can easily or be fully loaded into your server's memory. So if your backup file size is 200mb BUT your server memory size is only 128mb, your server will not be able to handle such a backup transfer to Dropbox, even if Dropbox allows such a transfer. If a Dropbox transfer exceeds your server memory limits, the backup will definitely not be transferred properly or at all. This is a server limitation, usually on less powerful servers, that we're trying to find a fix for.&lt;br /&gt;
**Your server or site has file transfer or PHP script processing limits which is resulting in the transfer not finishing.&lt;br /&gt;
**Your Dropbox connection settings are wrong.&lt;br /&gt;
**Your server may not have enough memory to perform this transfer.&lt;br /&gt;
**Your backup is around or larger than 300mb. Dropbox has a 300mb file size limitation when uploading files online via a file. Dropbox has a limitation of 300mb per file size upload limit when done via anything other than the Desktop dropbox client. This limitation is thus imposed on BackupBuddy also by Dropbox.&lt;br /&gt;
*'''Solutions to try:'''&lt;br /&gt;
**Make sure your Dropbox connection settings are right.&lt;br /&gt;
**Delete your current Dropbox connection and then re-create the Dropbox connection. See if that works.&lt;br /&gt;
**Most important and basic thing to try: wait 10 to 15 minutes for the backup to arrive before giving up. Dropbox uploads can be slow due to Dropbox itself. Dropbox has been known to show files even 30 minutes after a backup file was sent.&lt;br /&gt;
**Ask your host to increase the PHP maximum_execution_time. This is usually 30 seconds. Try increasing it to something much higher temporarily to see if that makes any difference. &lt;br /&gt;
**Ask your host if your server can get more allotted memory.&lt;br /&gt;
**Ask your host to enable PHP error logging to a file that you can access.&lt;br /&gt;
***What this does is create an entry, in a txt file on your server that your host can tell you the location of, every time there is a PHP related error or warning. When DropBox times out, this file can most probably give you an exact error message that you can tell your host to address or fix.&lt;br /&gt;
**Try sending a smaller backup file OR simply a database backup file to Dropbox. You can also use the Exclude option to exclude folders and files you do not need or to test things. See if such smaller files arrive. If they do, your issue is definitely with the larger file sizes.&lt;br /&gt;
**Try excluding certain folders from the backups via '''BackupBuddy --&amp;gt; Settings''' and then see if the smaller-than-before backup files get to Dropbox. Dropbox has a limit of 300mb per file size upload when uploading any file through any channel other than the desktop client. Therefore, this 300mb max size per each file limit is imposed by Dropbox on BackupBuddy also. Excluding unwanted folders can help reduce your backup file sizes. &lt;br /&gt;
*'''Related links:'''&lt;br /&gt;
**http://ithemes.com/forum/index.php?/topic/18099-dropbox-not-working/#p85173&lt;br /&gt;
**http://ithemes.com/forum/index.php?/topic/17812-no-downloads-to-dropbox/#p83619&lt;br /&gt;
&lt;br /&gt;
==Database SQL (MySql) file inside full backups==&lt;br /&gt;
In full backups, the actual database is backed up also. To find this sql file, look for the following folder in your backup file after you have extracted/unzipped the backup zip file: &lt;br /&gt;
&lt;br /&gt;
wp-content/uploads/backupbuddy_temp/'''XXXXXXXX'''&lt;br /&gt;
&lt;br /&gt;
The '''XXXXXXXX''' part in the above link will be a serial code that matches the one in the backup name. That is it will be the exact same as the last set of characters, after the date, in your backup file name.&lt;br /&gt;
&lt;br /&gt;
For example, if your backup file name is:&lt;br /&gt;
&lt;br /&gt;
'''backup-domain_com-2012_05_29-''ukitenaifg''.zip'''&lt;br /&gt;
&lt;br /&gt;
then the folder inside a full backup where your database file is saved is&lt;br /&gt;
&lt;br /&gt;
wp-content/uploads/backupbuddy_temp/'''ukitenaifg'''&lt;br /&gt;
&lt;br /&gt;
==BackupBuddy Tab Missing in WordPress==&lt;br /&gt;
*If the BackupBuddy Tab is missing in your WordPress Admin area, there could be a few reasons for it:&lt;br /&gt;
**'''MULTISITES:''' If you are activating BackupBuddy on a single site inside a Multisite instead of using the NETWORK ACTIVATE option, BackupBuddy options will be hidden on purpose for security reasons. You must use [http://ithemes.com/codex/page/Installing_BackupBuddy#Multisite Network NETWORK ACTIVATE] instead.&lt;br /&gt;
**Try disabling other plugins which may be causing a conflict OR not allowing BackupBuddy tab to show up in WordPress admin area, even if direct links to such areas work.&lt;br /&gt;
&lt;br /&gt;
*Related links&lt;br /&gt;
**[http://ithemes.com/codex/page/Installing_BackupBuddy#Multisite Network Active BackupBuddy on Multisites]&lt;br /&gt;
**[http://ithemes.com/forum/index.php?/topic/18395-backupbuddy-installed-and-working-but-missing-from-wordpress-left-panel/ Plugin conflicts causing BackupBuddy to disappear in WordPress Admin panel]&lt;br /&gt;
&lt;br /&gt;
==Warning:xxxxxx: open_basedir restriction in effect. File(xxxxxxx) is not within allowed the path(s)....==&lt;br /&gt;
*Your server is configured to only allow scripts access to files in a certain directory. Your own files are not in this directory. This is a server configuration error (you should be able to access your own files) and your host should be able to fix it.&lt;br /&gt;
*http://www.php.net/manual/en/ini.core.php#ini.open-basedir&lt;br /&gt;
&lt;br /&gt;
==Warning:xxxxx:Unable to Access .../wp-content/uploads/backupbuddy_backups/temp_test_xxxxxxx.zip in /wp-content/... on line X==&lt;br /&gt;
* Usually immediately followed by a Warning: Cannot modify header information - headers already sent&lt;br /&gt;
* Happens most often when installing/activating BackupBuddy or after a migration.&lt;br /&gt;
*Solution:&lt;br /&gt;
** Make sure that the backupbuddy_backups folder does exist at /wp-content/uploads/, if it doesn't then create it.&lt;br /&gt;
** Also make sure permissions are set to 755 recursively for the /wp-content/uploads directory.&lt;br /&gt;
** Logging into the WordPress admin and navigating around a few BackupBuddy pages can trigger it to create the folder also.&lt;br /&gt;
*** Setting permissions to 777 temporarily can let give it a chance to create it if it was having trouble doing so for some reason.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Restoring/Migrating=&lt;br /&gt;
&lt;br /&gt;
==Importbuddy asking for an authentication password when it didn't used to==&lt;br /&gt;
Importbuddy did not used to have a mandatory password to be ran or downloaded. However, it does now as of version 2.2.33 of BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
If using an older file that you never set a password for that is now asking for a password then:&lt;br /&gt;
* Set a password for importbuddy in BackupBuddy's Settings page. Then download and use this new importbuddy.&lt;br /&gt;
&lt;br /&gt;
==No Next Step Button In Step 1==&lt;br /&gt;
If the server info section of step 1 is keeping the page from finishing loading (aka: no &amp;quot;Next Step&amp;quot; button) then can go to this URL as a workaround:&lt;br /&gt;
* ......./importbuddy.php?skip_serverinfo=true&lt;br /&gt;
&lt;br /&gt;
==Step 3 in import results in importbuddy.php file being downloaded when &amp;quot;Next Step&amp;quot; is clicked==&lt;br /&gt;
This problem happens because the .htaccess file being imported conflicts with the way your new host/server/site, where you are importing to, runs and processes php files. &lt;br /&gt;
&lt;br /&gt;
* To fix it, try any of the following (keep going through the steps till you solve the problem - the Second step below should solve the problem completely)&lt;br /&gt;
** First, make sure you have the latest version of BackupBuddy's importbuddy.php (gotten from the download link available on the BackupBuddy main Backup page.)&lt;br /&gt;
** Second, read this exact issue explained in detail on PluginBuddy http://pluginbuddy.com/site-migration-heaven-one/ That has detailed steps on how to solve this.&lt;br /&gt;
** Third, AFTER you encounter the problem, since the importbuddy.php file already has extracted the files:&lt;br /&gt;
*** Rename the .htaccess file in the newly extracted folder/area to anything like .htaccess_backup &lt;br /&gt;
*** Restart the import process again. &lt;br /&gt;
*** This time, in the Advanced Tab, select the option to &amp;quot;Skip File Unzip&amp;quot;, since the files have already been extracted. &lt;br /&gt;
*** After the site has been restored, go into your Settings --&amp;gt; Permalinks area to simply save that page, without making any changes. That will recreate the necessary .htaccess file again for the newly imported file.&lt;br /&gt;
** Make sure all file, folder and any other permissions are set properly before and after the backup and restore.&lt;br /&gt;
* This is probably the SAME as the other issue of [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Importbuddy.php_shows_ACTUAL_file_contents_instead_of_the_next_step Importbuddy showing actual file contents instead of the next step]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You should now be able to pass Step 3 without any issues.&lt;br /&gt;
&lt;br /&gt;
* Similar pages/threads with solutions:&lt;br /&gt;
** http://pluginbuddy.com/site-migration-heaven-one/ &lt;br /&gt;
**  http://ithemes.com/forum/index.php?/topic/17933-backupbuddy-after-step-3-downloads-importbuddyphp/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/13350-step-3-click-next-step-downloads-a-file-does-not-go-to-step-4/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/15420-impurtbuddy-step-3-problem/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/16443-cant-get-past-step-3-asks-to-download-importbuddyphp-over-and-over/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/13375-rackspace-server-cant-migrate-to-it-using-importbuddy/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/13660-help-with-migration/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/14350-cannot-move-past-step-3-in-migration/&lt;br /&gt;
** [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Importbuddy.php_shows_ACTUAL_file_contents_instead_of_the_next_step Importbuddy showing actual file contents instead of the next step]&lt;br /&gt;
&lt;br /&gt;
=='''Parse error''': syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /.../importbuddy.php on line 7974 (or any line)==&lt;br /&gt;
This error usually means that your site/server, where you are importing to, is running PHP4. BackupBuddy and importbuddy.php require at least PHP5 to function properly. &lt;br /&gt;
*It's usually easily fixable:&lt;br /&gt;
** Make sure you are using PHP5 and not PHP4.&lt;br /&gt;
** Change your PHP settings yourself to run PHP5.&lt;br /&gt;
** Ask your host to make sure you're running PHP5.&lt;br /&gt;
*Related customer thread with solution&lt;br /&gt;
**http://ithemes.com/forum/index.php?/topic/18009-parse-error/&lt;br /&gt;
&lt;br /&gt;
==Extraction of zip files (unzipping) does not work==&lt;br /&gt;
&lt;br /&gt;
Sometimes your host or site setup may prevent importbuddy.php from extracting (unzipping) the backup file. &lt;br /&gt;
&lt;br /&gt;
Here are 2 manual solutions, one via FTP and one via cPanel, on unzipping the files manually and then continuing the importbuddy.php process. Try either of the following:&lt;br /&gt;
&lt;br /&gt;
* http://pluginbuddy.com/restoring-an-unzipped-backup-with-backupbuddy/&lt;br /&gt;
* http://pluginbuddy.com/tutorials/unzip-backup-zip-file-in-cpanel/&lt;br /&gt;
&lt;br /&gt;
IMPORTANT: Make sure you choose &amp;quot;Skip zip file extraction&amp;quot;, under the &amp;quot;Advanced Configuration Options&amp;quot; tab on Step 1, to tell importbuddy.php to SKIP the extraction process. The import should work fine then while skipping the extraction process.&lt;br /&gt;
&lt;br /&gt;
==Old importbuddy overwriting on unzip==&lt;br /&gt;
* Possible Symptoms:&lt;br /&gt;
** importbuddy behaves differently or stops functioning properly after the extraction step.&lt;br /&gt;
** Weird errors are seen after the extraction step.&lt;br /&gt;
** The importbuddy version at the bottom of importbuddy changes after the extraction step.&lt;br /&gt;
** Error: &amp;quot;Error! The unzip process reported success but the backup data file, backupbuddy_dat.php was not found in the extracted files. The unzip process either failed (most likely) or the zip file is not a proper BackupBuddy backup.&amp;quot;&lt;br /&gt;
** Error 9003.&lt;br /&gt;
* Possible Solutions:&lt;br /&gt;
** Open the backup ZIP and delete the importbuddy.php file within it.&lt;br /&gt;
** Replace the importbuddy.php on your server after the extraction step but before moving forward further.&lt;br /&gt;
&lt;br /&gt;
==After import: The source site is now redirecting to the destination site (or vice versa):==&lt;br /&gt;
* This occurs if the new database settings were not entered during Step 3 of importbuddy.php.  Because of this, both sites are now sharing the same database so one of them (usually source) is redirecting to the other (usually destination).  importbuddy.php needs to be re-run inputting the source URL on Step 3 and using the source database settings.  This will reconfigure the source database to use its proper URL.  Next importbuddy.php needs to be run again inputting the destination URL on Step 3 with the NEW database settings for the new database.  This way both sites will have their own database for their respective URLs.&lt;br /&gt;
* importbuddy no longer overwrites existing WordPress databases by default so this issue is not as common as it used to be.&lt;br /&gt;
&lt;br /&gt;
==After import: WordPress Error: `You do not have sufficient permissions to access this page`==&lt;br /&gt;
One or more of your database table prefixes did not get changed during migration. A fix is available here: http://www.tech-evangelist.com/2010/02/06/wordpress-error-sufficient-permissions/&lt;br /&gt;
&lt;br /&gt;
==Cannot Log-in and Keep Getting Redirected Back to Log-In Page==&lt;br /&gt;
The migration completed successfully and the site is browse-able but when you try to log in you keep getting redirected back to the log-in page and the URL looks something like this:&lt;br /&gt;
&amp;lt;pre&amp;gt;http://wptest.local/wp-login.php?redirect_to=http%3A%2F%2Fwptest.local%2Fwp-admin%2F&amp;amp;reauth=1&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This is a common WordPress related issue and not a result of BackupBuddy backup or restore/import. It is easily fixable, though, and happens mainly because of some plugin or custom edit somewhere in WordPress causing WordPress to keep redirecting to a specific url for admin login.&lt;br /&gt;
&lt;br /&gt;
* Solutions (try any of these to see if they work - make a backup of everything Or keep you BackupBuddy backup in case something goes wrong or you want to undo some changes you make below):&lt;br /&gt;
** Edit W3 Total Cache settings to fix this, if you are using or have used W3 Total Cache. Please check in your wp-config.php for a line such as this:&amp;lt;pre&amp;gt;define('COOKIE_DOMAIN', 'www.domain.com'); // Added by W3 Total Cache&amp;lt;/pre&amp;gt; In order to be able to log-in please either delete the line; or comment out the line; or change the string 'www.domain.com' to false - note that false is not enclosed by quotes, e.g.,: &amp;lt;pre&amp;gt;define('COOKIE_DOMAIN', false); // Added by W3 Total Cache&amp;lt;/pre&amp;gt; You will now be able to log-in and can then attend to updating this definition as required by your new site configuration. To read more about COOKIE_DOMAIN please visit: [http://codex.wordpress.org/Editing_wp-config.php#Set_Cookie_Domain WordPress Codex - Cooke Domain]&lt;br /&gt;
** Make sure your wp-config.php files does NOT have any hard-coded SITE or WordPress URI that may be causing this issue.&lt;br /&gt;
** Make sure there is no duplicate .htaccess file.&lt;br /&gt;
** Make sure the existing .htaccess file does not contain anything related to the Site or WordPress URL that is causing the redirect.&lt;br /&gt;
** Make sure the wp_options table does not have any OLD url's which were NOT updated prior to the move.&lt;br /&gt;
** Make sure you use the latest versions of BackupBuddy and importbuddy.php (even try importbuddy.php beta to see if that makes a difference)&lt;br /&gt;
** Disable conflicting/all plugins by renaming the folder names of the individual plugins to something different.&lt;br /&gt;
&lt;br /&gt;
* Some good posts with good/alternate solutions/info on this:&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/14324-getting-redirected-when-trying-to-login/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/14102-new-site-wp-admin-redirect-back-to-original-sites-wp-admin/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/13581-access-admin-backend/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/17383-wp-content-files-on-subdomain-redirect-to-root/&lt;br /&gt;
** http://codex.wordpress.org/Login_Trouble&lt;br /&gt;
** http://wordpress.org/support/topic/keeps-redirecting-when-logging-in&lt;br /&gt;
** http://codex.wordpress.org/Editing_wp-config.php#Set_Cookie_Domain&lt;br /&gt;
** [http://wordpress.org/support/topic/domain-redirection-keeps-forwarding-to-signup-page Multisite Redirects]&lt;br /&gt;
&lt;br /&gt;
==Blank OR strange homepage/frontpage BUT admin area works perfectly==&lt;br /&gt;
This usually happens when there is an existing and unwanted index.html, default.html or some other server default file already in the root of WordPress directory of your new restore/migrated site. &lt;br /&gt;
*Solution: &lt;br /&gt;
**Make sure your .htaccess file is not causing the issue.&lt;br /&gt;
**Make sure you delete any extra index.html, default.html or any other server default file that is already in the root of the WordPress directory of your newly restored/migrated site.&lt;br /&gt;
**Make sure your WordPress's index.php file is correct. If not, you can always download the latest version from WordPress.org and use the index.php file from that download (with any changes you may have made to the existing index.php file) to replace the index.php already present in your site.&lt;br /&gt;
**Make sure your theme's index.php and other theme files contents and permissions are correct.&lt;br /&gt;
**Make sure your theme settings in the WordPress admin section are correct. &lt;br /&gt;
** Make sure the home URL got updated in the database.&lt;br /&gt;
*** Can also use RepairBuddy to verify home URL.&lt;br /&gt;
*Related customer thread with easy solution:&lt;br /&gt;
**http://ithemes.com/forum/index.php?/topic/17989-update-in-progress-after-migrate/&lt;br /&gt;
&lt;br /&gt;
==Links (permalinks) return 404 errors==&lt;br /&gt;
====Most Common====&lt;br /&gt;
* The [[.htaccess]] file was not configured properly or was not writable so importbuddy didn't update it.&lt;br /&gt;
** Solution: Log in to the admin dashboard and navigate to: Settings -&amp;gt; Permalinks and click 'Save Changes'. This regenerates your .htaccess entries correcting most problems.&lt;br /&gt;
* To manually fix, edit the [[.htaccess]] file in a text editor following the format on the [[.htaccess]] page.&lt;br /&gt;
* If getting this after a migration in which it redirected you to home page during the migration's step 5&lt;br /&gt;
** Cause: .htaccess file is causing redirections.&lt;br /&gt;
** Solution:&lt;br /&gt;
*** 1) Redo import and pause after Step 2 (file extraction).&lt;br /&gt;
*** 2) After step 2 (but before continuing to step 3) delete the .htaccess file in the root of the site.&lt;br /&gt;
*** 3) Continue the import to completion&lt;br /&gt;
*** 4) Regenerate the .htaccess file in WordPress by going to Settings -&amp;gt; Permalinks -&amp;gt; and clicking to &amp;quot;Save Changes&amp;quot;&lt;br /&gt;
* If using custom permalinks, try default ones to see if the issue is tied to the custom permalinks.&lt;br /&gt;
* [http://codex.wordpress.org/Using_Permalinks#Fixing_Permalink_Problems See WordPress' official page on Fixing Permalinks for more solutions.]&lt;br /&gt;
&lt;br /&gt;
====Users of XAMPP (Windows)====&lt;br /&gt;
Some versions of XAMPP do not enable mod_rewrite by default (though it is compiled in Apache). To enable it — and thus enable WordPress to write the .htaccess file needed to create pretty permalinks — you must open apache/conf/httpd.conf and uncomment the line LoadModule rewrite_module modules/mod_rewrite.so (i.e., delete the hash/pound sign at the front of the line).&lt;br /&gt;
====Users of WAMP (Windows)====&lt;br /&gt;
Some versions of WAMP (all versions?) do not enable mod_rewrite or permit following SymLinks by default. To enable the required functionality navigate to the apache/conf/httpd.conf file, open with a text editor and uncomment the line LoadModule rewrite_module modules/mod_rewrite.so (i.e., delete the hash/pound sign at the front of the line). Then further down in the same file there is a section that starts with the line &amp;quot;Options FollowSymlinks&amp;quot;. Change the second line in that section from &amp;quot;AllowOverride none&amp;quot; to AllowOverride all. Save edited httpd.conf and restart all WAMP modules. Your permalinks should now work. &lt;br /&gt;
====Users of Ubuntu + Apache====&lt;br /&gt;
The packaged version of Apache that came down with apt-get lamp-server^ doesn't enable mod_rewrite by default.  [http://serverfault.com/questions/139791/how-can-i-enable-mod-rewrite-in-apache-on-ubuntu This link is a step in the right direction], although you also might have to set the AllowOverride rules to &amp;quot;all&amp;quot; in /etc/apache2/sites-enabled/000-default.  Also, after making those changes make sure to restart Apache.  -- In summary, the steps that helped me fix this problem were:  1) Enable mod_rewrite on Apache, 2) Restart Apache, 3) Rename .htaccess to .htaccess.bak (move it out of the way), 4) Regenerate the .htaccess file (as above) --&amp;gt; login to your admin dashboard and go to Settings -&amp;gt; Permalinks -&amp;gt; and click the &amp;quot;Save Changes&amp;quot; button.&lt;br /&gt;
&lt;br /&gt;
====500 Server Errors====&lt;br /&gt;
* [[.htaccess]] (click for details) file is invalid or contains unsupported directives. Often an &amp;quot;AddHandler&amp;quot; line exists from the source server that is not supported on the new destination server.&lt;br /&gt;
** Regnerating the .htaccess file can solve. To do this login to your admin dashboard and go to Settings -&amp;gt; Permalinks -&amp;gt; and click the &amp;quot;Save Changes&amp;quot; button.&lt;br /&gt;
*** Note: You don't have to actually make any changes on the page to regenerate the .htaccess in this manner by clicking to &amp;quot;Save Changes&amp;quot;.&lt;br /&gt;
** Optionally manually edit the [[.htaccess]] file in a text editor following the format on the [[.htaccess]] page.&lt;br /&gt;
* Invalid file permissions such as being too restrictive OR too open. Some servers throw a 500 error if permissions are set to 777 to prevent accidental unauthorized access.&lt;br /&gt;
** If permissions are currently set to 777 try changing them to 644 recursively on the site.&lt;br /&gt;
* PHP is not functioning or enabled for the site. Check with basic [[phpinfo()]].&lt;br /&gt;
* A 404 error is occurring but the server is not set up correctly to return a 404&lt;br /&gt;
&lt;br /&gt;
*Related links:&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/18089-migration-failure-with-500-internal-server-error/&lt;br /&gt;
** [http://ithemes.com/forum/index.php?/topic/18445-restored-site-now-wont-load-and-cant-log-in/#p86642 Remove extra .htaccess lines which may be preventing the site from loading]&lt;br /&gt;
** [http://ithemes.com/forum/index.php?/topic/18607-internal-server-error-hostgator-rocks/ How HostGator helped a customer fix this error by simply fixing the bad .htaccess file]&lt;br /&gt;
&lt;br /&gt;
==.htaccess being overwritten on unzip==&lt;br /&gt;
* Symptoms:&lt;br /&gt;
** PHP stops properly functions in importbuddy.php after the extraction step.&lt;br /&gt;
** Weird errors are seen after the extraction step.&lt;br /&gt;
* Solution:&lt;br /&gt;
** Open the backup ZIP and delete the .htaccess file within it, can be done before migrating.&lt;br /&gt;
*** Can also delete the .htaccess file in directory after step 2&lt;br /&gt;
&lt;br /&gt;
==The backup zip file is not found==&lt;br /&gt;
* The zip file has been renamed to a non-BackupBuddy format.&lt;br /&gt;
* The zip file permissions are wrong. Ex: Not readable.&lt;br /&gt;
* The zip file is not in the same directory as importbuddy.php.&lt;br /&gt;
* The zip file has not finished uploading or was interrupted in transit. If BackupBuddy was used to send it try manually uploading.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==backupbuddy_dat.php OR db_1.sql was not found after extraction==&lt;br /&gt;
* You may be using an older version of importbuddy.php not compatible with your backup version. Try upgrading your importbuddy.php to the version in the latest BackupBuddy.&lt;br /&gt;
* You may have renamed your backup ZIP file. BackupBuddy depends on the naming format to determine where some data in the backup ZIP is stored. Rename your backup back to its original name.&lt;br /&gt;
* Your backup may be corrupt. Try manually unzipping to verify it extracts properly.&lt;br /&gt;
&lt;br /&gt;
==SQL error near WH==&lt;br /&gt;
* It is because the table does not have a mysql primary key or unique index&lt;br /&gt;
** If you have Gravity Forms and the problem is in _rg_form_meta then upgrade Gravity Forms to version 1.6+&lt;br /&gt;
&lt;br /&gt;
==Restoring database times out==&lt;br /&gt;
* You can try reducing the size of that database.&lt;br /&gt;
** Checking for extra large tables you don't need (such as deleted plugins leaving data behind).&lt;br /&gt;
** What revision retention policy do you operate on the posts? It may be that you have a lot of revisions stored in the database that you could safely remove. The WordPress Codex gives some information on controlling revisions (http://codex.wordpress.org/Editing_wp-config.php#Post_Revisions) but I don't think this acts retrospectively so you might need to find a method to prune any revisions you currently have. &lt;br /&gt;
* Seeing if host will increase memory limit and runtime can help as well.&lt;br /&gt;
&lt;br /&gt;
==Extracting ZIP times out / hangs==&lt;br /&gt;
* Unzipping was not able to complete due to the unzipping process taking longer than the maximum PHP allowed runtime (usually 30 seconds).&lt;br /&gt;
* Solutions:&lt;br /&gt;
** Manual Unzip Process:&lt;br /&gt;
*** Manually extract the ZIP file on your computer then upload the files to the server.&lt;br /&gt;
*** Restart the importbuddy.php Import process, selecting `Skip Zip Extraction` from the advanced options slide-down.&lt;br /&gt;
** Or ask your host to increase the maximum PHP runtime beyond its current limit.&lt;br /&gt;
&lt;br /&gt;
==Defined URL in wp-config.php==&lt;br /&gt;
* Symptoms:&lt;br /&gt;
** URL does not appear to update after migration.&lt;br /&gt;
** Links 404 after migration and you verified that you entered the correct URL to migrate to.&lt;br /&gt;
** Links can also redirect to old site at the defined URL, though usually they 404&lt;br /&gt;
** Cannot update url's in the admin area. Such fields are usually disabled, as WordPress disallows their editing if the home URL is in the wp-config.php file&lt;br /&gt;
&lt;br /&gt;
==URLs redirecting to old site after migration==&lt;br /&gt;
* Symptoms: Home page is up and looks fine but links in the site all keep going to the old/source site.&lt;br /&gt;
* Solution:&lt;br /&gt;
** Re-run importbuddy.php entering the correct URLs and watching for any errors.&lt;br /&gt;
** Also make sure import is finishing correctly, may be timing out without realizing it.&lt;br /&gt;
*** Can check the importbuddy.txt log to see if it caught something, will be located in same place you uploaded the importbuddy file.&lt;br /&gt;
** Check for any hardcoded/defined URLs in the site's wp-config.php and HTML files.&lt;br /&gt;
*** If site URL is hardcoded in theme HTML files can wrap them in home_url( '/directory/' ) to fix.&lt;br /&gt;
&lt;br /&gt;
==URL needs manually updated==&lt;br /&gt;
* Note that this does not update serialized data. In short, some plugins, such as PluginBuddy plugins may not have internal URLs updated. This is more of a last-choice solution.&lt;br /&gt;
* SQL to update URL in posts manually:&lt;br /&gt;
&amp;lt;pre class=&amp;quot;brush:html&amp;quot;&amp;gt;update wp_posts set post_content = replace(post_content, 'http://OLD_URL', 'http://NEW_URL');&amp;lt;/pre&amp;gt;&lt;br /&gt;
* Command line zip test to check if exec is enabled and zip can create a file. Download: [[Media:Zip_test.zip]]&lt;br /&gt;
* Safest way to mass search/replace URLs is to use a tool that is prepared to handle serialized data. [https://github.com/interconnectit/Search-Replace-DB Search-Replace-DB] is a well known open source tool to take care of this.&lt;br /&gt;
&lt;br /&gt;
==The unzip process reported success but the backup data file...==&lt;br /&gt;
&amp;quot;Error! The unzip process reported success but the backup data file,&lt;br /&gt;
backupbuddy_dat.php was not found in the extracted files. The unzip&lt;br /&gt;
process either failed (most likely) or the zip file is not a proper&lt;br /&gt;
BackupBuddy backup.&amp;quot;&lt;br /&gt;
* Most common cause: See [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Old_importbuddy_overwriting_on_unzip]&lt;br /&gt;
* The backup did not finish extracting (timed out).&lt;br /&gt;
* Verify the backup is not damaged.&lt;br /&gt;
&lt;br /&gt;
==Importbuddy.php shows ACTUAL file contents instead of the next step==&lt;br /&gt;
There is one report that on Step 4, importbuddy.php started showing the actual importbuddy.php file contents. The reason for this was that the EXTRACTED .htaccess file from the OLD server/site was causing the issue.&lt;br /&gt;
&lt;br /&gt;
This is VERY similar OR the same as [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Step_3_in_import_results_in_importbuddy.php_file_being_downloaded_when_.22Next_Step.22_is_clicked Step 3 downloading importbuddy.php file issue] which also contains possible reasons and solutions.&lt;br /&gt;
&lt;br /&gt;
*Solutions&lt;br /&gt;
**Check your .htaccess file on the OLD server/site and fix any issues with it. THEN do the backup.&lt;br /&gt;
**After Step 3 has finished, and BEFORE proceeding to Step 4 (or any such step where this problem happens), open a new window OR your FTP program, go and find the EXTRACTED .htaccess file, EDIT it to remove any UNWANTED directives, and then switch back to the importbuddy.php window to continue onto the next step.&lt;br /&gt;
**On the OLD site, ALSO try saving your Permalinks again in WordPress --&amp;gt; Permalinks . Simply click &amp;quot;Save&amp;quot; on that page and then do a backup and retry the import/restore/migration. &lt;br /&gt;
**Thanks to our customer Chris Malone for finding the issue and finding a solution right away too.&lt;br /&gt;
**As mentioned above, this is VERY similar OR the same as [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Step_3_in_import_results_in_importbuddy.php_file_being_downloaded_when_.22Next_Step.22_is_clicked Step 3 downloading importbuddy.php file issue] which also contains possible reasons and solutions.&lt;br /&gt;
&lt;br /&gt;
*Related link&lt;br /&gt;
**[http://ithemes.com/forum/index.php?/topic/18621-wont-continue-past-step-3-when-running-importbuddy/ User reporting the issue and the solution]&lt;br /&gt;
**[http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Step_3_in_import_results_in_importbuddy.php_file_being_downloaded_when_.22Next_Step.22_is_clicked Step 3 downloading importbuddy.php file issue]&lt;br /&gt;
&lt;br /&gt;
=BackupBuddy Classic=&lt;br /&gt;
BackupBuddy Classic is available to download in case you have an older system OR older system specs like older PHP, MySql and other things. BackupBuddy Classic does not have any of the new features of BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
If your system or host forces you to use BackupBuddy Classic, you should start considering switching to another host or server ( we recommend [http://ithemes.com/hostgator HostGator] ) which is not old or not updated regularly.&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Classic can be found in your Member's area and is labeled &amp;quot;'''BackupBuddy Classic'''.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*Related Link&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/18448-download-legacy-versions-of-backupbuddy/#p86657&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]&lt;br /&gt;
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]&lt;br /&gt;
# [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
# [http://pluginbuddy.com/support/ Support Forums]&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues</id>
		<title>BackupBuddy: Frequent Support Issues</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues"/>
				<updated>2013-02-13T23:53:02Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: /* Compatibility Mode */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Backing Up=&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==HTTP Loopback Connections Disabled==&lt;br /&gt;
* Also known as '''Endless Ping'''.&lt;br /&gt;
* This usually happens before the second Scheduled Cron in your backup is run. You can see the number of times &amp;quot;Scheduled Cron&amp;quot; is mentioned in the Advanced Logs shown on the backup page to see if this is the case.&lt;br /&gt;
* If your Server Information page reports that HTTP Loopback Connections are disabled or the following occurs (see below), you need to either enable HTTP Loopback Connections or enter the WordPress Alternate Cron setting in your wp-config.php file. This is caused if your host is blocking loopback connections within their firewall. You will need to request that your host change this (this is very standard to have this available), enable the alternate cron method in your wp-config.php (as Solution below - often the '''only''' solution for those in a shared environment), or move to a new host. &lt;br /&gt;
** If your backup progress (as detailed in the Advanced Details area) consistently '''never''' progresses beyond this point except for the continuous &amp;quot;pings&amp;quot;:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
Backing up with BackupBuddy v2.1.8...&lt;br /&gt;
20:35:15: Setting greedy script limits.&lt;br /&gt;
20:35:15: Set memory limit to 256M. Previous value &amp;lt; 256M.&lt;br /&gt;
20:35:15: Finished greedy script limits.&lt;br /&gt;
20:35:15: Full backup mode.&lt;br /&gt;
20:35:15: Performing pre-backup procedures.&lt;br /&gt;
20:35:15: Backup serial: pyisomo736&lt;br /&gt;
20:35:15: Creating import data file.&lt;br /&gt;
20:35:15: Finished creating import data file.&lt;br /&gt;
20:35:15: Finished pre-backup procedures.&lt;br /&gt;
20:35:15: Scheduling Cron for pyisomo736.&lt;br /&gt;
1307910918|ping&lt;br /&gt;
1307910922|ping&lt;br /&gt;
1307910926|ping&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
* Solution:&lt;br /&gt;
** Add define('ALTERNATE_WP_CRON', true); to your wp-config.php&lt;br /&gt;
*** Open your wp-config.php in a text editor. This file is located in the root of your site.&lt;br /&gt;
*** Add the line somewhere between the first ( &amp;lt;?php ) and last line of the file (but before the line that says /* That's all, stop editing! Happy blogging. */)&lt;br /&gt;
*** &amp;lt;pre&amp;gt;define('ALTERNATE_WP_CRON', true);&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Deactivate all other plugins and see if it works then, if so then make sure you don't have a plugin that may apply a maintenance mode&lt;br /&gt;
*** This is because maintenance mode plugins rarely, if ever, take into account WordPress scheduling crons&lt;br /&gt;
* See also&lt;br /&gt;
**[http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Endless_Ping_on_second_Scheduling_Cron Endless Ping on Second Scheduling Cron in BackupBuddy Codex]&lt;br /&gt;
**[http://codex.wordpress.org/Editing_wp-config.php#Alternative_Cron WordPress Codex / Alternative Cron on WordPress.org]&lt;br /&gt;
&lt;br /&gt;
* Related threads with same/similar solutions:&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/17385-backupbuddy-doesnt-backup-at-all-infinite-ping/&lt;br /&gt;
** http://ithemes.com/forum/backupbuddy/endless-pinging-v2-2-14&lt;br /&gt;
&lt;br /&gt;
=== On Linux Systems ===&lt;br /&gt;
On Linux systems, be sure you have your /etc/hosts file correctly setup as problems here can cause loopback not to work.&lt;br /&gt;
&lt;br /&gt;
==Compatibility Mode==&lt;br /&gt;
* If your server does not support command line Zip then BackupBuddy will fall back into a compatibility mode to help aid you in creating a backup. This mode is significantly slower and less reliable.  It is not intended for persistent use and is provided to aid you in backing up in poor hosting environments, for instance to move to another host.&lt;br /&gt;
* Directory exclusion is not available in this mode.  Even existing backups will be backed up, resulting in rapidly growing backup file sizes.&lt;br /&gt;
* If you are running on a Windows server (or developing locally, ie on Xampp) you will need to install the [http://pluginbuddy.com/wp-content/uploads/2010/05/backupbuddy_windows_unzip.zip Windows zip.exe executable] (we do not provide support for setting this up, though the readme.txt in the file does help).&lt;br /&gt;
* Solutions:&lt;br /&gt;
** If you are running CentOS on a VPS or similar type of server then running the command &amp;lt;pre&amp;gt;yum install zip&amp;lt;/pre&amp;gt; as root will install the zip package and any dependencies. This may also apply to other environments using rpm packages and the yum package manager front-end. The yum manager can also be used to query installed packages and update packages, etc. If you have any issues with this then please consult your host support for additional assistance.&lt;br /&gt;
** for Debian-based Linux (including Ubuntu) run the following at the command line: &amp;lt;pre&amp;gt;sudo apt-get install zip unzip&amp;lt;/pre&amp;gt;&lt;br /&gt;
** If you are operating a Media Temple DV server then please make sure you have the Developer Tools installed as this contains the package necessary to provide zip capability.&lt;br /&gt;
** If your server is configured to disable access to the PHP exec() function and if you have access to configure your server then remove any blocking of the PHP exec() function in php.ini and configure permissions to allow running the Linux command line function `zip`.&lt;br /&gt;
** If your server is operating in safe_mode then either turn safe_mode off (if you can) or make sure that the safe_mode_exec_dir configuration parameter includes the directory which contains the `zip` command (please consult your host support for this information)&lt;br /&gt;
** Ask your host to enable access to the Linux command line Zip command via PHP's exec() function.&lt;br /&gt;
*** Example message to send to your host:&lt;br /&gt;
&amp;lt;pre&amp;gt;Dear Sir/Madam,&lt;br /&gt;
&lt;br /&gt;
I am attempting to use the highly popular WordPress backup software, BackupBuddy by PluginBuddy.com.&lt;br /&gt;
BackupBuddy requires the ability to use the Linux command line Zip command via PHP's exec() function.&lt;br /&gt;
BackupBuddy is reporting that it is unable to access this functionality on my server hosting environment.&lt;br /&gt;
Please enable this functionality for me so that I may use this backup solution in combination with your hosting.&lt;br /&gt;
These are commonly available features of many popular hosting providers such as HostGator.com so it is&lt;br /&gt;
not unreasonable to request it nor is it a security risk IF it is properly configured.&lt;br /&gt;
&lt;br /&gt;
Please verify access to the following features:&lt;br /&gt;
1) PHP's exec() function.&lt;br /&gt;
2) Permission to run Linux's `zip` command.&lt;br /&gt;
3) The directory containing the `zip` command is included in the PATH environment variable&lt;br /&gt;
available to the process executing the command passed to the exec() function &lt;br /&gt;
&lt;br /&gt;
Thank you for your time and consideration.&amp;lt;/pre&amp;gt;&lt;br /&gt;
** Also possible that even though that zip via exec() is enabled it still may not work if host does not have zip's path location currently as a part of PATH (or the path is not one of the &amp;quot;well known&amp;quot; locations that more recent versions of BackupBuddy with search). The below code is an example of how to add the directory of the zip executable to PATH after you ask your host where it is being kept and whether this is the correct way to do it on their servers or if not what is the preferred way (please note the colon that precedes the path being added):&lt;br /&gt;
*** &amp;lt;pre&amp;gt;putenv( &amp;quot;PATH=&amp;quot; . getenv( 'PATH' ) . &amp;quot;:directory zip exe is&amp;quot; );&amp;lt;/pre&amp;gt;&lt;br /&gt;
*** The line has to be added anywhere in the wp-config.php file after the first line ( &amp;lt;?php ) but at least before the line that says /* That's all, stop editing! Happy Blogging */&lt;br /&gt;
** If all of the above are either impossible or unsuccessful and you absolutely must have the native zip command capability then you only option is to move your site to an alternative server or host that provides this capability.&lt;br /&gt;
&lt;br /&gt;
==Unable to create directory /public_html/yourdomain/wp-content/uploads/2012/03. Is its parent directory writable by the server?==&lt;br /&gt;
Happens when trying to activate/install BackupBuddy.&lt;br /&gt;
* Check in WordPress admin Settings-&amp;gt;Media under the Uploading Files heading and see if there is anything there. Generally if you are using the default location for wp-content they would be left blank.&lt;br /&gt;
* Also make sure there are not any references to another site in the wp-config.php file, some 1-click WordPress installers add definitions in there other servers don't like&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Warning: exec() has been disabled for security reasons in /www/wp-content/plugins/backupbuddy/lib/zip/zip.php on line ###==&lt;br /&gt;
* exec() is disabled somewhere in PHP configuration. Ask the host to correct this or use cPanel to edit PHP settings to enable it if possible. See 'Fallback to Compatibility Mode' above.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Warning: mysql_query() [function.mysql-query]: Unable to save result set in /www/wp-content/plugins/backupbuddy/backupbuddy.php on line 1673==&lt;br /&gt;
* See [http://ithemes.com/codex/page/BackupBuddy:_Error_Codes#9001 BackupBuddy Error Code 9001]&lt;br /&gt;
&lt;br /&gt;
==Godaddy Related==&lt;br /&gt;
* The bottom tier of Godaddy hosting services are known for not being able to complete backups within the maximum PHP runtime configured on their servers (usually 30 seconds), causing backups to fail.&lt;br /&gt;
* Solutions:&lt;br /&gt;
** Choose another quality hosting provider such as Hostgator.com (recommended)&lt;br /&gt;
** Upgrade to a higher tier of Godaddy hosting (not recommended as even better Godaddy servers are poor performers)&lt;br /&gt;
&lt;br /&gt;
==.htaccess 404 / Addhandler Warning==&lt;br /&gt;
* Some hosts use a line at the top of the .htaccess file in the root of the site to configure some server settings such as enabling PHP support for that site. When used on a host that does not need this it can break PHP or other functionality.  When migrating to a new site this can break the migration process. This often causes URLs to give 404 Not Found errors after migrating/restoring.&lt;br /&gt;
* Solution:&lt;br /&gt;
** Remove the Addhandler line from the .htaccess file before backup or open the backup ZIP archive and remove the line within the file within the ZIP.&lt;br /&gt;
&lt;br /&gt;
==Backup marked as bad==&lt;br /&gt;
* Backups are verified by verifying the following criteria:&lt;br /&gt;
** The ZIP file is not corrupt and is openable.&lt;br /&gt;
** The database (.sql) file exists.&lt;br /&gt;
** The wp-config.php file.&lt;br /&gt;
** The backupbuddy_dat.php file.&lt;br /&gt;
* Potential causes:&lt;br /&gt;
** The backup timed out and did not complete within the PHP maximum runtime (usually 30 seconds)&lt;br /&gt;
*** Solution: Reduce the backup size by deleting files or excluding one or more directories. You may use the `Server Information` page's Directory Size browser to find large directories/files.&lt;br /&gt;
** Your hosting account does not have enough free space available.&lt;br /&gt;
** You may have the backupbuddy_temp directory excluded.&lt;br /&gt;
&lt;br /&gt;
==Database backup succeeds, full fails==&lt;br /&gt;
* This is almost exclusively due any single step of the backup process not completing within the maximum PHP runtime (usually 30 seconds).&lt;br /&gt;
* If you are in compatibility mode then backups are significantly slower and less likely to complete in time.&lt;br /&gt;
* Solution:&lt;br /&gt;
** Ask your host to enable command line ZIP via exec() if you are in compatibility mode.&lt;br /&gt;
** Reduce the size of your backups by deleting files or excluding large directories.&lt;br /&gt;
&lt;br /&gt;
==Directories not being excluded==&lt;br /&gt;
* Directories are not excluded if BackupBuddy is being forced to fall into compatibility mode.  This is expected behaviour. This happens if command line Zip is unavailable via the PHP exec() function.&lt;br /&gt;
* Solutions:&lt;br /&gt;
** Contact your host and ask them if they can enable command line ZIP via exec() if using Linux. For Windows servers a zip.exe file is available by downloading it from the `Getting Started` page of BackupBuddy when running on a Windows host.&lt;br /&gt;
** Continue using compatibility mode. If you do this you will not be able to exclude directories, including the backups directory.  Because of this even backups will be backed up. We recommend not storing any backups locally in this case as your backup file sizes will increase exponentially.&lt;br /&gt;
&lt;br /&gt;
==Tempory files in directories/root==&lt;br /&gt;
* BackupBuddy creates several temporary files within the directory `/wp-content/uploads/backupbuddy_temp/` while generating a backup.  Some of these may remain temporarily after backups complete though most are cleaned up immeditately.  BackupBuddy will automatically clean up any remaining temporary files within 12 hours. This is an automated process.&lt;br /&gt;
* While in compatibility mode large sites can create temporary .gz files in the site root.  Sometimes these may be left behind and require manual cleanup at this time.  This is uncommon and is a result of not having command line ZIP via exec() available. Ask your host to enable this.&lt;br /&gt;
* Solution:&lt;br /&gt;
** Wait ~12 hours or delete the file(s) manually.&lt;br /&gt;
&lt;br /&gt;
==Backups Time Out / Marked as Bad==&lt;br /&gt;
* Backup file size is too large so it takes too many resources or too much time to finish so the process is killed.&lt;br /&gt;
* The maximum PHP runtime is typically 30 seconds so backups must finish within this time period.&lt;br /&gt;
* Try reducing backup size, excluding directories, disabling compression to speed up zip file generation, or getting host to enable native zip compression if not already enabled.&lt;br /&gt;
* Backup completed but backup ZIP is incomplete / bad: exec() shares the maximum allowed memory usage with PHP. If this memory limit is met the exec() / proc() will be killed and return to PHP. The symptoms of this are a bad / incomplete ZIP file despite the backup fully completing successfully. Try increasing `memory_limit` to a larger size.&lt;br /&gt;
** &amp;lt;table border=&amp;quot;1&amp;quot;&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;&amp;amp;nbsp;&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;exec()&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;proc()&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Maximum PHP Runtime Timeout&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Zip file size stops increasing.&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Zip file size stops increasing&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Memory Limit Hit&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Zip creation completed but ZIP file&amp;lt;br&amp;gt;incomplete &amp;amp; marked as bad&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Zip file size stops increasing.&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&amp;lt;/table&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Zip File Creation Dies at 2GB==&lt;br /&gt;
* The limit of some file systems on a 32bit server can create a file is 2GB.&lt;br /&gt;
** Ask host to user a better file system that allows for the creation and handling of files bigger than 2GB.&lt;br /&gt;
*** Large File Systems (LFS) don't technically have limits on how big they can support, they are designed to expand.&lt;br /&gt;
&lt;br /&gt;
==Zip File Creation Dies at ~4GB==&lt;br /&gt;
* On a 32bit server the limit for Zip Archive is about 4GB.&lt;br /&gt;
** Ask host to upgrade to 64bit.&lt;br /&gt;
** Host may be able to use better configurations or software for the server to up this while staying on 32bit though I am unsure on the details&lt;br /&gt;
&lt;br /&gt;
==Remote Transfers Fail==&lt;br /&gt;
* Login credentials are wrong. Test them to be sure that they have not changed.  This is exceedingly common.&lt;br /&gt;
* The path entered is incorrect or the directory has not been created.  BackupBuddy requires the path/bucket to already exist in some cases.&lt;br /&gt;
* Some hosts block outgoing connections. Try another remote destination if possible. Most remote destinations transfer over the HTTP port 80.&lt;br /&gt;
** Amazon S3: port 80&lt;br /&gt;
** Dropbox: port 80&lt;br /&gt;
** Rackspace Cloud: port 80&lt;br /&gt;
** FTP: port 21 (unless overridden)&lt;br /&gt;
** Email: port 25 (if using external mail server)&lt;br /&gt;
&lt;br /&gt;
==Scheduled Events Fail to Trigger/Using Real Cron to Trigger==&lt;br /&gt;
* The scheduled date is wrong and has not passed.&lt;br /&gt;
* Not enough visitors are visiting to trigger the schedule.  Someone must visit any page on the WordPress site on or after the scheduled time for the event to occur.  If no one visits during the time-frame then the event may be missed or occur at an unscheduled time.&lt;br /&gt;
** Can force a cron job to run in Cpanel by adding this line of code to a cron job if really need to: &amp;lt;pre&amp;gt; wget -q -O - http://DOMAIN/wp-cron.php 2&amp;amp;&amp;gt;1 /dev/null &amp;lt;/pre&amp;gt;&lt;br /&gt;
*** Source: http://www.siteground.com/tutorials/cpanel/cron_jobs.htm&lt;br /&gt;
* The backup is failing. Test manual backups.&lt;br /&gt;
&lt;br /&gt;
==Files not being sent remotely==&lt;br /&gt;
* Files may fail remote sending for two possible reasons:&lt;br /&gt;
** Files are too large to be transferred during the alotted PHP maximum runtime (usually 30 seconds).  This is defined by your host.&lt;br /&gt;
** Your host's firewall is blocking outgoing HTTP connections / transfers.&lt;br /&gt;
** The backup itself isn't completing - verify that they work manually.&lt;br /&gt;
* Solutions:&lt;br /&gt;
** Reduce backup file size by deleting files or excluding directories.&lt;br /&gt;
** Contact your host to increase PHP's maximum allowed runtime.&lt;br /&gt;
** Contact your host to unblock their firewall to allow outgoing HTTP connections.&lt;br /&gt;
&lt;br /&gt;
==Error 3382==&lt;br /&gt;
Check out [http://ithemes.com/codex/page/BackupBuddy:_Error_Codes#3382 Error 3382 Details]&lt;br /&gt;
&lt;br /&gt;
==Backup failure running function `` in email==&lt;br /&gt;
* Usually due to sending remote backups/databases failed due to permissions/path if ftp.&lt;br /&gt;
** If sending the files by email, then files are probably too large for email(typically up to 10mb by email allowed by most places)&lt;br /&gt;
&lt;br /&gt;
==Endless Ping on second Scheduling Cron==&lt;br /&gt;
* Database may be too large, lot of times this would be the wp_posts table.&lt;br /&gt;
** See if can lower size of database. The database size may be too big for your site/host/server to handle properly.&lt;br /&gt;
** Use Server Info inside BackupBuddy ( '''BackupBuddy --&amp;gt; Server Info.''' ) to check where the most disk space is being used.&lt;br /&gt;
** Increase available runtime. Your server may be timing out too quickly or having other issues related to not being allowed enough time to run scripts or specific commands.&lt;br /&gt;
** What revision retention policy do you operate on the posts? It may be that you have a lot of revisions stored in the database that you could safely remove. The WordPress Codex gives some information on controlling revisions (http://codex.wordpress.org/Editing_wp-config.php#Post_Revisions) but I don't think this acts retrospectively so you might need to find a method to prune any revisions you currently have.&lt;br /&gt;
** Many plugins tend to leave a lot of data behind even after they have been de-activated and deleted in WordPress. This can result in very large BackupBuddy backups.&lt;br /&gt;
***Example: A famous example of this is Statpress, which has been publicly known to leave massive amounts of data behind in the WordPress database tables even after the plugin was deactivated and deleted.&lt;br /&gt;
***Solutions: &lt;br /&gt;
**** Use Server Info inside BackupBuddy ( '''BackupBuddy --&amp;gt; Server Info.''' ) to check where the most disk space is being used in different WordPress database tables.&lt;br /&gt;
**** Another way to see if such plugins may be affecting and causing your Backup to fail is to look through the database and see where the most db space is being used. If any table with a lot of data exists and is related to a plugin you no longer use, you can drop or empty that table with something like phpMyAdmin.&lt;br /&gt;
****Also, if you have a &amp;quot;maintenance mode&amp;quot; plugin active, this can cause endless pinging as well. Deactivating this plugin solved the problem for some users.&lt;br /&gt;
***Make full Database backup with BackupBuddy before making any Database changes. :D&lt;br /&gt;
*Related links:&lt;br /&gt;
**[http://ithemes.com/forum/index.php?/topic/18066-backup-not-working-keepings-pinging/#p85085 Database size causing endless pings on second scheduling cron]&lt;br /&gt;
&lt;br /&gt;
==Fatal Error: Call to undefined function home_url()==&lt;br /&gt;
* Full error will be  Fatal Error: Call to undefined function home_url() in /wp-content/plugins/backupbuddy/classes/backup.php on line x&lt;br /&gt;
** BackupBuddy requires at least WordPress version 3.0, make sure you don't have an older version of WordPress.&lt;br /&gt;
&lt;br /&gt;
==Parse Error, unexpected T_VARIABLE in .../backupbuddy.php on line xxx==&lt;br /&gt;
* Usually will come up during activation of BackupBuddy&lt;br /&gt;
** Make sure you are using PHP5 and not PHP4.&lt;br /&gt;
** If you are installing by downloading BackupBuddy, unzipping, and then using FTP the directory in the site plugins directory sometimes the configuration of the FTP transfer mode can cause issues. You can try deleting the existing plugin files with the plugin admin and then install through WordPress admin by going through Plugins -&amp;gt; Add New -&amp;gt; Upload -&amp;gt; and use the backupbuddy.zip file. Be sure to do this with a copy of backupbuddy.zip that has not been unzipped.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Backed up files link shows 404 error==&lt;br /&gt;
&lt;br /&gt;
* This error is shown when you click on the generated backed up files. There is no error shown on the Backup page or in the logs, yet clicking the backup links show a 404 error or result in you not being able to download them because the files don't exist. This could be caused by several things. Mainly, this has been known to be caused by the following:&lt;br /&gt;
** There is an Archive limit set on the BackupBuddy --&amp;gt; Settings page. If this is being exceeded, the extra archives will be deleted. Try setting this to something higher.&lt;br /&gt;
** Set the total size limit ( max file size ) to a higher setting.&lt;br /&gt;
** See if any other plugin may be causing the issue. Disable other plugins and try starting the backup process again.&lt;br /&gt;
** Make sure you have the necessary permissions to the downloads folder where the file is being saved.&lt;br /&gt;
** Check with host to make sure they don't have an over-zealous security system or error in it&lt;br /&gt;
** Make sure the Advanced Log file in BackupBuddy is not showing any errors. If it is, post on the [http://ithemes.com/forum/backupbuddy/ forums] so that the error can be looked at.&lt;br /&gt;
&lt;br /&gt;
* Other threads with solutions listed above:&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/17196-full-backup-completes-but-does-not-go-to-backup-archives/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/17624-backupbuddy-full-backup-is-deleting-backup-file-after-creating-it/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/15013-download-error-message/&lt;br /&gt;
&lt;br /&gt;
==Change backups folder/file permissions or verify it is writable==&lt;br /&gt;
BackupBuddy needs the backups folder in your '''wp-content/uploads''' directory on your site to be writable so that BackupBuddy can easily create and modify backup and related files in that directory. If those permissions are not setup properly, either automatically or manually, you'll run into the &amp;quot;'''Unable to create backup storage directory'''&amp;quot; or similar errors.&lt;br /&gt;
*To verify and change any file or folder permissions:&lt;br /&gt;
**Easily and quickly learn what permissions are and how to change them in the official [http://codex.wordpress.org/Changing_File_Permissions WordPress File Permissions page]&lt;br /&gt;
**Ask your host to verify or do it for you.&lt;br /&gt;
**Make sure your backups folder directory in '''wp-content/uploads''' is set to 755 (permission).&lt;br /&gt;
**Make sure your '''wp-content/uploads''' folder and everything under/in it is set to 755 also (called recursive permissions OR changing permissions recursively).&lt;br /&gt;
*Support thread with detailed info&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/5270-backupbuddy-setting-permissions-and-security-implications/#p24242&lt;br /&gt;
&lt;br /&gt;
==Big backup files with both &amp;quot;Force Compatibility Mode&amp;quot; and PHP exec() function enabled==&lt;br /&gt;
*If PHP exec() function is enabled on your server AND you have &amp;quot;Force Compatibility Mode&amp;quot; setting enabled, you may run into backup file size issues. The compatibility mode does NOT support folder exclusions, and thus your backups may be very big.&lt;br /&gt;
*Solution:&lt;br /&gt;
**If your server has '''PHP exec() enabled''', go into '''BackupBuddy --&amp;gt; Settings''' and '''disable &amp;quot;Force Compatibility Mode&amp;quot;''' option.&lt;br /&gt;
*Related links with solution:&lt;br /&gt;
**http://ithemes.com/forum/index.php?/topic/18007-utterly-botched-wordpress-migration/&lt;br /&gt;
&lt;br /&gt;
==Dropbox Backups Not Arriving==&lt;br /&gt;
Sometimes, backups sent to Dropbox never arrive (meaning they never show up) in Dropbox.&lt;br /&gt;
*'''Possible reasons:'''&lt;br /&gt;
**Due to the Dropbox API limits, each backup file has to be loaded into your server's memory and then sent to Dropbox. Dropbox requires PHP oAuth. Because of that, your server may run out of the required memory to do other things at the same time. When your server does not have enough memory to do multiple things at once, it may take longer than usual to complete each task, and the Dropbox process may take longer than the allowed time in PHP maximum_execution_time. This will simply result in the Dropbox process to time out and cancel. Since the limitation is because Dropbox requires PHP oAuth, there is no current workaround other than more memory.&lt;br /&gt;
**BackupBuddy can only transfer full backup files that can easily or be fully loaded into your server's memory. So if your backup file size is 200mb BUT your server memory size is only 128mb, your server will not be able to handle such a backup transfer to Dropbox, even if Dropbox allows such a transfer. If a Dropbox transfer exceeds your server memory limits, the backup will definitely not be transferred properly or at all. This is a server limitation, usually on less powerful servers, that we're trying to find a fix for.&lt;br /&gt;
**Your server or site has file transfer or PHP script processing limits which is resulting in the transfer not finishing.&lt;br /&gt;
**Your Dropbox connection settings are wrong.&lt;br /&gt;
**Your server may not have enough memory to perform this transfer.&lt;br /&gt;
**Your backup is around or larger than 300mb. Dropbox has a 300mb file size limitation when uploading files online via a file. Dropbox has a limitation of 300mb per file size upload limit when done via anything other than the Desktop dropbox client. This limitation is thus imposed on BackupBuddy also by Dropbox.&lt;br /&gt;
*'''Solutions to try:'''&lt;br /&gt;
**Make sure your Dropbox connection settings are right.&lt;br /&gt;
**Delete your current Dropbox connection and then re-create the Dropbox connection. See if that works.&lt;br /&gt;
**Most important and basic thing to try: wait 10 to 15 minutes for the backup to arrive before giving up. Dropbox uploads can be slow due to Dropbox itself. Dropbox has been known to show files even 30 minutes after a backup file was sent.&lt;br /&gt;
**Ask your host to increase the PHP maximum_execution_time. This is usually 30 seconds. Try increasing it to something much higher temporarily to see if that makes any difference. &lt;br /&gt;
**Ask your host if your server can get more allotted memory.&lt;br /&gt;
**Ask your host to enable PHP error logging to a file that you can access.&lt;br /&gt;
***What this does is create an entry, in a txt file on your server that your host can tell you the location of, every time there is a PHP related error or warning. When DropBox times out, this file can most probably give you an exact error message that you can tell your host to address or fix.&lt;br /&gt;
**Try sending a smaller backup file OR simply a database backup file to Dropbox. You can also use the Exclude option to exclude folders and files you do not need or to test things. See if such smaller files arrive. If they do, your issue is definitely with the larger file sizes.&lt;br /&gt;
**Try excluding certain folders from the backups via '''BackupBuddy --&amp;gt; Settings''' and then see if the smaller-than-before backup files get to Dropbox. Dropbox has a limit of 300mb per file size upload when uploading any file through any channel other than the desktop client. Therefore, this 300mb max size per each file limit is imposed by Dropbox on BackupBuddy also. Excluding unwanted folders can help reduce your backup file sizes. &lt;br /&gt;
*'''Related links:'''&lt;br /&gt;
**http://ithemes.com/forum/index.php?/topic/18099-dropbox-not-working/#p85173&lt;br /&gt;
**http://ithemes.com/forum/index.php?/topic/17812-no-downloads-to-dropbox/#p83619&lt;br /&gt;
&lt;br /&gt;
==Database SQL (MySql) file inside full backups==&lt;br /&gt;
In full backups, the actual database is backed up also. To find this sql file, look for the following folder in your backup file after you have extracted/unzipped the backup zip file: &lt;br /&gt;
&lt;br /&gt;
wp-content/uploads/backupbuddy_temp/'''XXXXXXXX'''&lt;br /&gt;
&lt;br /&gt;
The '''XXXXXXXX''' part in the above link will be a serial code that matches the one in the backup name. That is it will be the exact same as the last set of characters, after the date, in your backup file name.&lt;br /&gt;
&lt;br /&gt;
For example, if your backup file name is:&lt;br /&gt;
&lt;br /&gt;
'''backup-domain_com-2012_05_29-''ukitenaifg''.zip'''&lt;br /&gt;
&lt;br /&gt;
then the folder inside a full backup where your database file is saved is&lt;br /&gt;
&lt;br /&gt;
wp-content/uploads/backupbuddy_temp/'''ukitenaifg'''&lt;br /&gt;
&lt;br /&gt;
==BackupBuddy Tab Missing in WordPress==&lt;br /&gt;
*If the BackupBuddy Tab is missing in your WordPress Admin area, there could be a few reasons for it:&lt;br /&gt;
**'''MULTISITES:''' If you are activating BackupBuddy on a single site inside a Multisite instead of using the NETWORK ACTIVATE option, BackupBuddy options will be hidden on purpose for security reasons. You must use [http://ithemes.com/codex/page/Installing_BackupBuddy#Multisite Network NETWORK ACTIVATE] instead.&lt;br /&gt;
**Try disabling other plugins which may be causing a conflict OR not allowing BackupBuddy tab to show up in WordPress admin area, even if direct links to such areas work.&lt;br /&gt;
&lt;br /&gt;
*Related links&lt;br /&gt;
**[http://ithemes.com/codex/page/Installing_BackupBuddy#Multisite Network Active BackupBuddy on Multisites]&lt;br /&gt;
**[http://ithemes.com/forum/index.php?/topic/18395-backupbuddy-installed-and-working-but-missing-from-wordpress-left-panel/ Plugin conflicts causing BackupBuddy to disappear in WordPress Admin panel]&lt;br /&gt;
&lt;br /&gt;
==Warning:xxxxxx: open_basedir restriction in effect. File(xxxxxxx) is not within allowed the path(s)....==&lt;br /&gt;
*Your server is configured to only allow scripts access to files in a certain directory. Your own files are not in this directory. This is a server configuration error (you should be able to access your own files) and your host should be able to fix it.&lt;br /&gt;
*http://www.php.net/manual/en/ini.core.php#ini.open-basedir&lt;br /&gt;
&lt;br /&gt;
==Warning:xxxxx:Unable to Access .../wp-content/uploads/backupbuddy_backups/temp_test_xxxxxxx.zip in /wp-content/... on line X==&lt;br /&gt;
* Usually immediately followed by a Warning: Cannot modify header information - headers already sent&lt;br /&gt;
* Happens most often when installing/activating BackupBuddy or after a migration.&lt;br /&gt;
*Solution:&lt;br /&gt;
** Make sure that the backupbuddy_backups folder does exist at /wp-content/uploads/, if it doesn't then create it.&lt;br /&gt;
** Also make sure permissions are set to 755 recursively for the /wp-content/uploads directory.&lt;br /&gt;
** Logging into the WordPress admin and navigating around a few BackupBuddy pages can trigger it to create the folder also.&lt;br /&gt;
*** Setting permissions to 777 temporarily can let give it a chance to create it if it was having trouble doing so for some reason.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Restoring/Migrating=&lt;br /&gt;
&lt;br /&gt;
==Importbuddy asking for an authentication password when it didn't used to==&lt;br /&gt;
Importbuddy did not used to have a mandatory password to be ran or downloaded. However, it does now as of version 2.2.33 of BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
If using an older file that you never set a password for that is now asking for a password then:&lt;br /&gt;
* Set a password for importbuddy in BackupBuddy's Settings page. Then download and use this new importbuddy.&lt;br /&gt;
&lt;br /&gt;
==No Next Step Button In Step 1==&lt;br /&gt;
If the server info section of step 1 is keeping the page from finishing loading (aka: no &amp;quot;Next Step&amp;quot; button) then can go to this URL as a workaround:&lt;br /&gt;
* ......./importbuddy.php?skip_serverinfo=true&lt;br /&gt;
&lt;br /&gt;
==Step 3 in import results in importbuddy.php file being downloaded when &amp;quot;Next Step&amp;quot; is clicked==&lt;br /&gt;
This problem happens because the .htaccess file being imported conflicts with the way your new host/server/site, where you are importing to, runs and processes php files. &lt;br /&gt;
&lt;br /&gt;
* To fix it, try any of the following (keep going through the steps till you solve the problem - the Second step below should solve the problem completely)&lt;br /&gt;
** First, make sure you have the latest version of BackupBuddy's importbuddy.php (gotten from the download link available on the BackupBuddy main Backup page.)&lt;br /&gt;
** Second, read this exact issue explained in detail on PluginBuddy http://pluginbuddy.com/site-migration-heaven-one/ That has detailed steps on how to solve this.&lt;br /&gt;
** Third, AFTER you encounter the problem, since the importbuddy.php file already has extracted the files:&lt;br /&gt;
*** Rename the .htaccess file in the newly extracted folder/area to anything like .htaccess_backup &lt;br /&gt;
*** Restart the import process again. &lt;br /&gt;
*** This time, in the Advanced Tab, select the option to &amp;quot;Skip File Unzip&amp;quot;, since the files have already been extracted. &lt;br /&gt;
*** After the site has been restored, go into your Settings --&amp;gt; Permalinks area to simply save that page, without making any changes. That will recreate the necessary .htaccess file again for the newly imported file.&lt;br /&gt;
** Make sure all file, folder and any other permissions are set properly before and after the backup and restore.&lt;br /&gt;
* This is probably the SAME as the other issue of [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Importbuddy.php_shows_ACTUAL_file_contents_instead_of_the_next_step Importbuddy showing actual file contents instead of the next step]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You should now be able to pass Step 3 without any issues.&lt;br /&gt;
&lt;br /&gt;
* Similar pages/threads with solutions:&lt;br /&gt;
** http://pluginbuddy.com/site-migration-heaven-one/ &lt;br /&gt;
**  http://ithemes.com/forum/index.php?/topic/17933-backupbuddy-after-step-3-downloads-importbuddyphp/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/13350-step-3-click-next-step-downloads-a-file-does-not-go-to-step-4/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/15420-impurtbuddy-step-3-problem/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/16443-cant-get-past-step-3-asks-to-download-importbuddyphp-over-and-over/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/13375-rackspace-server-cant-migrate-to-it-using-importbuddy/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/13660-help-with-migration/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/14350-cannot-move-past-step-3-in-migration/&lt;br /&gt;
** [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Importbuddy.php_shows_ACTUAL_file_contents_instead_of_the_next_step Importbuddy showing actual file contents instead of the next step]&lt;br /&gt;
&lt;br /&gt;
=='''Parse error''': syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /.../importbuddy.php on line 7974 (or any line)==&lt;br /&gt;
This error usually means that your site/server, where you are importing to, is running PHP4. BackupBuddy and importbuddy.php require at least PHP5 to function properly. &lt;br /&gt;
*It's usually easily fixable:&lt;br /&gt;
** Make sure you are using PHP5 and not PHP4.&lt;br /&gt;
** Change your PHP settings yourself to run PHP5.&lt;br /&gt;
** Ask your host to make sure you're running PHP5.&lt;br /&gt;
*Related customer thread with solution&lt;br /&gt;
**http://ithemes.com/forum/index.php?/topic/18009-parse-error/&lt;br /&gt;
&lt;br /&gt;
==Extraction of zip files (unzipping) does not work==&lt;br /&gt;
&lt;br /&gt;
Sometimes your host or site setup may prevent importbuddy.php from extracting (unzipping) the backup file. &lt;br /&gt;
&lt;br /&gt;
Here are 2 manual solutions, one via FTP and one via cPanel, on unzipping the files manually and then continuing the importbuddy.php process. Try either of the following:&lt;br /&gt;
&lt;br /&gt;
* http://pluginbuddy.com/restoring-an-unzipped-backup-with-backupbuddy/&lt;br /&gt;
* http://pluginbuddy.com/tutorials/unzip-backup-zip-file-in-cpanel/&lt;br /&gt;
&lt;br /&gt;
IMPORTANT: Make sure you choose &amp;quot;Skip zip file extraction&amp;quot;, under the &amp;quot;Advanced Configuration Options&amp;quot; tab on Step 1, to tell importbuddy.php to SKIP the extraction process. The import should work fine then while skipping the extraction process.&lt;br /&gt;
&lt;br /&gt;
==Old importbuddy overwriting on unzip==&lt;br /&gt;
* Possible Symptoms:&lt;br /&gt;
** importbuddy behaves differently or stops functioning properly after the extraction step.&lt;br /&gt;
** Weird errors are seen after the extraction step.&lt;br /&gt;
** The importbuddy version at the bottom of importbuddy changes after the extraction step.&lt;br /&gt;
** Error: &amp;quot;Error! The unzip process reported success but the backup data file, backupbuddy_dat.php was not found in the extracted files. The unzip process either failed (most likely) or the zip file is not a proper BackupBuddy backup.&amp;quot;&lt;br /&gt;
** Error 9003.&lt;br /&gt;
* Possible Solutions:&lt;br /&gt;
** Open the backup ZIP and delete the importbuddy.php file within it.&lt;br /&gt;
** Replace the importbuddy.php on your server after the extraction step but before moving forward further.&lt;br /&gt;
&lt;br /&gt;
==After import: The source site is now redirecting to the destination site (or vice versa):==&lt;br /&gt;
* This occurs if the new database settings were not entered during Step 3 of importbuddy.php.  Because of this, both sites are now sharing the same database so one of them (usually source) is redirecting to the other (usually destination).  importbuddy.php needs to be re-run inputting the source URL on Step 3 and using the source database settings.  This will reconfigure the source database to use its proper URL.  Next importbuddy.php needs to be run again inputting the destination URL on Step 3 with the NEW database settings for the new database.  This way both sites will have their own database for their respective URLs.&lt;br /&gt;
* importbuddy no longer overwrites existing WordPress databases by default so this issue is not as common as it used to be.&lt;br /&gt;
&lt;br /&gt;
==After import: WordPress Error: `You do not have sufficient permissions to access this page`==&lt;br /&gt;
One or more of your database table prefixes did not get changed during migration. A fix is available here: http://www.tech-evangelist.com/2010/02/06/wordpress-error-sufficient-permissions/&lt;br /&gt;
&lt;br /&gt;
==Cannot Log-in and Keep Getting Redirected Back to Log-In Page==&lt;br /&gt;
The migration completed successfully and the site is browse-able but when you try to log in you keep getting redirected back to the log-in page and the URL looks something like this:&lt;br /&gt;
&amp;lt;pre&amp;gt;http://wptest.local/wp-login.php?redirect_to=http%3A%2F%2Fwptest.local%2Fwp-admin%2F&amp;amp;reauth=1&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This is a common WordPress related issue and not a result of BackupBuddy backup or restore/import. It is easily fixable, though, and happens mainly because of some plugin or custom edit somewhere in WordPress causing WordPress to keep redirecting to a specific url for admin login.&lt;br /&gt;
&lt;br /&gt;
* Solutions (try any of these to see if they work - make a backup of everything Or keep you BackupBuddy backup in case something goes wrong or you want to undo some changes you make below):&lt;br /&gt;
** Edit W3 Total Cache settings to fix this, if you are using or have used W3 Total Cache. Please check in your wp-config.php for a line such as this:&amp;lt;pre&amp;gt;define('COOKIE_DOMAIN', 'www.domain.com'); // Added by W3 Total Cache&amp;lt;/pre&amp;gt; In order to be able to log-in please either delete the line; or comment out the line; or change the string 'www.domain.com' to false - note that false is not enclosed by quotes, e.g.,: &amp;lt;pre&amp;gt;define('COOKIE_DOMAIN', false); // Added by W3 Total Cache&amp;lt;/pre&amp;gt; You will now be able to log-in and can then attend to updating this definition as required by your new site configuration. To read more about COOKIE_DOMAIN please visit: [http://codex.wordpress.org/Editing_wp-config.php#Set_Cookie_Domain WordPress Codex - Cooke Domain]&lt;br /&gt;
** Make sure your wp-config.php files does NOT have any hard-coded SITE or WordPress URI that may be causing this issue.&lt;br /&gt;
** Make sure there is no duplicate .htaccess file.&lt;br /&gt;
** Make sure the existing .htaccess file does not contain anything related to the Site or WordPress URL that is causing the redirect.&lt;br /&gt;
** Make sure the wp_options table does not have any OLD url's which were NOT updated prior to the move.&lt;br /&gt;
** Make sure you use the latest versions of BackupBuddy and importbuddy.php (even try importbuddy.php beta to see if that makes a difference)&lt;br /&gt;
** Disable conflicting/all plugins by renaming the folder names of the individual plugins to something different.&lt;br /&gt;
&lt;br /&gt;
* Some good posts with good/alternate solutions/info on this:&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/14324-getting-redirected-when-trying-to-login/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/14102-new-site-wp-admin-redirect-back-to-original-sites-wp-admin/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/13581-access-admin-backend/&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/17383-wp-content-files-on-subdomain-redirect-to-root/&lt;br /&gt;
** http://codex.wordpress.org/Login_Trouble&lt;br /&gt;
** http://wordpress.org/support/topic/keeps-redirecting-when-logging-in&lt;br /&gt;
** http://codex.wordpress.org/Editing_wp-config.php#Set_Cookie_Domain&lt;br /&gt;
** [http://wordpress.org/support/topic/domain-redirection-keeps-forwarding-to-signup-page Multisite Redirects]&lt;br /&gt;
&lt;br /&gt;
==Blank OR strange homepage/frontpage BUT admin area works perfectly==&lt;br /&gt;
This usually happens when there is an existing and unwanted index.html, default.html or some other server default file already in the root of WordPress directory of your new restore/migrated site. &lt;br /&gt;
*Solution: &lt;br /&gt;
**Make sure your .htaccess file is not causing the issue.&lt;br /&gt;
**Make sure you delete any extra index.html, default.html or any other server default file that is already in the root of the WordPress directory of your newly restored/migrated site.&lt;br /&gt;
**Make sure your WordPress's index.php file is correct. If not, you can always download the latest version from WordPress.org and use the index.php file from that download (with any changes you may have made to the existing index.php file) to replace the index.php already present in your site.&lt;br /&gt;
**Make sure your theme's index.php and other theme files contents and permissions are correct.&lt;br /&gt;
**Make sure your theme settings in the WordPress admin section are correct. &lt;br /&gt;
** Make sure the home URL got updated in the database.&lt;br /&gt;
*** Can also use RepairBuddy to verify home URL.&lt;br /&gt;
*Related customer thread with easy solution:&lt;br /&gt;
**http://ithemes.com/forum/index.php?/topic/17989-update-in-progress-after-migrate/&lt;br /&gt;
&lt;br /&gt;
==Links (permalinks) return 404 errors==&lt;br /&gt;
====Most Common====&lt;br /&gt;
* The [[.htaccess]] file was not configured properly or was not writable so importbuddy didn't update it.&lt;br /&gt;
** Solution: Log in to the admin dashboard and navigate to: Settings -&amp;gt; Permalinks and click 'Save Changes'. This regenerates your .htaccess entries correcting most problems.&lt;br /&gt;
* To manually fix, edit the [[.htaccess]] file in a text editor following the format on the [[.htaccess]] page.&lt;br /&gt;
* If getting this after a migration in which it redirected you to home page during the migration's step 5&lt;br /&gt;
** Cause: .htaccess file is causing redirections.&lt;br /&gt;
** Solution:&lt;br /&gt;
*** 1) Redo import and pause after Step 2 (file extraction).&lt;br /&gt;
*** 2) After step 2 (but before continuing to step 3) delete the .htaccess file in the root of the site.&lt;br /&gt;
*** 3) Continue the import to completion&lt;br /&gt;
*** 4) Regenerate the .htaccess file in WordPress by going to Settings -&amp;gt; Permalinks -&amp;gt; and clicking to &amp;quot;Save Changes&amp;quot;&lt;br /&gt;
* If using custom permalinks, try default ones to see if the issue is tied to the custom permalinks.&lt;br /&gt;
* [http://codex.wordpress.org/Using_Permalinks#Fixing_Permalink_Problems See WordPress' official page on Fixing Permalinks for more solutions.]&lt;br /&gt;
&lt;br /&gt;
====Users of XAMPP (Windows)====&lt;br /&gt;
Some versions of XAMPP do not enable mod_rewrite by default (though it is compiled in Apache). To enable it — and thus enable WordPress to write the .htaccess file needed to create pretty permalinks — you must open apache/conf/httpd.conf and uncomment the line LoadModule rewrite_module modules/mod_rewrite.so (i.e., delete the hash/pound sign at the front of the line).&lt;br /&gt;
====Users of WAMP (Windows)====&lt;br /&gt;
Some versions of WAMP (all versions?) do not enable mod_rewrite or permit following SymLinks by default. To enable the required functionality navigate to the apache/conf/httpd.conf file, open with a text editor and uncomment the line LoadModule rewrite_module modules/mod_rewrite.so (i.e., delete the hash/pound sign at the front of the line). Then further down in the same file there is a section that starts with the line &amp;quot;Options FollowSymlinks&amp;quot;. Change the second line in that section from &amp;quot;AllowOverride none&amp;quot; to AllowOverride all. Save edited httpd.conf and restart all WAMP modules. Your permalinks should now work. &lt;br /&gt;
====Users of Ubuntu + Apache====&lt;br /&gt;
The packaged version of Apache that came down with apt-get lamp-server^ doesn't enable mod_rewrite by default.  [http://serverfault.com/questions/139791/how-can-i-enable-mod-rewrite-in-apache-on-ubuntu This link is a step in the right direction], although you also might have to set the AllowOverride rules to &amp;quot;all&amp;quot; in /etc/apache2/sites-enabled/000-default.  Also, after making those changes make sure to restart Apache.  -- In summary, the steps that helped me fix this problem were:  1) Enable mod_rewrite on Apache, 2) Restart Apache, 3) Rename .htaccess to .htaccess.bak (move it out of the way), 4) Regenerate the .htaccess file (as above) --&amp;gt; login to your admin dashboard and go to Settings -&amp;gt; Permalinks -&amp;gt; and click the &amp;quot;Save Changes&amp;quot; button.&lt;br /&gt;
&lt;br /&gt;
====500 Server Errors====&lt;br /&gt;
* [[.htaccess]] (click for details) file is causing URLs to be redirected improperly or is malformed. Sometimes the front end simply won't load.&lt;br /&gt;
** Regnerating the .htaccess file can solve. To do this login to your admin dashboard and go to Settings -&amp;gt; Permalinks -&amp;gt; and click the &amp;quot;Save Changes&amp;quot; button.&lt;br /&gt;
*** Note: You don't have to actually make any changes on the page to regenerate the .htaccess in this manner by clicking to &amp;quot;Save Changes&amp;quot;.&lt;br /&gt;
* PHP is not functioning or enabled for the site. Check with basic [[phpinfo()]].&lt;br /&gt;
* A 404 error is occurring but the server is not set up correctly to return a 404. Do sanity check with .htm file.&lt;br /&gt;
* Manually edit the [[.htaccess]] file in a text editor following the format on the [[.htaccess]] page.&lt;br /&gt;
* Delete or manually remove your OLD .htaccess file from the extracted folders after it passes the step of extracting files, from the backup file (and then zip it again) OR before you do a backup.&lt;br /&gt;
* Edit your OLD .htaccess file to be basic without any extra comments that may be interfering on the new server.&lt;br /&gt;
* Make sure your new OR old .htaccess does NOT have any directive that is resulting in any website file, including the index, to be blocked.&lt;br /&gt;
* See `.htaccess being overwritten on unzip` below if it happens on Step 2 of import.&lt;br /&gt;
* Ask your host to look at the .htaccess file and to fix any errors with it, OR to delete the EXISTING AND/OR GENERATED .htaccess file OR to generate a new .htaccess file for you.&lt;br /&gt;
&lt;br /&gt;
*Related links:&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/18089-migration-failure-with-500-internal-server-error/&lt;br /&gt;
** [http://ithemes.com/forum/index.php?/topic/18445-restored-site-now-wont-load-and-cant-log-in/#p86642 Remove extra .htaccess lines which may be preventing the site from loading]&lt;br /&gt;
** [http://ithemes.com/forum/index.php?/topic/18607-internal-server-error-hostgator-rocks/ How HostGator helped a customer fix this error by simply fixing the bad .htaccess file]&lt;br /&gt;
&lt;br /&gt;
==.htaccess being overwritten on unzip==&lt;br /&gt;
* Symptoms:&lt;br /&gt;
** PHP stops properly functions in importbuddy.php after the extraction step.&lt;br /&gt;
** Weird errors are seen after the extraction step.&lt;br /&gt;
* Solution:&lt;br /&gt;
** Open the backup ZIP and delete the .htaccess file within it, can be done before migrating.&lt;br /&gt;
*** Can also delete the .htaccess file in directory after step 2&lt;br /&gt;
&lt;br /&gt;
==The backup zip file is not found==&lt;br /&gt;
* The zip file has been renamed to a non-BackupBuddy format.&lt;br /&gt;
* The zip file permissions are wrong. Ex: Not readable.&lt;br /&gt;
* The zip file is not in the same directory as importbuddy.php.&lt;br /&gt;
* The zip file has not finished uploading or was interrupted in transit. If BackupBuddy was used to send it try manually uploading.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==backupbuddy_dat.php OR db_1.sql was not found after extraction==&lt;br /&gt;
* You may be using an older version of importbuddy.php not compatible with your backup version. Try upgrading your importbuddy.php to the version in the latest BackupBuddy.&lt;br /&gt;
* You may have renamed your backup ZIP file. BackupBuddy depends on the naming format to determine where some data in the backup ZIP is stored. Rename your backup back to its original name.&lt;br /&gt;
* Your backup may be corrupt. Try manually unzipping to verify it extracts properly.&lt;br /&gt;
&lt;br /&gt;
==SQL error near WH==&lt;br /&gt;
* It is because the table does not have a mysql primary key or unique index&lt;br /&gt;
** If you have Gravity Forms and the problem is in _rg_form_meta then upgrade Gravity Forms to version 1.6+&lt;br /&gt;
&lt;br /&gt;
==Restoring database times out==&lt;br /&gt;
* You can try reducing the size of that database.&lt;br /&gt;
** Checking for extra large tables you don't need (such as deleted plugins leaving data behind).&lt;br /&gt;
** What revision retention policy do you operate on the posts? It may be that you have a lot of revisions stored in the database that you could safely remove. The WordPress Codex gives some information on controlling revisions (http://codex.wordpress.org/Editing_wp-config.php#Post_Revisions) but I don't think this acts retrospectively so you might need to find a method to prune any revisions you currently have. &lt;br /&gt;
* Seeing if host will increase memory limit and runtime can help as well.&lt;br /&gt;
&lt;br /&gt;
==Extracting ZIP times out / hangs==&lt;br /&gt;
* Unzipping was not able to complete due to the unzipping process taking longer than the maximum PHP allowed runtime (usually 30 seconds).&lt;br /&gt;
* Solutions:&lt;br /&gt;
** Manual Unzip Process:&lt;br /&gt;
*** Manually extract the ZIP file on your computer then upload the files to the server.&lt;br /&gt;
*** Restart the importbuddy.php Import process, selecting `Skip Zip Extraction` from the advanced options slide-down.&lt;br /&gt;
** Or ask your host to increase the maximum PHP runtime beyond its current limit.&lt;br /&gt;
&lt;br /&gt;
==Defined URL in wp-config.php==&lt;br /&gt;
* Symptoms:&lt;br /&gt;
** URL does not appear to update after migration.&lt;br /&gt;
** Links 404 after migration and you verified that you entered the correct URL to migrate to.&lt;br /&gt;
** Links can also redirect to old site at the defined URL, though usually they 404&lt;br /&gt;
** Cannot update url's in the admin area. Such fields are usually disabled, as WordPress disallows their editing if the home URL is in the wp-config.php file&lt;br /&gt;
&lt;br /&gt;
==URLs redirecting to old site after migration==&lt;br /&gt;
* Symptoms: Home page is up and looks fine but links in the site all keep going to the old/source site.&lt;br /&gt;
* Solution:&lt;br /&gt;
** Re-run importbuddy.php entering the correct URLs and watching for any errors.&lt;br /&gt;
** Also make sure import is finishing correctly, may be timing out without realizing it.&lt;br /&gt;
*** Can check the importbuddy.txt log to see if it caught something, will be located in same place you uploaded the importbuddy file.&lt;br /&gt;
** Check for any hardcoded/defined URLs in the site's wp-config.php and HTML files.&lt;br /&gt;
*** If site URL is hardcoded in theme HTML files can wrap them in home_url( '/directory/' ) to fix.&lt;br /&gt;
&lt;br /&gt;
==URL needs manually updated==&lt;br /&gt;
* Note that this does not update serialized data. In short, some plugins, such as PluginBuddy plugins may not have internal URLs updated. This is more of a last-choice solution.&lt;br /&gt;
* SQL to update URL in posts manually:&lt;br /&gt;
&amp;lt;pre class=&amp;quot;brush:html&amp;quot;&amp;gt;update wp_posts set post_content = replace(post_content, 'http://OLD_URL', 'http://NEW_URL');&amp;lt;/pre&amp;gt;&lt;br /&gt;
* Command line zip test to check if exec is enabled and zip can create a file. Download: [[Media:Zip_test.zip]]&lt;br /&gt;
* Safest way to mass search/replace URLs is to use a tool that is prepared to handle serialized data. [https://github.com/interconnectit/Search-Replace-DB Search-Replace-DB] is a well known open source tool to take care of this.&lt;br /&gt;
&lt;br /&gt;
==The unzip process reported success but the backup data file...==&lt;br /&gt;
&amp;quot;Error! The unzip process reported success but the backup data file,&lt;br /&gt;
backupbuddy_dat.php was not found in the extracted files. The unzip&lt;br /&gt;
process either failed (most likely) or the zip file is not a proper&lt;br /&gt;
BackupBuddy backup.&amp;quot;&lt;br /&gt;
* Most common cause: See [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Old_importbuddy_overwriting_on_unzip]&lt;br /&gt;
* The backup did not finish extracting (timed out).&lt;br /&gt;
* Verify the backup is not damaged.&lt;br /&gt;
&lt;br /&gt;
==Importbuddy.php shows ACTUAL file contents instead of the next step==&lt;br /&gt;
There is one report that on Step 4, importbuddy.php started showing the actual importbuddy.php file contents. The reason for this was that the EXTRACTED .htaccess file from the OLD server/site was causing the issue.&lt;br /&gt;
&lt;br /&gt;
This is VERY similar OR the same as [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Step_3_in_import_results_in_importbuddy.php_file_being_downloaded_when_.22Next_Step.22_is_clicked Step 3 downloading importbuddy.php file issue] which also contains possible reasons and solutions.&lt;br /&gt;
&lt;br /&gt;
*Solutions&lt;br /&gt;
**Check your .htaccess file on the OLD server/site and fix any issues with it. THEN do the backup.&lt;br /&gt;
**After Step 3 has finished, and BEFORE proceeding to Step 4 (or any such step where this problem happens), open a new window OR your FTP program, go and find the EXTRACTED .htaccess file, EDIT it to remove any UNWANTED directives, and then switch back to the importbuddy.php window to continue onto the next step.&lt;br /&gt;
**On the OLD site, ALSO try saving your Permalinks again in WordPress --&amp;gt; Permalinks . Simply click &amp;quot;Save&amp;quot; on that page and then do a backup and retry the import/restore/migration. &lt;br /&gt;
**Thanks to our customer Chris Malone for finding the issue and finding a solution right away too.&lt;br /&gt;
**As mentioned above, this is VERY similar OR the same as [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Step_3_in_import_results_in_importbuddy.php_file_being_downloaded_when_.22Next_Step.22_is_clicked Step 3 downloading importbuddy.php file issue] which also contains possible reasons and solutions.&lt;br /&gt;
&lt;br /&gt;
*Related link&lt;br /&gt;
**[http://ithemes.com/forum/index.php?/topic/18621-wont-continue-past-step-3-when-running-importbuddy/ User reporting the issue and the solution]&lt;br /&gt;
**[http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Step_3_in_import_results_in_importbuddy.php_file_being_downloaded_when_.22Next_Step.22_is_clicked Step 3 downloading importbuddy.php file issue]&lt;br /&gt;
&lt;br /&gt;
=BackupBuddy Classic=&lt;br /&gt;
BackupBuddy Classic is available to download in case you have an older system OR older system specs like older PHP, MySql and other things. BackupBuddy Classic does not have any of the new features of BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
If your system or host forces you to use BackupBuddy Classic, you should start considering switching to another host or server ( we recommend [http://ithemes.com/hostgator HostGator] ) which is not old or not updated regularly.&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Classic can be found in your Member's area and is labeled &amp;quot;'''BackupBuddy Classic'''.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
*Related Link&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/18448-download-legacy-versions-of-backupbuddy/#p86657&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]&lt;br /&gt;
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]&lt;br /&gt;
# [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
# [http://pluginbuddy.com/support/ Support Forums]&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy:_Settings</id>
		<title>BackupBuddy: Settings</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy:_Settings"/>
				<updated>2013-01-28T23:21:19Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{#ev:youtube|PmXLw_tS42Q|400|right}}&lt;br /&gt;
== Quick Tip ==&lt;br /&gt;
Each of the different settings on the BackupBuddy settings page has a small question mark icon [[File:Pluginbuddy_tip.png‎]] that, when hovered over with the mouse, shows an explanation of what that setting will effect.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Email Notifications ==&lt;br /&gt;
===== Scheduled backup completion reciptients =====&lt;br /&gt;
This setting allows you to set email addresses that you would like email notifications to be sent to when a scheduled backup is completed.&lt;br /&gt;
&lt;br /&gt;
===== Manual backup completion recipients =====&lt;br /&gt;
This setting allows you to set email addresses that you would like email notifications to be sent to when a manual backup is completed.&lt;br /&gt;
&lt;br /&gt;
===== Backup failure/error recipients =====&lt;br /&gt;
This setting allows you to set email addresses that you would like email notifications to be sent to when a backup fails or runs into issues.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== General Options ==&lt;br /&gt;
===== Import password (optional) =====&lt;br /&gt;
Setting this option will customize importbuddy to require a password to launch the import/migration script. This prevents unauthorized users from being able to view your backup archive listing on the destination server during Step 1 or proceed with an unauthorized import.&lt;br /&gt;
&lt;br /&gt;
===== Backup reminders =====&lt;br /&gt;
When this option is enabled reminder links will be displayed when a post or page is updated and on the WordPress upgrades screen before you update as a reminder. The reminder links allow for easily backing up after modifications or before upgrading.&lt;br /&gt;
&lt;br /&gt;
===== Backup all database tables =====&lt;br /&gt;
When this option is enabled ALL tables and data in the database will be backed up, even database content not related to WordPress, its content, or plugins (based on prefix).  This is useful if you have other software installed on your hosting that stores data in your database.&lt;br /&gt;
&lt;br /&gt;
===== Compatibility/Troubleshooting options =====&lt;br /&gt;
Various options to aid in making BackupBuddy work in less than ideal server environments. These are useful for working around problems. You may be directed by support to modify these if you encounter problems.&lt;br /&gt;
&lt;br /&gt;
====== Enable ZIP compression ======&lt;br /&gt;
When BackupBuddy creates a backup file this is always created as a ZIP archive format file. Whether or not the files that are included in the archive are compressed in size is an option and this setting enables you to choose whether or not files will be compressed when stored within the archive.&lt;br /&gt;
&lt;br /&gt;
The choice of whether to use compression or not is based on a time/space trade-off: if files are compressed it takes longer to produce the archive but the archive will (in almost all cases) be smaller in size; where as if files are not compressed the archive takes less time to produce but will (in almost all cases) be larger.&lt;br /&gt;
&lt;br /&gt;
The reason why a compressed archive takes longer to produce is of course because the mechanics of compressing files is processor intensive and slower than just copying file content from one place to another.&lt;br /&gt;
&lt;br /&gt;
The reason why, just sometimes, an archive containing compressed files may be larger than one containing the same files in an uncompressed form is that some of the files on your site may already be in a compressed format - particularly media files - and trying to compress an already compressed file, aside from being very processor intensive, can result in a larger file.&lt;br /&gt;
&lt;br /&gt;
The default for this setting is checked, meaning that compression is enabled - this is usually the best option for most sites as it gives a good balance between speed of producing the backup and the size of the backup file. Another reason why you might want compression enabled is if you have a large site which approaches the size limits of the standard ZIP archive file format - around 4GB. Provided that you have no time constraint in producing a backup file then enabling compression means that you will get your site into a zip archive which you might otherwise not do if the files were included without compression.&lt;br /&gt;
&lt;br /&gt;
On the other hand, if you have time constraints on producing your backup then you might want to consider disabling compression so that the backup file may be produced faster but of course at the expense of being larger.&lt;br /&gt;
&lt;br /&gt;
Another reason you might want to consider disabling compression is if you have a large number of media files on your site - which as explained, may already be in a compressed format. It is worth experimenting in this case, try a backup with compression enabled, see how long it takes and how large the backup file is. Then try a backup with compression disabled and again how long does it take and how large is it. By comparing the two and based on your requirements and any other constraints you can decide whether it is better to have compression enabled or disabled on that specific site.&lt;br /&gt;
&lt;br /&gt;
====== Perform integrity check on backup files ======&lt;br /&gt;
By default BackupBuddy checks each backup file for integrity and completion the first time it is viewed on the Backup page. On some server configurations this check may cause memory problems as the integrity checking process is intensive.  If you are experiencing out of memory errors on the Backup file listing, you can uncheck this option to disable this feature. &lt;br /&gt;
&lt;br /&gt;
====== Advanced: Force compatibility mode backups ======&lt;br /&gt;
WARNING: This option forces the less reliable mode of operation. Only use if absolutely necessary. Enabling this option can cause backup failures if it is not needed. Under normal circumstances compatibility mode is automatically used as needed without user intervention. However under some server configurations the native backup system is unavailable but is incorrectly reported as functioning by the server. Forcing compatibility mode may fix problems in this situation by bypassing the native backup system check entirely.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Logging level =====&lt;br /&gt;
Throughout BackupBuddy there are different levels of log statements that can be written to a txt document for different processes that are run in BackupBuddy. The logging feature is useful for finding out what processes have been run and when any errors occur.&lt;br /&gt;
&lt;br /&gt;
Here is a list of the different logging levels:&lt;br /&gt;
* None - Nothing will be recorded in the log file.&lt;br /&gt;
* Errors Only - This is the default logging level, where only error statements will be recorded in the log file.&lt;br /&gt;
* Errors and Warnings - Only Errors and warnings will be recorded in the log file.&lt;br /&gt;
* Everything - This is also know as debug mode because everything that happens will be recorded in the log file, making it very easy to see when different actions occurred and when errors occurred in relation to other events.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Archive Storage Limits ==&lt;br /&gt;
===== Maximum number of archived backups =====&lt;br /&gt;
This option allows you to set the maximum number of backups that will be stored locally.&lt;br /&gt;
&lt;br /&gt;
By default this option is set to 0 which means that there is no limit.&lt;br /&gt;
&lt;br /&gt;
If a maximum number of backups is set and is exceeded BackupBuddy will delete local backups from oldest to youngest until the number of backups is equal to the maximum that is set.&lt;br /&gt;
&lt;br /&gt;
===== Maximum size of archived backups =====&lt;br /&gt;
This option allows you to set a maximum total filesize of all of the local backups.&lt;br /&gt;
&lt;br /&gt;
By default this option is set to 0 which means that there is no limit.&lt;br /&gt;
&lt;br /&gt;
If a maximum size is set and is exceeded Backup will delete local backups from oldest to youngest until the total filesize of the local backups is equal to or lower then the maximum that is set.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Remote Offsite Storage / Destinations ==&lt;br /&gt;
This section of the settings page allows you to access a tabbed menu with the different account information for each different remote storage device.&lt;br /&gt;
&lt;br /&gt;
The available remote storage devices are:&lt;br /&gt;
* Amazon S3&lt;br /&gt;
* Dropbox&lt;br /&gt;
* Rackspace&lt;br /&gt;
* FTP&lt;br /&gt;
* Email&lt;br /&gt;
Once you have added different accounts for different devices this area has built in clients that allow you to manage the BackupBuddy backups on those different accounts. Those built in clients will show a list of the backups on those remote devices. You will be able to delete and copy those BackupBuddy backups to where you local backups are being stored.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Backup Exclusions ==&lt;br /&gt;
This feature allows you to select any directories that you don't want to be included in the backups that are created. This feature is very useful if there are any large directories that aren't necessary that can be excluded and allow the backup process complete in a shorter amount of time.&lt;br /&gt;
&lt;br /&gt;
If BackupBuddy is dropping into compatibility mode during the backup process then none of the directories will be excluded. In order to use directory exclusion BackupBuddy must be using exec during the backup process.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]&lt;br /&gt;
&lt;br /&gt;
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]&lt;br /&gt;
# [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
# [http://pluginbuddy.com/support/ Support Forums]&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy</id>
		<title>BackupBuddy</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy"/>
				<updated>2013-01-28T23:19:58Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* '''New to BackupBuddy?''' Check out the [[BackupBuddy:_Getting_Started|Getting Started]] page.&lt;br /&gt;
* '''Problems?''' Check out the [[BackupBuddy:_Frequent_Support_Issues|Frequently Seen Support Issues]] page.&lt;br /&gt;
* '''Need hosting?''' ''Hostgator Coupons'' are available to BackupBuddy customers [http://ithemes.com/forum/index.php?/topic/14012-hostgator-coupons-for-our-community/ here].&lt;br /&gt;
* '''[http://ithemes.com/codex/page/BackupBuddy_Multisite BackupBuddy Multisite Codex]'''&lt;br /&gt;
&lt;br /&gt;
=Tutorials=&lt;br /&gt;
&lt;br /&gt;
===Training Videos===&lt;br /&gt;
For video training including walkthroughs &amp;amp; tutorials please see http://ithemes.com/backupbuddy-training/&lt;br /&gt;
&lt;br /&gt;
===Installing BackupBuddy===&lt;br /&gt;
&lt;br /&gt;
Check out the [[Installing BackupBuddy]] section to see how BackupBuddy can be uploaded and activated on Single sites or Multisite networks or Multisite sites.&lt;br /&gt;
&lt;br /&gt;
===Getting Started===&lt;br /&gt;
Check out the [[BackupBuddy:_Getting_Started|Getting Started]] page to backup your Single sites or Multisite networks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Restore or Migrate===&lt;br /&gt;
Learn to [[BackupBuddy:_ImportBuddy|Restore or Migrate]] your Single sites or Multisite networks with the latest importbuddy.php.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Settings Explained===&lt;br /&gt;
Get in depth information about the various [[BackupBuddy:_Settings|Settings]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Developing Locally===&lt;br /&gt;
Set up your computer to [[BackupBuddy:_Local_Development|Develop Sites Locally]] and then migrate them to your live site.&lt;br /&gt;
&lt;br /&gt;
=Specifications=&lt;br /&gt;
Server configuration is a very complex topic and varies wildly between hosts, server operating systems, and even the personal preference of the server administrator. Below are the bare minimum requirements for the plugin along with the recommended setup to get the most out of this plugin. You may use [[ServerBuddy]] to help you determine how your server compares to our minimum requirements &amp;amp; recommendations.&lt;br /&gt;
&lt;br /&gt;
===Server Recommendations (full functionality)===&lt;br /&gt;
* PHP 5.2+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires PHP 5.2+]&lt;br /&gt;
* mySQL 5.x+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires mySQL 5.0.15+]&lt;br /&gt;
* WordPress 3.3+ &lt;br /&gt;
* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.&lt;br /&gt;
** Backups will be stored in /wp-content/uploads/backupbuddy_backups/&lt;br /&gt;
** Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)&lt;br /&gt;
* Free disk space equal to or greater than the entire size of your site once compressed.&lt;br /&gt;
** SuPHP or environment so that file operations/zip run as user to prevent permissions issues.&lt;br /&gt;
** PHP exec() function enabled&lt;br /&gt;
** PHP ZipArchive class installed&lt;br /&gt;
* Linux (Apache):&lt;br /&gt;
** Command-line zip installed and accessible via exec().&lt;br /&gt;
* Windows (only supported for local development via Apache; IIS is not officially supported):&lt;br /&gt;
** Windows zip executable (available [http://pluginbuddy.com/wp-content/uploads/2010/05/backupbuddy_windows_unzip.zip here])&lt;br /&gt;
*** You must have the ability to configure your server to allow execution of this zip.exe file for it to function.&lt;br /&gt;
*** File permissions must also be set to allow access and execution of the zip executable.&lt;br /&gt;
* wp-config.php file must be in WordPress installation directory OR (starting with BackupBuddy v3.0) in the parent directory.&lt;br /&gt;
&lt;br /&gt;
===Minimum Server Requirements (reduced functionality)===&lt;br /&gt;
'' NOTE: Some features of BackupBuddy will be unavailable or limited if running on minimum requirements without recommendations. Large sites may not be able to be backed up with these minimum features.'''&lt;br /&gt;
* PHP 5.2+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires PHP 5.2+]&lt;br /&gt;
* mySQL 5.x+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires mySQL 5.0.15+]&lt;br /&gt;
* WordPress 3.2+&lt;br /&gt;
** We are trying to maintain bare minimum backup functionality for legacy versions as far back as WordPress v2.6 (though it's not pretty nor guaranteed to work perfectly at this time; we recommend only performing backups &amp;amp; direct restores for older versions and use it for safety while upgrading to the latest WordPress).&lt;br /&gt;
* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.&lt;br /&gt;
* BackupBuddy requires the uploads directory to be in the standard WordPress location.&lt;br /&gt;
** Backups will be stored in /wp-content/uploads/backupbuddy_backups/&lt;br /&gt;
** Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)&lt;br /&gt;
* Free disk space equal to or greater than the entire size of your site once compressed.&lt;br /&gt;
* wp-config.php file must be in WordPress installation directory OR (starting with BackupBuddy v3.0) in the parent directory.&lt;br /&gt;
&lt;br /&gt;
===Host Compatibility===&lt;br /&gt;
Compare various [[BackupBuddy:_Hosts|Hosts &amp;amp; Hosting Environments]] to see how your host/potential host compares.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Misc. Information===&lt;br /&gt;
Find out some [[BackupBuddy:_Misc_Information|Miscellaneous Information]] about BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
	&lt;br /&gt;
=Troubleshooting=&lt;br /&gt;
&lt;br /&gt;
===Frequently Seen Support Issues===&lt;br /&gt;
''Problems?'' We have compiled a list of issues and solutions to many problems that we have seen encountered before. [[BackupBuddy:_Frequent_Support_Issues|Frequently Seen Support Issues]] to attempt to narrow down your problem and find a solution.&lt;br /&gt;
&lt;br /&gt;
===BackupBuddy: Error Codes===&lt;br /&gt;
Receive an error code? Check out the [[BackupBuddy:_Error_Codes|Error Codes]] page for explanations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Manual Migration===&lt;br /&gt;
Import fails on file extraction? Learn how to perform a [[BackupBuddy:_Manual_Migration|Manual Migration]] ... it's easier than you'd think!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
&lt;br /&gt;
'''Tools'''&lt;br /&gt;
&lt;br /&gt;
* [http://ithemes.com/codex/page/File:Zip_test.zip Manually test command line zip functionality]&lt;br /&gt;
&lt;br /&gt;
=Multisite=&lt;br /&gt;
&lt;br /&gt;
BackupBuddy supports the following Multisite functionality:&lt;br /&gt;
* Export a Multisite subsite to standalone&lt;br /&gt;
* Import an exported Multisite subsite into an existing Network&lt;br /&gt;
* Import a standalone WordPress site into an existing Network&lt;br /&gt;
* Backup entire Network (backup/restore only; no migration to new URL)&lt;br /&gt;
* Restore entire Network WITHOUT URL migration for subsites within if migrating to a new URL (URL changes have limitations. Please see Multisite page for details)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://ithemes.com/codex/page/BackupBuddy_Multisite Check out the BackupBuddy Multisite Codex] and [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite Beta Today!]&lt;br /&gt;
&lt;br /&gt;
BETA indicates that Multisite functionality has known issues and is not reccomended for production use except at your own risk.  We do NOT guarantee its functionality or provide guaranteed support for beta products.&lt;br /&gt;
&lt;br /&gt;
'''Links'''&lt;br /&gt;
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]&lt;br /&gt;
# [http://ithemes.com/codex/page/BackupBuddy_Multisite BackupBuddy Multisite Codex]&lt;br /&gt;
# [http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy beta Multisite support announcement]&lt;br /&gt;
# [http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ BackupBuddy beta Multisite key points everyone is raving about!] &lt;br /&gt;
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]&lt;br /&gt;
# [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
# [http://pluginbuddy.com/support/ Support Forums]&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy_Multisite</id>
		<title>BackupBuddy Multisite</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy_Multisite"/>
				<updated>2013-01-22T08:05:30Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Introduction=&lt;br /&gt;
&lt;br /&gt;
Multisite support is a BETA UNSUPPORTED BONUS FEATURE provided in BackupBuddy to AID you in importing and exporting subsites with Multisite.  Due to the nature of Multisite we cannot provide the same level of thoroughness in migrations as with standalone sites.  You should NOT expect as smooth of an experience and we only recommend advanced users attempt to use Multisite functionality due to this.  As WordPress Multisite functionality is much more technically complex some BackupBuddy features available for standalone sites are NOT supports for Multisite environments.  Please carefully review the features, differences, and limitations so that you are aware of them and are sure it will meet your needs.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''BackupBuddy Multisite is a BETA product'''.  As such you ''may encounter issues'' using it and we cannot necessarily insure flawless functionality or that issues encountered will be resolved in as timely manner as non-beta features.  Usage of it in a production environment is at your own risk; Import/Export functionality is quite solid but Network migrations have some issues which require additional intervention to fully complete if the URL changes (see limitations below for full details). There is currently not a specific ETA on when the beta tag will be removed. It will be removed once we believe Multisite functionality to be as solid and reliable as the BackupBuddy standalone many have come to love.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Features &amp;amp; Limitation Notes=&lt;br /&gt;
&lt;br /&gt;
'''IMPORTANT: BackupBuddy Multisite does NOT support migrating entire Networks to a different URL. If you attempt to do so then only the main site URLs will be migrated and you must manually update all subsite URLs, for instance using the Server Information Page's Mass Database Replace Tool.'''&lt;br /&gt;
&lt;br /&gt;
* '''Backup entire Multisite Network'''&lt;br /&gt;
** Limitations:&lt;br /&gt;
***As a Network can contain many subsites, each subsite increases the amount of time needed to perform a backup, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish backups under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
*** WordPress 3.5 Multisite has introduced multiple problems with site imports related with both file uploads and user imports. Some workarounds: http://ithemes.com/forum/topic/37186-backupbuddy-ms-import-not-working-on-wp-35-multisite/&lt;br /&gt;
&lt;br /&gt;
* '''Restore entire Multisite Network (same server &amp;amp; URLs)'''&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a restore, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish restores under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Migrate entire Multisite Network (different server or URLs)'''&lt;br /&gt;
** Limitation: When migrating a Network to a new server or changing URLs, domains, or moving a Network in or out of a subdirectory, BackupBuddy will only migrate the database tables associated with the MAIN site. Due to technical reasons BackupBuddy currently will not automatically migrate URLs or paths of any other subsites within the migrated network.  If the URLs or paths of subsites need to be updated you may perform this procedure by using the 'Mass Database Text Replacement' tool on the 'Server Information' page within BackupBuddy for each subsite you need to update.&lt;br /&gt;
** Limitation: You cannot change from sub-domains to sub-directory URL structure using BackupBuddy Multisite nor can you change from sub-directories to sub-domain URL structure.&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a migration, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish migrations under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Export a subsite from the Network'''&lt;br /&gt;
** Exported subsites may be imported back into the same network (AKA Duplicated), imported into another Network, or restored as a standalone WordPress site using the importbuddy.php tool.&lt;br /&gt;
** Limitation: The main Network [sub]site cannot be exported as it is tied to the Network. It is still included in the main Network backup however.&lt;br /&gt;
&lt;br /&gt;
* '''Import an exported subsite into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Import a backed up standalone site into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Restore or Migrate an exported subsite as a standalone site'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
=Running Backup, Migrating OR Restoring with BackupBuddy Multisite BETA=&lt;br /&gt;
&lt;br /&gt;
Here is an actual video, from one of our many webinars (we have many regular webinars planned), with details on how to migrate or restore with BackupBuddy. Note: Some functionality has changed and improved since this video was made. It is not the latest version.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|WYhLIK3KfK4|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
=Frequently Asked Questions=&lt;br /&gt;
&lt;br /&gt;
====Are multiple Multisite databases supported?====&lt;br /&gt;
No. A couple of plugins, such as Multi-DB allow Multisite networks to run on multiple databases instead of the normal one.  We do not currently support this custom 3rd party configuration.&lt;br /&gt;
&lt;br /&gt;
====WordPress Multisite Domain Mapping and BackupBuddy Multisite====&lt;br /&gt;
&lt;br /&gt;
Domain mapping was confirmed by customers to work in pre-v3.0 BackupBuddy versions. It has not been officially tested with &amp;gt; 3.0 versions. Customer reports of success/failure are welcomed. Note: Some functionality has changed and improved since this video was made. It is not the latest version.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|oDM5v2Ymk1M|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
====Support Questions====&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Multisite support questions can be asked in the official [http://ithemes.com/forum/backupbuddy-ms/ BackupBuddy Multisite Forums]. &lt;br /&gt;
&lt;br /&gt;
non-Multisite related BackupBuddy support questions can be asked in the official [http://ithemes.com/forum/backupbuddy/ BackupBuddy Forums].&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Pre-Sales questions, for Multisite OR non-Multisite backups and restores/migrations, can be asked on the [http://ithemes.com/forum/pre-sales-and-other-inquiries/ Pre-Sales Forums], via the Live Chat (the Panda icon on top of [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite] page), or by emailing sales@ithemes.com&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
====Official Pages====&lt;br /&gt;
*[http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy]&lt;br /&gt;
*[http://ithemes.com/codex/page/BackupBuddy BackupBuddy Codex - Self-Hosted and Multisite combined]&lt;br /&gt;
====Blog Posts====&lt;br /&gt;
*[http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ 5 Reasons to Love BackupBuddy with Multisite Support - Blog Article]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy Multisite Migration - Expanded Features in Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-ms-released-as-a-beta/ BackupBuddy Multisite Released as Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/how-backupbuddy-changed-my-business-model/ How BackupBuddy changed one of our customer's entire business model!]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy:_Error_Codes</id>
		<title>BackupBuddy: Error Codes</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy:_Error_Codes"/>
				<updated>2013-01-06T10:23:12Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==3382==&lt;br /&gt;
&amp;lt;strong&amp;gt;Backup FAILED. Unable to successfully generate ZIP archive. Error #3382.12:20:04: Failed function backup_zip_files. Backup terminated.&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* The 3382 error literally means that both command line zip AND pclzip were unable to create a .zip file and failed for some reason.&lt;br /&gt;
* Possible causes:&lt;br /&gt;
** Command line zip is being actively killed. (Cheapest packages at Godaddy kill off exec() within about 10 seconds, throwing the user into compatibility mode which cannot handle larger sites).&lt;br /&gt;
** Permissions may be blocking backup file creation. Make sure permissions are set to 755 for the /wp-content/uploads/ directory recursively.&lt;br /&gt;
** Your hosting account may not have enough free space to create the backup file.&lt;br /&gt;
** There may be one or more files/folders being included in the backup which neither the native zip command nor the pclzip function are able to access, e.g., unreadable files or broken symbolic links&lt;br /&gt;
* Possible solutions:&lt;br /&gt;
** If you have BackupBuddy Version 2.2.29 or later then visit the Settings page and enable the Alternative Zip System option and save. Then repeat a Full backup and study the Advanced Details for indications of failure.&lt;br /&gt;
*** For the native zip command alternatives there will usually be an exit code followed by some general descriptive text concerning the reason for failure (such as being unable to read a file, lack of disk space, etc.).&lt;br /&gt;
*** If the failure is file based then unfortunately at present we are unable to isolate the specific file details from this command. However, the backup will fall back to the Compatibility Mode and the failure indication from that will almost certainly provide a specific indication of the file (including the absolute file path) that is causing the issue. In such a case you must correct the issue by making the file readable if that is appropriate for the file or alternatively use the Exclusions on the Settings page to exclude the folder that contains the bad file.&lt;br /&gt;
*** If you cannot make the file readable and you cannot exclude the folder (because it contains other files that you need) then you will need to consult your host support to try and resolve what is the issue with the file.&lt;br /&gt;
*** If you are having trouble interpreting the diagnostic information in the Advanced Details then please create a topic in the BackupBuddy Forum and we can help explain it to you - however, this doesn't mean to say that we can resolve the issue as it relates to your files and server.&lt;br /&gt;
** Verify permissions are set correctly for /wp-content/uploads/ recursively to 755.&lt;br /&gt;
** Verify allowed disk usage isn't close or exceeded. (ie Your hosting account is limited to 5GB and you've used 4.95GB.)&lt;br /&gt;
** Reducing backup size often helps. (directory exclusion, etc)&lt;br /&gt;
** Turning Zip Compression on or off may help.&lt;br /&gt;
** Have at least double the amount of defined storage quota available (or the same amount of free space as your used disk space) so that the backup can be created.&lt;br /&gt;
* Related link:&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/17953-backup-failure/#p85314&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/20145-another-solution-to-error-3382/&lt;br /&gt;
&lt;br /&gt;
==9001==&lt;br /&gt;
'''Unable to read database table wp_redirection_logs. Your backup will not include data from this table (you may ignore this warning if you do not need this specific data). This is due to the following error: MySQL client ran out of memory in /www/wp-content/plugins/backupbuddy/backupbuddy.php  on line 1757'''&lt;br /&gt;
&lt;br /&gt;
* '''MySQL client ran out of memory'''&lt;br /&gt;
** This is typically caused by your PHP memory limit being low, resulting in part of the data returned being clipped.  If you do not need the data from this specific table of the database to be backed up then you may safely ignore this.  Some tables, such as wp_redirection_logs, contain logs that you most likely do not need.&lt;br /&gt;
** BackupBuddy attempts to increase the PHP memory limit on runtime but many hosts block this.&lt;br /&gt;
** Add/modify this line in your php.ini with a higher number than the default, such as: php_value memory_limit 128M&lt;br /&gt;
** PHP memory is separate from mysql memory. Your host has to up the mysql memory as it is not possible for you the client to do so at all. &lt;br /&gt;
* '''Unable to save result set'''&lt;br /&gt;
** This is typically caused by a corrupt database/table. [http://textpattern.com/faq/36/warning-unable-to-save-result-set/ Citation of problem.]&lt;br /&gt;
** Repair the database/table using a tool such as phpMyAdmin or the free plugin [http://wordpress.org/extend/plugins/wp-dbmanager/ WP-dbManager]&lt;br /&gt;
** Add this line to wp-config.php to allow WordPress to repair tables: define('WP_ALLOW_REPAIR', true)&lt;br /&gt;
* '''MySQL server has gone away'''&lt;br /&gt;
** MySQL server is dying, this is mostly a host issue. Probably need to contact host to get them to fix the issue.&lt;br /&gt;
* WordPress Revisions may also be clogging up the system&lt;br /&gt;
** Disabling WordPress' automatic revisions, or at least limiting how many to keep, can help with this error&lt;br /&gt;
** http://codex.wordpress.org/Editing_wp-config.php#Post_Revisions&lt;br /&gt;
&lt;br /&gt;
==9002==&lt;br /&gt;
'''Unable to create temporary storage directory ((/www/wp-content/uploads/temp_xxxxxxxxxx)'''&lt;br /&gt;
&lt;br /&gt;
*This error means that BackupBuddy was unable to create a temporary storage directory at the location listed in the error message.  BackupBuddy must temporarily create this directory to place temporary files to be backed up into the ZIP file.&lt;br /&gt;
* Adjust permissions to allow write &amp;amp; directory creation access to your uploads folder. ie: /www/wp-content/uploads/&lt;br /&gt;
&lt;br /&gt;
==9003==&lt;br /&gt;
&lt;br /&gt;
'''BackupBuddy data file (backupbuddy_dat.php) missing or unreadable. There may be a problem with the backup file, the files could not be extracted (you may manually extract the zip file in this directory to manually do this portion of restore), or the files were deleted before this portion of the restore was reached. Start the import process over or try manually extracting (unzipping) the files then starting over. Restore will not continue to protect integrity of any existing data.'''&lt;br /&gt;
&lt;br /&gt;
* This error is often caused by the importbuddy.php script being replaced by an older version during the unzip step. See [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Old_importbuddy_overwriting_on_unzip importbuddy overwriting on unzip]&lt;br /&gt;
* This error is often caused by the server timing out before zip file extraction could complete.&lt;br /&gt;
** Manually extract files using either cPanel or extracting (unzipping) the files locally then uploading them &amp;amp; selecting the importbuddy.php advanced option to skip file extraction.&lt;br /&gt;
** Ask your server host to extend the maximum script execution time.&lt;br /&gt;
** Create a custom php.ini file if your host allows for this.&lt;br /&gt;
*** Tutorial: Create custom php.ini &amp;amp; enable in cPanel: http://pluginbuddy.com/tutorials/custom_php_ini/&lt;br /&gt;
*** Dreamhost users may use this tool if they do not want to use the above method: http://sxi.sabrextreme.com/dh-phpini&lt;br /&gt;
*** Increase php.ini max_execution_time&lt;br /&gt;
** Change hosts &amp;amp; let your current host know why you changed.&lt;br /&gt;
* Additional potential causes (very rare):&lt;br /&gt;
** File permissions not allowing reading of the backupbuddy_dat.php file.&lt;br /&gt;
** Incomplete backup. Verify the backup is marked as Good on the source site.&lt;br /&gt;
&lt;br /&gt;
==9004==&lt;br /&gt;
&lt;br /&gt;
'''Error! The unzip process reported success but the backup data file, backupbuddy_dat.php was not found in the extracted files. The unzip process either failed (most likely) or the zip file is not a proper BackupBuddy backup.''' (importbuddy.php)&lt;br /&gt;
&lt;br /&gt;
* Manually extract backup ZIP. This usually resolves this issue.&lt;br /&gt;
* Force compatibility mode to see if it able to unzip to completion.&lt;br /&gt;
* Contact the host to see if they can verify that the Linux command line ZIP is set up properly.&lt;br /&gt;
&lt;br /&gt;
==9005==&lt;br /&gt;
&lt;br /&gt;
'''File extraction process did not complete successfully. Unable to continue to next step. Manually extract the backup ZIP file and choose to &amp;quot;Skip File Extraction&amp;quot; from the advanced options on Step 1.''' (importbuddy.php)&lt;br /&gt;
* This ZIP file was unable to be extracted for some reason.&lt;br /&gt;
** Unzipping may have taken too long and the PHP process halted.&lt;br /&gt;
** Server memory usage may have been exceeded.&lt;br /&gt;
** Server configuration may be blocking extracting of ZIP files.&lt;br /&gt;
&lt;br /&gt;
* Attempt manual extraction &amp;amp; disable File Extraction from the advanced debugging options of Step 1.&lt;br /&gt;
&lt;br /&gt;
==9006==&lt;br /&gt;
'''ERROR: Unable to connect to database server and/or log in. Verify the database server name, username, and password.''' (importbuddy.php)&lt;br /&gt;
* Verify the server address, your username, and your password. One of these settings is wrong.&lt;br /&gt;
* cPanel sometimes prefixes your username with a prefix. Check if this exists.&lt;br /&gt;
&lt;br /&gt;
==9007==&lt;br /&gt;
'''Unable to select your specified database. Verify the database name and that you have set up proper permissions for your specified username to access it.''' (importbuddy.php)&lt;br /&gt;
* Verify the database name exists.&lt;br /&gt;
* Verify the mysql username has been granted ALL permissions to this database.&lt;br /&gt;
&lt;br /&gt;
==9008==&lt;br /&gt;
'''ERROR: A database prefix is required for importing.''' (importbuddy.php)&lt;br /&gt;
* You must specify a WordPress database table prefix. Default is &amp;quot;wp_&amp;quot; without quotes.&lt;br /&gt;
&lt;br /&gt;
==9009==&lt;br /&gt;
'''ERROR: Unable to find any database backup data in the selected backup.''' (importbuddy.php)&lt;br /&gt;
* Database file is missing from the backup.&lt;br /&gt;
&lt;br /&gt;
==9010==&lt;br /&gt;
'''ERROR: Unable to import SQL query:''' (importbuddy.php)&lt;br /&gt;
* Something went wrong attempting to import this row into the database.&lt;br /&gt;
* If it says duplicate table or row then the user is importing/migrating into a database that has an existing WordPress installation with the same prefix. This could cause problems if it's a different install or a lot has changed.&lt;br /&gt;
&lt;br /&gt;
==9011==&lt;br /&gt;
'''ERROR #9011.  FTP/FTPs login failed on scheduled FTP. Credentials: username:password@server.com.'''&lt;br /&gt;
* Unable to log in to FTP or FTPs server due to a problem with the login credentials. Verify your username and password.&lt;br /&gt;
&lt;br /&gt;
==9012==&lt;br /&gt;
'''FTP/FTPs file upload failed. Check file permissions &amp;amp; disk quota. Details: [additional details here]'''&lt;br /&gt;
* BackupBuddy was able to connect to the FTP server but was not able to upload the file.&lt;br /&gt;
* Verify file permissions allow writing and that enough disk space is available.&lt;br /&gt;
&lt;br /&gt;
==9013==&lt;br /&gt;
'''Sorry! PHP version x.x or newer is required for BackupBuddy to properly run. You are running PHP version x.x.x.'''&lt;br /&gt;
* BackupBuddy currently requires PHP 5.x.  See the Sales page or [[BackupBuddy]] codex page for the latest version requirements.&lt;br /&gt;
* Most hosts allow you to change the PHP version from their control panel.&lt;br /&gt;
&lt;br /&gt;
==9014==&lt;br /&gt;
'''Fatal error. The database already contains a WordPress installation with this prefix (27 tables). Restore has been stopped to prevent overwriting existing data. Please go back and enter a new database name and/or prefix OR clear our your database prior to restoring again.'''&lt;br /&gt;
* WordPress already exists in the database/prefix combo entered.&lt;br /&gt;
* Choose a new prefix, database, or delete the existing WordPress tables from the database.&lt;br /&gt;
&lt;br /&gt;
==9015==&lt;br /&gt;
'''Temp data directory is not writable. Check your permissions. (#directory#)'''&lt;br /&gt;
* Verify user permissions for this directory. Make sure the user can create &amp;amp; write files.&lt;br /&gt;
* Use SUPHP so PHP will run as your user.  This insures it will have proper file/directory permissions.&lt;br /&gt;
&lt;br /&gt;
==9016==&lt;br /&gt;
'''Archive file is not writable. is not writable. Check your permissions. (#directory#)'''&lt;br /&gt;
* Verify user permissions for this directory. Make sure the user can create &amp;amp; write files.&lt;br /&gt;
* Use SUPHP so PHP will run as your user.  This insures it will have proper file/directory permissions.&lt;br /&gt;
&lt;br /&gt;
==9017==&lt;br /&gt;
'''Temp data file is not creatable/writable. Check your permissions. (#directory#)'''&lt;br /&gt;
* Verify user permissions for this directory. Make sure the user can create &amp;amp; write files.&lt;br /&gt;
* Use SUPHP so PHP will run as your user.  This insures it will have proper file/directory permissions.&lt;br /&gt;
&lt;br /&gt;
==9018==&lt;br /&gt;
'''Database file is not creatable/writable. Check your permissions. (#directory#)'''&lt;br /&gt;
* Verify user permissions for this directory. Make sure the user can create &amp;amp; write files.&lt;br /&gt;
* Use SUPHP so PHP will run as your user.  This insures it will have proper file/directory permissions.&lt;br /&gt;
&lt;br /&gt;
==9019==&lt;br /&gt;
'''Invalid or corrupt AJAX data. (#DATA#)'''&lt;br /&gt;
* The backup data sent by the browser was invalid. Refresh and try again.&lt;br /&gt;
* Make sure you are using a modern browser on a stable internet connection.&lt;br /&gt;
&lt;br /&gt;
==9020==&lt;br /&gt;
'''Unable to write to file [.htaccess/wp-config.php]. Permissions are preventing this file from being modified.'''&lt;br /&gt;
* Verify write permissions are properly configured for this file. Suggestion: 755.&lt;br /&gt;
* For .htaccess: Another option is to delete the .htaccess file &amp;amp; in the WordPress admin navigate to Settings: Permalinks &amp;amp; click the Save button to regenerate the file.&lt;br /&gt;
&lt;br /&gt;
==9021==&lt;br /&gt;
'''PHP Timeout or Fatal Error Occurred'''&lt;br /&gt;
* &amp;quot;The page did not finish loading as expected. The most common cause for this is the PHP process taking more time than it has been allowed by your host (php.ini setting max_execution_time). If a PHP error is displayed above this can also cause this error. &amp;quot;&lt;br /&gt;
* Increase the maximum allowed PHP runtime by contacting your host or creating a php.ini file to override host settings (if allowed).&lt;br /&gt;
* If on the unzip step, manually extract the ZIP file on your local PC then upload or use another server-based software such as cpanel.&lt;br /&gt;
&lt;br /&gt;
==9022==&lt;br /&gt;
'''Error: Unable to create backup storage directory `/www/wp-content/uploads/backupbuddy_backups/`. Please verify that proper write permissions are enabled to create this directory. You may also manually create this directory. If you do so make sure to give permissions to allow writing backups into this directory.'''&lt;br /&gt;
&lt;br /&gt;
*This error means that BackupBuddy was unable to create a storage directory at the location listed in the error message.  BackupBuddy must create this directory to place backup files into.&lt;br /&gt;
* Adjust permissions to allow write &amp;amp; directory creation access to your uploads folder. ie: /www/wp-content/uploads/&lt;br /&gt;
&lt;br /&gt;
==9023==&lt;br /&gt;
'''The backup is of a full Multisite Network. You cannot import a Network into a Network. You may only import standalone sites and sites exported from a Multisite.'''&lt;br /&gt;
* If you want to import a site from a Multisite Network you must first use BackupBuddy to export a site from it.  You can then import that individually exported site into another Multisite Network using BackupBuddy's Multisite Import or even as a standalone site with importbuddy.php.&lt;br /&gt;
&lt;br /&gt;
==9024==&lt;br /&gt;
'''ERROR #9024: Connected to Amazon S3 but unable to put file. There is a problem with one of the following S3 settings: bucket, directory, or S3 permissions. Details: ...'''&lt;br /&gt;
* In the destination settings page click the button to test the connection to verify the settings.&lt;br /&gt;
* Try manually sending a backup.&lt;br /&gt;
* See the Details portion of this error at the end for advanced troubleshooting information. This may be helpful for support or the developers.&lt;br /&gt;
&lt;br /&gt;
==9025==&lt;br /&gt;
'''ERROR #9025: Connected to Rackspace but unable to put file. Verify Rackspace settings included Rackspace permissions, etc.'''&lt;br /&gt;
&lt;br /&gt;
==9026==&lt;br /&gt;
'''ERROR #9026: The mySQL server went away unexpectedly during database dump. This is almost always caused by mySQL running out of memory. The backup integrity can no longer be guaranteed so the backup has been halted. 'Last table dumped before database server went away: `wp_#####`.'''&lt;br /&gt;
* Ask host to increase mysql memory.&lt;br /&gt;
* Reduce database [table(s)] size.&lt;br /&gt;
&lt;br /&gt;
==9027==&lt;br /&gt;
'''ERROR #9027: The mySQL server went away and was unavailable for scheduling the next cron step. This is almost always caused by mySQL running out of memory. The backup integrity can no longer be guaranteed so the backup has been halted.'''&lt;br /&gt;
* This is the same issue as 9026 except that it may have happened after a different step than the database dump.&lt;br /&gt;
* See 9026.&lt;br /&gt;
&lt;br /&gt;
==9028==&lt;br /&gt;
'''ERROR #9028: Based on your backup archive limits (size limit) the backup that was just created would be deleted. Skipped deleting this backup. Please update your archive limits.'''&lt;br /&gt;
* Your archive size limit is less than the backup file size. This would result in all backup files being deleted, including the latest, which would result in zero backups. The last backup has been kept for safety.&lt;br /&gt;
* Adjust the backup size limit to a larger value or reduce the size of your backups by deleting files or excluding directories.&lt;br /&gt;
&lt;br /&gt;
==9029==&lt;br /&gt;
'''Error #9029: Table `TABLE_NAME` does not contain a primary key; BackupBuddy cannot safely modify the contents of this table. Skipping migration of this table. ([serialized()|bruteforce_table()])'''&lt;br /&gt;
* This table is not set up properly. All tables should have a PRIMARY key and/or a UNIQUE key. Mysql automatically returns the first fully unique key if available if a primary key does not exist.&lt;br /&gt;
* If a plugin created the reported table contact the author to have this corrected.&lt;br /&gt;
&lt;br /&gt;
==9030==&lt;br /&gt;
'''mysqlbuddy: Error #9030. Command did not exit normally. Falling back to database dump compatibility modes.'''&lt;br /&gt;
* Occurs when command line mysql is reported to be available but still failed. BackupBuddy cannot always capture command line mysql error messages.&lt;br /&gt;
* Common causes:&lt;br /&gt;
** One or more tables that was attempted to be imported already existed.&lt;br /&gt;
&lt;br /&gt;
==9031==&lt;br /&gt;
&amp;quot;Error #9031. Invalid backup serial (xxxxxxxxxx). Please check directory permissions and your PHP error_log as an early backup function (such as pre_backup) may have failed. Fatal error.&amp;quot;&lt;br /&gt;
* This is a fatal error which will halt the backup process. You must fix whatever is causing it before BackupBuddy can continue.&lt;br /&gt;
* This basically means that when BackupBuddy tried to load backup information for the unique backup your browser requested information on, no information was found. Please try the following fixes:&lt;br /&gt;
**1 : Fix the file and folder permissions on all your BackupBuddy folders and the wp-content/uploads folder to allow proper writing permissions. &lt;br /&gt;
**2 : Make sure you have plenty of free disk space.&lt;br /&gt;
**3 : Upgrade to the latest version of BackupBuddy to make sure you are not encountering any old bugs or we have improved workarounds for your server issue.&lt;br /&gt;
&lt;br /&gt;
*Related forum threads&lt;br /&gt;
**[http://ithemes.com/forum/index.php?/topic/13796-error-5445589-invalid-backup-serial/ File permissions causing 5445589 error]&lt;br /&gt;
**[http://ithemes.com/forum/index.php?/topic/14834-error-5445589-invalid-backup-serial-0i64w23keq-fatal-error/ Increase the available disk space]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==9032==&lt;br /&gt;
''BackupBuddy Error #9032: You have not set a password to download this script yet. Please do so on the Settings page. You should have been prompted for a password when you clicked to download this script. If you are seeing this then most likely another plugin is loading its javascript on our plugin page causing it to break. Try disabling all other plugins to see if that fixes it. If so then turn them back on one by one until you find the offending plugin. You may also view your browser javascript error console to check for any script errors to help diagnose the issue.''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==9033==&lt;br /&gt;
&amp;quot;Error #9033: The pre-backup initialization did not fully complete. Check for any errors above or in logs. Verify permissions &amp;amp; that there is enough server memory. See the BackupBuddy &amp;quot;Server Information&amp;quot; page to help assess your server.&amp;quot;&lt;br /&gt;
* One known cause: Server ran out of memory at some point during the pre_backup() initialization procedure, possibly during importbuddy generation.  Check PHP error log for memory errors.  Increase server memory for probably fix.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==3488439==&lt;br /&gt;
'''Error scheduling event with WordPress. Your schedule may not work properly. Please try again. Error #3488439.'''&lt;br /&gt;
* This means the built-in WordPress function wp_schedule_event() is returning false. The only thing that can cause that is another plugin or something filtering/blocking scheduling of events. So can try deactivating/disabling all other plugins and then see if it clears it up. If it does then one of them was conflicting and can reactivate the plugins one at a time to find which one causes it again.&lt;br /&gt;
** Letting the conflicting plugin's author know about the conflict is good to do as well so they can update their plugin and fix it&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==5445589==&lt;br /&gt;
'''Error #5445589 – Invalid b/u serial Verify b/u directory writer permission'''&lt;br /&gt;
* SEE ERROR #9031 ABOVE.&lt;br /&gt;
&lt;br /&gt;
==4543849498==&lt;br /&gt;
'''Error #4543849498. Missing old home URL.&lt;br /&gt;
Failed. Your current backup does not include a home URL. Make a new backup with the latest BackupBuddy before migrating.'''&lt;br /&gt;
* Error means that the backup file being used for the migration/restore is much older than the importbuddy version being used.&lt;br /&gt;
** Use a backup .zip file created from an up to date BackupBuddy (or at least a version not as old)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==8438934984==&lt;br /&gt;
'''Error #8438934984: dbimport class missing option in constructor $options variable.'''&lt;br /&gt;
* Error means that at the point of starting the database import importbuddy is missing one of the following: backup file identifier (the random 10 character string at the end of the backup file name); the database server address; the database name; the database user; the database password; the table prefix to use; or the table prefix that was previously used.&lt;br /&gt;
* Especially for the cases where migrating to a local server with root having no password&lt;br /&gt;
** For that case then the resolution is to create a database user and associated password and associate these with the specific database (as would be the case on a commercial host) and then use that user rather than &amp;quot;root&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
* Related forum threads:&lt;br /&gt;
** [http://ithemes.com/forum/topic/21500-restore-error-8438934984/page__p__100824#entry100824 Restore Error 8438934984]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Additional Resources==&lt;br /&gt;
# [[BackupBuddy: Advanced Debugging]]&lt;br /&gt;
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]&lt;br /&gt;
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]&lt;br /&gt;
# [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
# [http://pluginbuddy.com/support/ Support Forums]&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy:_Error_Codes</id>
		<title>BackupBuddy: Error Codes</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy:_Error_Codes"/>
				<updated>2012-11-12T23:04:15Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==3382==&lt;br /&gt;
&amp;lt;strong&amp;gt;Backup FAILED. Unable to successfully generate ZIP archive. Error #3382.12:20:04: Failed function backup_zip_files. Backup terminated.&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* The 3382 error literally means that both command line zip AND pclzip were unable to create a .zip file and failed for some reason.&lt;br /&gt;
* Possible causes:&lt;br /&gt;
** Command line zip is being actively killed. (Cheapest packages at Godaddy kill off exec() within about 10 seconds, throwing the user into compatibility mode which cannot handle larger sites).&lt;br /&gt;
** Permissions may be blocking backup file creation. Make sure permissions are set to 755 for the /wp-content/uploads/ directory recursively.&lt;br /&gt;
** Your hosting account may not have enough free space to create the backup file.&lt;br /&gt;
** There may be one or more files/folders being included in the backup which neither the native zip command nor the pclzip function are able to access, e.g., unreadable files or broken symbolic links&lt;br /&gt;
* Possible solutions:&lt;br /&gt;
** If you have BackupBuddy Version 2.2.29 or later then visit the Settings page and enable the Alternative Zip System option and save. Then repeat a Full backup and study the Advanced Details for indications of failure.&lt;br /&gt;
*** For the native zip command alternatives there will usually be an exit code followed by some general descriptive text concerning the reason for failure (such as being unable to read a file, lack of disk space, etc.).&lt;br /&gt;
*** If the failure is file based then unfortunately at present we are unable to isolate the specific file details from this command. However, the backup will fall back to the Compatibility Mode and the failure indication from that will almost certainly provide a specific indication of the file (including the absolute file path) that is causing the issue. In such a case you must correct the issue by making the file readable if that is appropriate for the file or alternatively use the Exclusions on the Settings page to exclude the folder that contains the bad file.&lt;br /&gt;
*** If you cannot make the file readable and you cannot exclude the folder (because it contains other files that you need) then you will need to consult your host support to try and resolve what is the issue with the file.&lt;br /&gt;
*** If you are having trouble interpreting the diagnostic information in the Advanced Details then please create a topic in the BackupBuddy Forum and we can help explain it to you - however, this doesn't mean to say that we can resolve the issue as it relates to your files and server.&lt;br /&gt;
** Verify permissions are set correctly for /wp-content/uploads/ recursively to 755.&lt;br /&gt;
** Verify allowed disk usage isn't close or exceeded. (ie Your hosting account is limited to 5GB and you've used 4.95GB.)&lt;br /&gt;
** Reducing backup size often helps. (directory exclusion, etc)&lt;br /&gt;
** Turning Zip Compression on or off may help.&lt;br /&gt;
** Have at least double the amount of defined storage quota available (or the same amount of free space as your used disk space) so that the backup can be created.&lt;br /&gt;
* Related link:&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/17953-backup-failure/#p85314&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/20145-another-solution-to-error-3382/&lt;br /&gt;
&lt;br /&gt;
==9001==&lt;br /&gt;
'''Unable to read database table wp_redirection_logs. Your backup will not include data from this table (you may ignore this warning if you do not need this specific data). This is due to the following error: MySQL client ran out of memory in /www/wp-content/plugins/backupbuddy/backupbuddy.php  on line 1757'''&lt;br /&gt;
&lt;br /&gt;
* '''MySQL client ran out of memory'''&lt;br /&gt;
** This is typically caused by your PHP memory limit being low, resulting in part of the data returned being clipped.  If you do not need the data from this specific table of the database to be backed up then you may safely ignore this.  Some tables, such as wp_redirection_logs, contain logs that you most likely do not need.&lt;br /&gt;
** BackupBuddy attempts to increase the PHP memory limit on runtime but many hosts block this.&lt;br /&gt;
** Add/modify this line in your php.ini with a higher number than the default, such as: php_value memory_limit 128M&lt;br /&gt;
** PHP memory is separate from mysql memory. Your host has to up the mysql memory as it is not possible for you the client to do so at all. &lt;br /&gt;
* '''Unable to save result set'''&lt;br /&gt;
** This is typically caused by a corrupt database/table. [http://textpattern.com/faq/36/warning-unable-to-save-result-set/ Citation of problem.]&lt;br /&gt;
** Repair the database/table using a tool such as phpMyAdmin or the free plugin [http://wordpress.org/extend/plugins/wp-dbmanager/ WP-dbManager]&lt;br /&gt;
** Add this line to wp-config.php to allow WordPress to repair tables: define('WP_ALLOW_REPAIR', true)&lt;br /&gt;
* '''MySQL server has gone away'''&lt;br /&gt;
** MySQL server is dying, this is mostly a host issue. Probably need to contact host to get them to fix the issue.&lt;br /&gt;
* WordPress Revisions may also be clogging up the system&lt;br /&gt;
** Disabling WordPress' automatic revisions, or at least limiting how many to keep, can help with this error&lt;br /&gt;
** http://codex.wordpress.org/Editing_wp-config.php#Post_Revisions&lt;br /&gt;
&lt;br /&gt;
==9002==&lt;br /&gt;
'''Unable to create temporary storage directory ((/www/wp-content/uploads/temp_xxxxxxxxxx)'''&lt;br /&gt;
&lt;br /&gt;
*This error means that BackupBuddy was unable to create a temporary storage directory at the location listed in the error message.  BackupBuddy must temporarily create this directory to place temporary files to be backed up into the ZIP file.&lt;br /&gt;
* Adjust permissions to allow write &amp;amp; directory creation access to your uploads folder. ie: /www/wp-content/uploads/&lt;br /&gt;
&lt;br /&gt;
==9003==&lt;br /&gt;
&lt;br /&gt;
'''BackupBuddy data file (backupbuddy_dat.php) missing or unreadable. There may be a problem with the backup file, the files could not be extracted (you may manually extract the zip file in this directory to manually do this portion of restore), or the files were deleted before this portion of the restore was reached. Start the import process over or try manually extracting (unzipping) the files then starting over. Restore will not continue to protect integrity of any existing data.'''&lt;br /&gt;
&lt;br /&gt;
* This error is often caused by the importbuddy.php script being replaced by an older version during the unzip step. See [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Old_importbuddy_overwriting_on_unzip importbuddy overwriting on unzip]&lt;br /&gt;
* This error is often caused by the server timing out before zip file extraction could complete.&lt;br /&gt;
** Manually extract files using either cPanel or extracting (unzipping) the files locally then uploading them &amp;amp; selecting the importbuddy.php advanced option to skip file extraction.&lt;br /&gt;
** Ask your server host to extend the maximum script execution time.&lt;br /&gt;
** Create a custom php.ini file if your host allows for this.&lt;br /&gt;
*** Tutorial: Create custom php.ini &amp;amp; enable in cPanel: http://pluginbuddy.com/tutorials/custom_php_ini/&lt;br /&gt;
*** Dreamhost users may use this tool if they do not want to use the above method: http://sxi.sabrextreme.com/dh-phpini&lt;br /&gt;
*** Increase php.ini max_execution_time&lt;br /&gt;
** Change hosts &amp;amp; let your current host know why you changed.&lt;br /&gt;
* Additional potential causes (very rare):&lt;br /&gt;
** File permissions not allowing reading of the backupbuddy_dat.php file.&lt;br /&gt;
** Incomplete backup. Verify the backup is marked as Good on the source site.&lt;br /&gt;
&lt;br /&gt;
==9004==&lt;br /&gt;
&lt;br /&gt;
'''Error! The unzip process reported success but the backup data file, backupbuddy_dat.php was not found in the extracted files. The unzip process either failed (most likely) or the zip file is not a proper BackupBuddy backup.''' (importbuddy.php)&lt;br /&gt;
&lt;br /&gt;
* Manually extract backup ZIP. This usually resolves this issue.&lt;br /&gt;
* Force compatibility mode to see if it able to unzip to completion.&lt;br /&gt;
* Contact the host to see if they can verify that the Linux command line ZIP is set up properly.&lt;br /&gt;
&lt;br /&gt;
==9005==&lt;br /&gt;
&lt;br /&gt;
'''File extraction process did not complete successfully. Unable to continue to next step. Manually extract the backup ZIP file and choose to &amp;quot;Skip File Extraction&amp;quot; from the advanced options on Step 1.''' (importbuddy.php)&lt;br /&gt;
* This ZIP file was unable to be extracted for some reason.&lt;br /&gt;
** Unzipping may have taken too long and the PHP process halted.&lt;br /&gt;
** Server memory usage may have been exceeded.&lt;br /&gt;
** Server configuration may be blocking extracting of ZIP files.&lt;br /&gt;
&lt;br /&gt;
* Attempt manual extraction &amp;amp; disable File Extraction from the advanced debugging options of Step 1.&lt;br /&gt;
&lt;br /&gt;
==9006==&lt;br /&gt;
'''ERROR: Unable to connect to database server and/or log in. Verify the database server name, username, and password.''' (importbuddy.php)&lt;br /&gt;
* Verify the server address, your username, and your password. One of these settings is wrong.&lt;br /&gt;
* cPanel sometimes prefixes your username with a prefix. Check if this exists.&lt;br /&gt;
&lt;br /&gt;
==9007==&lt;br /&gt;
'''Unable to select your specified database. Verify the database name and that you have set up proper permissions for your specified username to access it.''' (importbuddy.php)&lt;br /&gt;
* Verify the database name exists.&lt;br /&gt;
* Verify the mysql username has been granted ALL permissions to this database.&lt;br /&gt;
&lt;br /&gt;
==9008==&lt;br /&gt;
'''ERROR: A database prefix is required for importing.''' (importbuddy.php)&lt;br /&gt;
* You must specify a WordPress database table prefix. Default is &amp;quot;wp_&amp;quot; without quotes.&lt;br /&gt;
&lt;br /&gt;
==9009==&lt;br /&gt;
'''ERROR: Unable to find any database backup data in the selected backup.''' (importbuddy.php)&lt;br /&gt;
* Database file is missing from the backup.&lt;br /&gt;
&lt;br /&gt;
==9010==&lt;br /&gt;
'''ERROR: Unable to import SQL query:''' (importbuddy.php)&lt;br /&gt;
* Something went wrong attempting to import this row into the database.&lt;br /&gt;
* If it says duplicate table or row then the user is importing/migrating into a database that has an existing WordPress installation with the same prefix. This could cause problems if it's a different install or a lot has changed.&lt;br /&gt;
&lt;br /&gt;
==9011==&lt;br /&gt;
'''ERROR #9011.  FTP/FTPs login failed on scheduled FTP. Credentials: username:password@server.com.'''&lt;br /&gt;
* Unable to log in to FTP or FTPs server due to a problem with the login credentials. Verify your username and password.&lt;br /&gt;
&lt;br /&gt;
==9012==&lt;br /&gt;
'''FTP/FTPs file upload failed. Check file permissions &amp;amp; disk quota. Details: [additional details here]'''&lt;br /&gt;
* BackupBuddy was able to connect to the FTP server but was not able to upload the file.&lt;br /&gt;
* Verify file permissions allow writing and that enough disk space is available.&lt;br /&gt;
&lt;br /&gt;
==9013==&lt;br /&gt;
'''Sorry! PHP version x.x or newer is required for BackupBuddy to properly run. You are running PHP version x.x.x.'''&lt;br /&gt;
* BackupBuddy currently requires PHP 5.x.  See the Sales page or [[BackupBuddy]] codex page for the latest version requirements.&lt;br /&gt;
* Most hosts allow you to change the PHP version from their control panel.&lt;br /&gt;
&lt;br /&gt;
==9014==&lt;br /&gt;
'''Fatal error. The database already contains a WordPress installation with this prefix (27 tables). Restore has been stopped to prevent overwriting existing data. Please go back and enter a new database name and/or prefix OR clear our your database prior to restoring again.'''&lt;br /&gt;
* WordPress already exists in the database/prefix combo entered.&lt;br /&gt;
* Choose a new prefix, database, or delete the existing WordPress tables from the database.&lt;br /&gt;
&lt;br /&gt;
==9015==&lt;br /&gt;
'''Temp data directory is not writable. Check your permissions. (#directory#)'''&lt;br /&gt;
* Verify user permissions for this directory. Make sure the user can create &amp;amp; write files.&lt;br /&gt;
* Use SUPHP so PHP will run as your user.  This insures it will have proper file/directory permissions.&lt;br /&gt;
&lt;br /&gt;
==9016==&lt;br /&gt;
'''Archive file is not writable. is not writable. Check your permissions. (#directory#)'''&lt;br /&gt;
* Verify user permissions for this directory. Make sure the user can create &amp;amp; write files.&lt;br /&gt;
* Use SUPHP so PHP will run as your user.  This insures it will have proper file/directory permissions.&lt;br /&gt;
&lt;br /&gt;
==9017==&lt;br /&gt;
'''Temp data file is not creatable/writable. Check your permissions. (#directory#)'''&lt;br /&gt;
* Verify user permissions for this directory. Make sure the user can create &amp;amp; write files.&lt;br /&gt;
* Use SUPHP so PHP will run as your user.  This insures it will have proper file/directory permissions.&lt;br /&gt;
&lt;br /&gt;
==9018==&lt;br /&gt;
'''Database file is not creatable/writable. Check your permissions. (#directory#)'''&lt;br /&gt;
* Verify user permissions for this directory. Make sure the user can create &amp;amp; write files.&lt;br /&gt;
* Use SUPHP so PHP will run as your user.  This insures it will have proper file/directory permissions.&lt;br /&gt;
&lt;br /&gt;
==9019==&lt;br /&gt;
'''Invalid or corrupt AJAX data. (#DATA#)'''&lt;br /&gt;
* The backup data sent by the browser was invalid. Refresh and try again.&lt;br /&gt;
* Make sure you are using a modern browser on a stable internet connection.&lt;br /&gt;
&lt;br /&gt;
==9020==&lt;br /&gt;
'''Unable to write to file [.htaccess/wp-config.php]. Permissions are preventing this file from being modified.'''&lt;br /&gt;
* Verify write permissions are properly configured for this file. Suggestion: 755.&lt;br /&gt;
* For .htaccess: Another option is to delete the .htaccess file &amp;amp; in the WordPress admin navigate to Settings: Permalinks &amp;amp; click the Save button to regenerate the file.&lt;br /&gt;
&lt;br /&gt;
==9021==&lt;br /&gt;
'''PHP Timeout or Fatal Error Occurred'''&lt;br /&gt;
* &amp;quot;The page did not finish loading as expected. The most common cause for this is the PHP process taking more time than it has been allowed by your host (php.ini setting max_execution_time). If a PHP error is displayed above this can also cause this error. &amp;quot;&lt;br /&gt;
* Increase the maximum allowed PHP runtime by contacting your host or creating a php.ini file to override host settings (if allowed).&lt;br /&gt;
* If on the unzip step, manually extract the ZIP file on your local PC then upload or use another server-based software such as cpanel.&lt;br /&gt;
&lt;br /&gt;
==9022==&lt;br /&gt;
'''Error: Unable to create backup storage directory `/www/wp-content/uploads/backupbuddy_backups/`. Please verify that proper write permissions are enabled to create this directory. You may also manually create this directory. If you do so make sure to give permissions to allow writing backups into this directory.'''&lt;br /&gt;
&lt;br /&gt;
*This error means that BackupBuddy was unable to create a storage directory at the location listed in the error message.  BackupBuddy must create this directory to place backup files into.&lt;br /&gt;
* Adjust permissions to allow write &amp;amp; directory creation access to your uploads folder. ie: /www/wp-content/uploads/&lt;br /&gt;
&lt;br /&gt;
==9023==&lt;br /&gt;
'''The backup is of a full Multisite Network. You cannot import a Network into a Network. You may only import standalone sites and sites exported from a Multisite.'''&lt;br /&gt;
* If you want to import a site from a Multisite Network you must first use BackupBuddy to export a site from it.  You can then import that individually exported site into another Multisite Network using BackupBuddy's Multisite Import or even as a standalone site with importbuddy.php.&lt;br /&gt;
&lt;br /&gt;
==9024==&lt;br /&gt;
'''ERROR #9024: Connected to Amazon S3 but unable to put file. There is a problem with one of the following S3 settings: bucket, directory, or S3 permissions. Details: ...'''&lt;br /&gt;
* In the destination settings page click the button to test the connection to verify the settings.&lt;br /&gt;
* Try manually sending a backup.&lt;br /&gt;
* See the Details portion of this error at the end for advanced troubleshooting information. This may be helpful for support or the developers.&lt;br /&gt;
&lt;br /&gt;
==9025==&lt;br /&gt;
'''ERROR #9025: Connected to Rackspace but unable to put file. Verify Rackspace settings included Rackspace permissions, etc.'''&lt;br /&gt;
&lt;br /&gt;
==9026==&lt;br /&gt;
'''ERROR #9026: The mySQL server went away unexpectedly during database dump. This is almost always caused by mySQL running out of memory. The backup integrity can no longer be guaranteed so the backup has been halted. 'Last table dumped before database server went away: `wp_#####`.'''&lt;br /&gt;
* Ask host to increase mysql memory.&lt;br /&gt;
* Reduce database [table(s)] size.&lt;br /&gt;
&lt;br /&gt;
==9027==&lt;br /&gt;
'''ERROR #9027: The mySQL server went away and was unavailable for scheduling the next cron step. This is almost always caused by mySQL running out of memory. The backup integrity can no longer be guaranteed so the backup has been halted.'''&lt;br /&gt;
* This is the same issue as 9026 except that it may have happened after a different step than the database dump.&lt;br /&gt;
* See 9026.&lt;br /&gt;
&lt;br /&gt;
==9028==&lt;br /&gt;
'''ERROR #9028: Based on your backup archive limits (size limit) the backup that was just created would be deleted. Skipped deleting this backup. Please update your archive limits.'''&lt;br /&gt;
* Your archive size limit is less than the backup file size. This would result in all backup files being deleted, including the latest, which would result in zero backups. The last backup has been kept for safety.&lt;br /&gt;
* Adjust the backup size limit to a larger value or reduce the size of your backups by deleting files or excluding directories.&lt;br /&gt;
&lt;br /&gt;
==9029==&lt;br /&gt;
'''Error #9029: Table `TABLE_NAME` does not contain a primary key; BackupBuddy cannot safely modify the contents of this table. Skipping migration of this table. ([serialized()|bruteforce_table()])'''&lt;br /&gt;
* This table is not set up properly. All tables should have a PRIMARY key and/or a UNIQUE key. Mysql automatically returns the first fully unique key if available if a primary key does not exist.&lt;br /&gt;
* If a plugin created the reported table contact the author to have this corrected.&lt;br /&gt;
&lt;br /&gt;
==9030==&lt;br /&gt;
'''mysqlbuddy: Error #9030. Command did not exit normally. Falling back to database dump compatibility modes.'''&lt;br /&gt;
* Occurs when command line mysql is reported to be available but still failed. BackupBuddy cannot always capture command line mysql error messages.&lt;br /&gt;
* Common causes:&lt;br /&gt;
** One or more tables that was attempted to be imported already existed.&lt;br /&gt;
&lt;br /&gt;
==9031==&lt;br /&gt;
&amp;quot;Error #9031. Invalid backup serial (xxxxxxxxxx). Please check directory permissions and your PHP error_log as an early backup function (such as pre_backup) may have failed. Fatal error.&amp;quot;&lt;br /&gt;
* This is a fatal error which will halt the backup process. You must fix whatever is causing it before BackupBuddy can continue.&lt;br /&gt;
* This basically means that when BackupBuddy tried to load backup information for the unique backup your browser requested information on, no information was found. Please try the following fixes:&lt;br /&gt;
**1 : Fix the file and folder permissions on all your BackupBuddy folders and the wp-content/uploads folder to allow proper writing permissions. &lt;br /&gt;
**2 : Make sure you have plenty of free disk space.&lt;br /&gt;
**3 : Upgrade to the latest version of BackupBuddy to make sure you are not encountering any old bugs or we have improved workarounds for your server issue.&lt;br /&gt;
&lt;br /&gt;
*Related forum threads&lt;br /&gt;
**[http://ithemes.com/forum/index.php?/topic/13796-error-5445589-invalid-backup-serial/ File permissions causing 5445589 error]&lt;br /&gt;
**[http://ithemes.com/forum/index.php?/topic/14834-error-5445589-invalid-backup-serial-0i64w23keq-fatal-error/ Increase the available disk space]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==9032==&lt;br /&gt;
''BackupBuddy Error #9032: You have not set a password to download this script yet. Please do so on the Settings page. You should have been prompted for a password when you clicked to download this script. If you are seeing this then most likely another plugin is loading its javascript on our plugin page causing it to break. Try disabling all other plugins to see if that fixes it. If so then turn them back on one by one until you find the offending plugin. You may also view your browser javascript error console to check for any script errors to help diagnose the issue.''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==3488439==&lt;br /&gt;
'''Error scheduling event with WordPress. Your schedule may not work properly. Please try again. Error #3488439.'''&lt;br /&gt;
* This means the built-in WordPress function wp_schedule_event() is returning false. The only thing that can cause that is another plugin or something filtering/blocking scheduling of events. So can try deactivating/disabling all other plugins and then see if it clears it up. If it does then one of them was conflicting and can reactivate the plugins one at a time to find which one causes it again.&lt;br /&gt;
** Letting the conflicting plugin's author know about the conflict is good to do as well so they can update their plugin and fix it&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==5445589==&lt;br /&gt;
'''Error #5445589 – Invalid b/u serial Verify b/u directory writer permission'''&lt;br /&gt;
* SEE ERROR #9031 ABOVE.&lt;br /&gt;
&lt;br /&gt;
==4543849498==&lt;br /&gt;
'''Error #4543849498. Missing old home URL.&lt;br /&gt;
Failed. Your current backup does not include a home URL. Make a new backup with the latest BackupBuddy before migrating.'''&lt;br /&gt;
* Error means that the backup file being used for the migration/restore is much older than the importbuddy version being used.&lt;br /&gt;
** Use a backup .zip file created from an up to date BackupBuddy (or at least a version not as old)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==8438934984==&lt;br /&gt;
'''Error #8438934984: dbimport class missing option in constructor $options variable.'''&lt;br /&gt;
* Error means that at the point of starting the database import importbuddy is missing one of the following: backup file identifier (the random 10 character string at the end of the backup file name); the database server address; the database name; the database user; the database password; the table prefix to use; or the table prefix that was previously used.&lt;br /&gt;
* Especially for the cases where migrating to a local server with root having no password&lt;br /&gt;
** For that case then the resolution is to create a database user and associated password and associate these with the specific database (as would be the case on a commercial host) and then use that user rather than &amp;quot;root&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
* Related forum threads:&lt;br /&gt;
** [http://ithemes.com/forum/topic/21500-restore-error-8438934984/page__p__100824#entry100824 Restore Error 8438934984]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Additional Resources==&lt;br /&gt;
# [[BackupBuddy: Advanced Debugging]]&lt;br /&gt;
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]&lt;br /&gt;
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]&lt;br /&gt;
# [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
# [http://pluginbuddy.com/support/ Support Forums]&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy:_Error_Codes</id>
		<title>BackupBuddy: Error Codes</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy:_Error_Codes"/>
				<updated>2012-11-12T23:03:48Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==3382==&lt;br /&gt;
&amp;lt;strong&amp;gt;Backup FAILED. Unable to successfully generate ZIP archive. Error #3382.12:20:04: Failed function backup_zip_files. Backup terminated.&amp;lt;/strong&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* The 3382 error literally means that both command line zip AND pclzip were unable to create a .zip file and failed for some reason.&lt;br /&gt;
* Possible causes:&lt;br /&gt;
** Command line zip is being actively killed. (Cheapest packages at Godaddy kill off exec() within about 10 seconds, throwing the user into compatibility mode which cannot handle larger sites).&lt;br /&gt;
** Permissions may be blocking backup file creation. Make sure permissions are set to 755 for the /wp-content/uploads/ directory recursively.&lt;br /&gt;
** Your hosting account may not have enough free space to create the backup file.&lt;br /&gt;
** There may be one or more files/folders being included in the backup which neither the native zip command nor the pclzip function are able to access, e.g., unreadable files or broken symbolic links&lt;br /&gt;
* Possible solutions:&lt;br /&gt;
** If you have BackupBuddy Version 2.2.29 or later then visit the Settings page and enable the Alternative Zip System option and save. Then repeat a Full backup and study the Advanced Details for indications of failure.&lt;br /&gt;
*** For the native zip command alternatives there will usually be an exit code followed by some general descriptive text concerning the reason for failure (such as being unable to read a file, lack of disk space, etc.).&lt;br /&gt;
*** If the failure is file based then unfortunately at present we are unable to isolate the specific file details from this command. However, the backup will fall back to the Compatibility Mode and the failure indication from that will almost certainly provide a specific indication of the file (including the absolute file path) that is causing the issue. In such a case you must correct the issue by making the file readable if that is appropriate for the file or alternatively use the Exclusions on the Settings page to exclude the folder that contains the bad file.&lt;br /&gt;
*** If you cannot make the file readable and you cannot exclude the folder (because it contains other files that you need) then you will need to consult your host support to try and resolve what is the issue with the file.&lt;br /&gt;
*** If you are having trouble interpreting the diagnostic information in the Advanced Details then please create a topic in the BackupBuddy Forum and we can help explain it to you - however, this doesn't mean to say that we can resolve the issue as it relates to your files and server.&lt;br /&gt;
** Verify permissions are set correctly for /wp-content/uploads/ recursively to 755.&lt;br /&gt;
** Verify allowed disk usage isn't close or exceeded. (ie Your hosting account is limited to 5GB and you've used 4.95GB.)&lt;br /&gt;
** Reducing backup size often helps. (directory exclusion, etc)&lt;br /&gt;
** Turning Zip Compression on or off may help.&lt;br /&gt;
** Have at least double the amount of defined storage quota available (or the same amount of free space as your used disk space) so that the backup can be created.&lt;br /&gt;
* Related link:&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/17953-backup-failure/#p85314&lt;br /&gt;
** http://ithemes.com/forum/index.php?/topic/20145-another-solution-to-error-3382/&lt;br /&gt;
&lt;br /&gt;
==9001==&lt;br /&gt;
'''Unable to read database table wp_redirection_logs. Your backup will not include data from this table (you may ignore this warning if you do not need this specific data). This is due to the following error: MySQL client ran out of memory in /www/wp-content/plugins/backupbuddy/backupbuddy.php  on line 1757'''&lt;br /&gt;
&lt;br /&gt;
* '''MySQL client ran out of memory'''&lt;br /&gt;
** This is typically caused by your PHP memory limit being low, resulting in part of the data returned being clipped.  If you do not need the data from this specific table of the database to be backed up then you may safely ignore this.  Some tables, such as wp_redirection_logs, contain logs that you most likely do not need.&lt;br /&gt;
** BackupBuddy attempts to increase the PHP memory limit on runtime but many hosts block this.&lt;br /&gt;
** Add/modify this line in your php.ini with a higher number than the default, such as: php_value memory_limit 128M&lt;br /&gt;
** PHP memory is separate from mysql memory. Your host has to up the mysql memory as it is not possible for you the client to do so at all. &lt;br /&gt;
* '''Unable to save result set'''&lt;br /&gt;
** This is typically caused by a corrupt database/table. [http://textpattern.com/faq/36/warning-unable-to-save-result-set/ Citation of problem.]&lt;br /&gt;
** Repair the database/table using a tool such as phpMyAdmin or the free plugin [http://wordpress.org/extend/plugins/wp-dbmanager/ WP-dbManager]&lt;br /&gt;
** Add this line to wp-config.php to allow WordPress to repair tables: define('WP_ALLOW_REPAIR', true)&lt;br /&gt;
* '''MySQL server has gone away'''&lt;br /&gt;
** MySQL server is dying, this is mostly a host issue. Probably need to contact host to get them to fix the issue.&lt;br /&gt;
* WordPress Revisions may also be clogging up the system&lt;br /&gt;
** Disabling WordPress' automatic revisions, or at least limiting how many to keep, can help with this error&lt;br /&gt;
** http://codex.wordpress.org/Editing_wp-config.php#Post_Revisions&lt;br /&gt;
&lt;br /&gt;
==9002==&lt;br /&gt;
'''Unable to create temporary storage directory ((/www/wp-content/uploads/temp_xxxxxxxxxx)'''&lt;br /&gt;
&lt;br /&gt;
*This error means that BackupBuddy was unable to create a temporary storage directory at the location listed in the error message.  BackupBuddy must temporarily create this directory to place temporary files to be backed up into the ZIP file.&lt;br /&gt;
* Adjust permissions to allow write &amp;amp; directory creation access to your uploads folder. ie: /www/wp-content/uploads/&lt;br /&gt;
&lt;br /&gt;
==9003==&lt;br /&gt;
&lt;br /&gt;
'''BackupBuddy data file (backupbuddy_dat.php) missing or unreadable. There may be a problem with the backup file, the files could not be extracted (you may manually extract the zip file in this directory to manually do this portion of restore), or the files were deleted before this portion of the restore was reached. Start the import process over or try manually extracting (unzipping) the files then starting over. Restore will not continue to protect integrity of any existing data.'''&lt;br /&gt;
&lt;br /&gt;
* This error is often caused by the importbuddy.php script being replaced by an older version during the unzip step. See [http://ithemes.com/codex/page/BackupBuddy:_Frequent_Support_Issues#Old_importbuddy_overwriting_on_unzip importbuddy overwriting on unzip]&lt;br /&gt;
* This error is often caused by the server timing out before zip file extraction could complete.&lt;br /&gt;
** Manually extract files using either cPanel or extracting (unzipping) the files locally then uploading them &amp;amp; selecting the importbuddy.php advanced option to skip file extraction.&lt;br /&gt;
** Ask your server host to extend the maximum script execution time.&lt;br /&gt;
** Create a custom php.ini file if your host allows for this.&lt;br /&gt;
*** Tutorial: Create custom php.ini &amp;amp; enable in cPanel: http://pluginbuddy.com/tutorials/custom_php_ini/&lt;br /&gt;
*** Dreamhost users may use this tool if they do not want to use the above method: http://sxi.sabrextreme.com/dh-phpini&lt;br /&gt;
*** Increase php.ini max_execution_time&lt;br /&gt;
** Change hosts &amp;amp; let your current host know why you changed.&lt;br /&gt;
* Additional potential causes (very rare):&lt;br /&gt;
** File permissions not allowing reading of the backupbuddy_dat.php file.&lt;br /&gt;
** Incomplete backup. Verify the backup is marked as Good on the source site.&lt;br /&gt;
&lt;br /&gt;
==9004==&lt;br /&gt;
&lt;br /&gt;
'''Error! The unzip process reported success but the backup data file, backupbuddy_dat.php was not found in the extracted files. The unzip process either failed (most likely) or the zip file is not a proper BackupBuddy backup.''' (importbuddy.php)&lt;br /&gt;
&lt;br /&gt;
* Manually extract backup ZIP. This usually resolves this issue.&lt;br /&gt;
* Force compatibility mode to see if it able to unzip to completion.&lt;br /&gt;
* Contact the host to see if they can verify that the Linux command line ZIP is set up properly.&lt;br /&gt;
&lt;br /&gt;
==9005==&lt;br /&gt;
&lt;br /&gt;
'''File extraction process did not complete successfully. Unable to continue to next step. Manually extract the backup ZIP file and choose to &amp;quot;Skip File Extraction&amp;quot; from the advanced options on Step 1.''' (importbuddy.php)&lt;br /&gt;
* This ZIP file was unable to be extracted for some reason.&lt;br /&gt;
** Unzipping may have taken too long and the PHP process halted.&lt;br /&gt;
** Server memory usage may have been exceeded.&lt;br /&gt;
** Server configuration may be blocking extracting of ZIP files.&lt;br /&gt;
&lt;br /&gt;
* Attempt manual extraction &amp;amp; disable File Extraction from the advanced debugging options of Step 1.&lt;br /&gt;
&lt;br /&gt;
==9006==&lt;br /&gt;
'''ERROR: Unable to connect to database server and/or log in. Verify the database server name, username, and password.''' (importbuddy.php)&lt;br /&gt;
* Verify the server address, your username, and your password. One of these settings is wrong.&lt;br /&gt;
* cPanel sometimes prefixes your username with a prefix. Check if this exists.&lt;br /&gt;
&lt;br /&gt;
==9007==&lt;br /&gt;
'''Unable to select your specified database. Verify the database name and that you have set up proper permissions for your specified username to access it.''' (importbuddy.php)&lt;br /&gt;
* Verify the database name exists.&lt;br /&gt;
* Verify the mysql username has been granted ALL permissions to this database.&lt;br /&gt;
&lt;br /&gt;
==9008==&lt;br /&gt;
'''ERROR: A database prefix is required for importing.''' (importbuddy.php)&lt;br /&gt;
* You must specify a WordPress database table prefix. Default is &amp;quot;wp_&amp;quot; without quotes.&lt;br /&gt;
&lt;br /&gt;
==9009==&lt;br /&gt;
'''ERROR: Unable to find any database backup data in the selected backup.''' (importbuddy.php)&lt;br /&gt;
* Database file is missing from the backup.&lt;br /&gt;
&lt;br /&gt;
==9010==&lt;br /&gt;
'''ERROR: Unable to import SQL query:''' (importbuddy.php)&lt;br /&gt;
* Something went wrong attempting to import this row into the database.&lt;br /&gt;
* If it says duplicate table or row then the user is importing/migrating into a database that has an existing WordPress installation with the same prefix. This could cause problems if it's a different install or a lot has changed.&lt;br /&gt;
&lt;br /&gt;
==9011==&lt;br /&gt;
'''ERROR #9011.  FTP/FTPs login failed on scheduled FTP. Credentials: username:password@server.com.'''&lt;br /&gt;
* Unable to log in to FTP or FTPs server due to a problem with the login credentials. Verify your username and password.&lt;br /&gt;
&lt;br /&gt;
==9012==&lt;br /&gt;
'''FTP/FTPs file upload failed. Check file permissions &amp;amp; disk quota. Details: [additional details here]'''&lt;br /&gt;
* BackupBuddy was able to connect to the FTP server but was not able to upload the file.&lt;br /&gt;
* Verify file permissions allow writing and that enough disk space is available.&lt;br /&gt;
&lt;br /&gt;
==9013==&lt;br /&gt;
'''Sorry! PHP version x.x or newer is required for BackupBuddy to properly run. You are running PHP version x.x.x.'''&lt;br /&gt;
* BackupBuddy currently requires PHP 5.x.  See the Sales page or [[BackupBuddy]] codex page for the latest version requirements.&lt;br /&gt;
* Most hosts allow you to change the PHP version from their control panel.&lt;br /&gt;
&lt;br /&gt;
==9014==&lt;br /&gt;
'''Fatal error. The database already contains a WordPress installation with this prefix (27 tables). Restore has been stopped to prevent overwriting existing data. Please go back and enter a new database name and/or prefix OR clear our your database prior to restoring again.'''&lt;br /&gt;
* WordPress already exists in the database/prefix combo entered.&lt;br /&gt;
* Choose a new prefix, database, or delete the existing WordPress tables from the database.&lt;br /&gt;
&lt;br /&gt;
==9015==&lt;br /&gt;
'''Temp data directory is not writable. Check your permissions. (#directory#)'''&lt;br /&gt;
* Verify user permissions for this directory. Make sure the user can create &amp;amp; write files.&lt;br /&gt;
* Use SUPHP so PHP will run as your user.  This insures it will have proper file/directory permissions.&lt;br /&gt;
&lt;br /&gt;
==9016==&lt;br /&gt;
'''Archive file is not writable. is not writable. Check your permissions. (#directory#)'''&lt;br /&gt;
* Verify user permissions for this directory. Make sure the user can create &amp;amp; write files.&lt;br /&gt;
* Use SUPHP so PHP will run as your user.  This insures it will have proper file/directory permissions.&lt;br /&gt;
&lt;br /&gt;
==9017==&lt;br /&gt;
'''Temp data file is not creatable/writable. Check your permissions. (#directory#)'''&lt;br /&gt;
* Verify user permissions for this directory. Make sure the user can create &amp;amp; write files.&lt;br /&gt;
* Use SUPHP so PHP will run as your user.  This insures it will have proper file/directory permissions.&lt;br /&gt;
&lt;br /&gt;
==9018==&lt;br /&gt;
'''Database file is not creatable/writable. Check your permissions. (#directory#)'''&lt;br /&gt;
* Verify user permissions for this directory. Make sure the user can create &amp;amp; write files.&lt;br /&gt;
* Use SUPHP so PHP will run as your user.  This insures it will have proper file/directory permissions.&lt;br /&gt;
&lt;br /&gt;
==9019==&lt;br /&gt;
'''Invalid or corrupt AJAX data. (#DATA#)'''&lt;br /&gt;
* The backup data sent by the browser was invalid. Refresh and try again.&lt;br /&gt;
* Make sure you are using a modern browser on a stable internet connection.&lt;br /&gt;
&lt;br /&gt;
==9020==&lt;br /&gt;
'''Unable to write to file [.htaccess/wp-config.php]. Permissions are preventing this file from being modified.'''&lt;br /&gt;
* Verify write permissions are properly configured for this file. Suggestion: 755.&lt;br /&gt;
* For .htaccess: Another option is to delete the .htaccess file &amp;amp; in the WordPress admin navigate to Settings: Permalinks &amp;amp; click the Save button to regenerate the file.&lt;br /&gt;
&lt;br /&gt;
==9021==&lt;br /&gt;
'''PHP Timeout or Fatal Error Occurred'''&lt;br /&gt;
* &amp;quot;The page did not finish loading as expected. The most common cause for this is the PHP process taking more time than it has been allowed by your host (php.ini setting max_execution_time). If a PHP error is displayed above this can also cause this error. &amp;quot;&lt;br /&gt;
* Increase the maximum allowed PHP runtime by contacting your host or creating a php.ini file to override host settings (if allowed).&lt;br /&gt;
* If on the unzip step, manually extract the ZIP file on your local PC then upload or use another server-based software such as cpanel.&lt;br /&gt;
&lt;br /&gt;
==9022==&lt;br /&gt;
'''Error: Unable to create backup storage directory `/www/wp-content/uploads/backupbuddy_backups/`. Please verify that proper write permissions are enabled to create this directory. You may also manually create this directory. If you do so make sure to give permissions to allow writing backups into this directory.'''&lt;br /&gt;
&lt;br /&gt;
*This error means that BackupBuddy was unable to create a storage directory at the location listed in the error message.  BackupBuddy must create this directory to place backup files into.&lt;br /&gt;
* Adjust permissions to allow write &amp;amp; directory creation access to your uploads folder. ie: /www/wp-content/uploads/&lt;br /&gt;
&lt;br /&gt;
==9023==&lt;br /&gt;
'''The backup is of a full Multisite Network. You cannot import a Network into a Network. You may only import standalone sites and sites exported from a Multisite.'''&lt;br /&gt;
* If you want to import a site from a Multisite Network you must first use BackupBuddy to export a site from it.  You can then import that individually exported site into another Multisite Network using BackupBuddy's Multisite Import or even as a standalone site with importbuddy.php.&lt;br /&gt;
&lt;br /&gt;
==9024==&lt;br /&gt;
'''ERROR #9024: Connected to Amazon S3 but unable to put file. There is a problem with one of the following S3 settings: bucket, directory, or S3 permissions. Details: ...'''&lt;br /&gt;
* In the destination settings page click the button to test the connection to verify the settings.&lt;br /&gt;
* Try manually sending a backup.&lt;br /&gt;
* See the Details portion of this error at the end for advanced troubleshooting information. This may be helpful for support or the developers.&lt;br /&gt;
&lt;br /&gt;
==9025==&lt;br /&gt;
'''ERROR #9025: Connected to Rackspace but unable to put file. Verify Rackspace settings included Rackspace permissions, etc.'''&lt;br /&gt;
&lt;br /&gt;
==9026==&lt;br /&gt;
'''ERROR #9026: The mySQL server went away unexpectedly during database dump. This is almost always caused by mySQL running out of memory. The backup integrity can no longer be guaranteed so the backup has been halted. 'Last table dumped before database server went away: `wp_#####`.'''&lt;br /&gt;
* Ask host to increase mysql memory.&lt;br /&gt;
* Reduce database [table(s)] size.&lt;br /&gt;
&lt;br /&gt;
==9027==&lt;br /&gt;
'''ERROR #9027: The mySQL server went away and was unavailable for scheduling the next cron step. This is almost always caused by mySQL running out of memory. The backup integrity can no longer be guaranteed so the backup has been halted.'''&lt;br /&gt;
* This is the same issue as 9026 except that it may have happened after a different step than the database dump.&lt;br /&gt;
* See 9026.&lt;br /&gt;
&lt;br /&gt;
==9028==&lt;br /&gt;
'''ERROR #9028: Based on your backup archive limits (size limit) the backup that was just created would be deleted. Skipped deleting this backup. Please update your archive limits.'''&lt;br /&gt;
* Your archive size limit is less than the backup file size. This would result in all backup files being deleted, including the latest, which would result in zero backups. The last backup has been kept for safety.&lt;br /&gt;
* Adjust the backup size limit to a larger value or reduce the size of your backups by deleting files or excluding directories.&lt;br /&gt;
&lt;br /&gt;
==9029==&lt;br /&gt;
'''Error #9029: Table `TABLE_NAME` does not contain a primary key; BackupBuddy cannot safely modify the contents of this table. Skipping migration of this table. ([serialized()|bruteforce_table()])'''&lt;br /&gt;
* This table is not set up properly. All tables should have a PRIMARY key and/or a UNIQUE key. Mysql automatically returns the first fully unique key if available if a primary key does not exist.&lt;br /&gt;
* If a plugin created the reported table contact the author to have this corrected.&lt;br /&gt;
&lt;br /&gt;
==9030==&lt;br /&gt;
'''mysqlbuddy: Error #9030. Command did not exit normally. Falling back to database dump compatibility modes.'''&lt;br /&gt;
* Occurs when command line mysql is reported to be available but still failed. BackupBuddy cannot always capture command line mysql error messages.&lt;br /&gt;
* Common causes:&lt;br /&gt;
** One or more tables that was attempted to be imported already existed.&lt;br /&gt;
&lt;br /&gt;
==9031==&lt;br /&gt;
&amp;quot;Error #9031. Invalid backup serial (xxxxxxxxxx). Please check directory permissions and your PHP error_log as an early backup function (such as pre_backup) may have failed. Fatal error.&amp;quot;&lt;br /&gt;
* This is a fatal error which will halt the backup process. You must fix whatever is causing it before BackupBuddy can continue.&lt;br /&gt;
* This basically means that when BackupBuddy tried to load backup information for the unique backup your browser requested information on, no information was found. Please try the following fixes:&lt;br /&gt;
**1 : Fix the file and folder permissions on all your BackupBuddy folders and the wp-content/uploads folder to allow proper writing permissions. &lt;br /&gt;
**2 : Make sure you have plenty of free disk space.&lt;br /&gt;
**3 : Upgrade to the latest version of BackupBuddy to make sure you are not encountering any old bugs or we have improved workarounds for your server issue.&lt;br /&gt;
&lt;br /&gt;
==9032==&lt;br /&gt;
''BackupBuddy Error #9032: You have not set a password to download this script yet. Please do so on the Settings page. You should have been prompted for a password when you clicked to download this script. If you are seeing this then most likely another plugin is loading its javascript on our plugin page causing it to break. Try disabling all other plugins to see if that fixes it. If so then turn them back on one by one until you find the offending plugin. You may also view your browser javascript error console to check for any script errors to help diagnose the issue.''&lt;br /&gt;
&lt;br /&gt;
*Related forum threads&lt;br /&gt;
**[http://ithemes.com/forum/index.php?/topic/13796-error-5445589-invalid-backup-serial/ File permissions causing 5445589 error]&lt;br /&gt;
**[http://ithemes.com/forum/index.php?/topic/14834-error-5445589-invalid-backup-serial-0i64w23keq-fatal-error/ Increase the available disk space]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==3488439==&lt;br /&gt;
'''Error scheduling event with WordPress. Your schedule may not work properly. Please try again. Error #3488439.'''&lt;br /&gt;
* This means the built-in WordPress function wp_schedule_event() is returning false. The only thing that can cause that is another plugin or something filtering/blocking scheduling of events. So can try deactivating/disabling all other plugins and then see if it clears it up. If it does then one of them was conflicting and can reactivate the plugins one at a time to find which one causes it again.&lt;br /&gt;
** Letting the conflicting plugin's author know about the conflict is good to do as well so they can update their plugin and fix it&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==5445589==&lt;br /&gt;
'''Error #5445589 – Invalid b/u serial Verify b/u directory writer permission'''&lt;br /&gt;
* SEE ERROR #9031 ABOVE.&lt;br /&gt;
&lt;br /&gt;
==4543849498==&lt;br /&gt;
'''Error #4543849498. Missing old home URL.&lt;br /&gt;
Failed. Your current backup does not include a home URL. Make a new backup with the latest BackupBuddy before migrating.'''&lt;br /&gt;
* Error means that the backup file being used for the migration/restore is much older than the importbuddy version being used.&lt;br /&gt;
** Use a backup .zip file created from an up to date BackupBuddy (or at least a version not as old)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==8438934984==&lt;br /&gt;
'''Error #8438934984: dbimport class missing option in constructor $options variable.'''&lt;br /&gt;
* Error means that at the point of starting the database import importbuddy is missing one of the following: backup file identifier (the random 10 character string at the end of the backup file name); the database server address; the database name; the database user; the database password; the table prefix to use; or the table prefix that was previously used.&lt;br /&gt;
* Especially for the cases where migrating to a local server with root having no password&lt;br /&gt;
** For that case then the resolution is to create a database user and associated password and associate these with the specific database (as would be the case on a commercial host) and then use that user rather than &amp;quot;root&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
* Related forum threads:&lt;br /&gt;
** [http://ithemes.com/forum/topic/21500-restore-error-8438934984/page__p__100824#entry100824 Restore Error 8438934984]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Additional Resources==&lt;br /&gt;
# [[BackupBuddy: Advanced Debugging]]&lt;br /&gt;
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]&lt;br /&gt;
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]&lt;br /&gt;
# [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
# [http://pluginbuddy.com/support/ Support Forums]&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy_Multisite</id>
		<title>BackupBuddy Multisite</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy_Multisite"/>
				<updated>2012-10-30T21:40:25Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Introduction=&lt;br /&gt;
&lt;br /&gt;
Multisite support is a BETA UNSUPPORTED BONUS FEATURE provided in BackupBuddy to AID you in importing and exporting subsites with Multisite.  Due to the nature of Multisite we cannot provide the same level of thoroughness in migrations as with standalone sites.  You should NOT expect as smooth of an experience and we only recommend advanced users attempt to use Multisite functionality due to this.  As WordPress Multisite functionality is much more technically complex some BackupBuddy features available for standalone sites are NOT supports for Multisite environments.  Please carefully review the features, differences, and limitations so that you are aware of them and are sure it will meet your needs.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''BackupBuddy Multisite is a BETA product'''.  As such you ''may encounter issues'' using it and we cannot necessarily insure flawless functionality or that issues encountered will be resolved in as timely manner as non-beta features.  Usage of it in a production environment is at your own risk; Import/Export functionality is quite solid but Network migrations have some issues which require additional intervention to fully complete if the URL changes (see limitations below for full details). There is currently not a specific ETA on when the beta tag will be removed. It will be removed once we believe Multisite functionality to be as solid and reliable as the BackupBuddy standalone many have come to love.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Features &amp;amp; Limitation Notes=&lt;br /&gt;
&lt;br /&gt;
'''IMPORTANT: BackupBuddy Multisite does NOT support migrating entire Networks to a different URL. If you attempt to do so then only the main site URLs will be migrated and you must manually update all subsite URLs, for instance using the Server Information Page's Mass Database Replace Tool.'''&lt;br /&gt;
&lt;br /&gt;
* '''Backup entire Multisite Network'''&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a backup, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish backups under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Restore entire Multisite Network (same server &amp;amp; URLs)'''&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a restore, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish restores under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Migrate entire Multisite Network (different server or URLs)'''&lt;br /&gt;
** Limitation: When migrating a Network to a new server or changing URLs, domains, or moving a Network in or out of a subdirectory, BackupBuddy will only migrate the database tables associated with the MAIN site. Due to technical reasons BackupBuddy currently will not automatically migrate URLs or paths of any other subsites within the migrated network.  If the URLs or paths of subsites need to be updated you may perform this procedure by using the 'Mass Database Text Replacement' tool on the 'Server Information' page within BackupBuddy for each subsite you need to update.&lt;br /&gt;
** Limitation: You cannot change from sub-domains to sub-directory URL structure using BackupBuddy Multisite nor can you change from sub-directories to sub-domain URL structure.&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a migration, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish migrations under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Export a subsite from the Network'''&lt;br /&gt;
** Exported subsites may be imported back into the same network (AKA Duplicated), imported into another Network, or restored as a standalone WordPress site using the importbuddy.php tool.&lt;br /&gt;
** Limitation: The main Network [sub]site cannot be exported as it is tied to the Network. It is still included in the main Network backup however.&lt;br /&gt;
&lt;br /&gt;
* '''Import an exported subsite into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Import a backed up standalone site into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Restore or Migrate an exported subsite as a standalone site'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
=Running Backup, Migrating OR Restoring with BackupBuddy Multisite BETA=&lt;br /&gt;
&lt;br /&gt;
Here is an actual video, from one of our many webinars (we have many regular webinars planned), with details on how to migrate or restore with BackupBuddy. Note: Some functionality has changed and improved since this video was made. It is not the latest version.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|WYhLIK3KfK4|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
=Frequently Asked Questions=&lt;br /&gt;
&lt;br /&gt;
====Are multiple Multisite databases supported?====&lt;br /&gt;
No. A couple of plugins, such as Multi-DB allow Multisite networks to run on multiple databases instead of the normal one.  We do not currently support this custom 3rd party configuration.&lt;br /&gt;
&lt;br /&gt;
====WordPress Multisite Domain Mapping and BackupBuddy Multisite====&lt;br /&gt;
&lt;br /&gt;
Domain mapping was confirmed by customers to work in pre-v3.0 BackupBuddy versions. It has not been officially tested with &amp;gt; 3.0 versions. Customer reports of success/failure are welcomed. Note: Some functionality has changed and improved since this video was made. It is not the latest version.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|oDM5v2Ymk1M|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
====Support Questions====&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Multisite support questions can be asked in the official [http://ithemes.com/forum/backupbuddy-ms/ BackupBuddy Multisite Forums]. &lt;br /&gt;
&lt;br /&gt;
non-Multisite related BackupBuddy support questions can be asked in the official [http://ithemes.com/forum/backupbuddy/ BackupBuddy Forums].&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Pre-Sales questions, for Multisite OR non-Multisite backups and restores/migrations, can be asked on the [http://ithemes.com/forum/pre-sales-and-other-inquiries/ Pre-Sales Forums], via the Live Chat (the Panda icon on top of [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite] page), or by emailing sales@ithemes.com&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
====Official Pages====&lt;br /&gt;
*[http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy]&lt;br /&gt;
*[http://ithemes.com/codex/page/BackupBuddy BackupBuddy Codex - Self-Hosted and Multisite combined]&lt;br /&gt;
====Blog Posts====&lt;br /&gt;
*[http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ 5 Reasons to Love BackupBuddy with Multisite Support - Blog Article]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy Multisite Migration - Expanded Features in Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-ms-released-as-a-beta/ BackupBuddy Multisite Released as Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/how-backupbuddy-changed-my-business-model/ How BackupBuddy changed one of our customer's entire business model!]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy:_Hosts</id>
		<title>BackupBuddy: Hosts</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy:_Hosts"/>
				<updated>2012-10-29T23:19:11Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''We've created a free ebook resource titled How to Pick a Great Web Host without Having a Computer Science Degree.''' &lt;br /&gt;
&lt;br /&gt;
Download it here: [[Media:http://ithemes.com/publishing/how-to-pick-web-hosting-without-a-computer-science-degree/]]&lt;br /&gt;
&lt;br /&gt;
The information contained here is for shared hosting accounts unless specified otherwise.  Much of this information is provided by customers. Please contact your host for details and confirmation as this page should be used as a guideline only, not an official definitive source.&lt;br /&gt;
&lt;br /&gt;
==[http://1and1.com 1and1]==&lt;br /&gt;
* Servers sometimes overloaded causing browsing sites hosted on them to take a very long time to load or time out.&lt;br /&gt;
&lt;br /&gt;
==[http://aplus.net aPlus.net]==&lt;br /&gt;
'''Issues'''&lt;br /&gt;
* Problems reported with sites above 450mb (with zip compression on; off increases limit).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==[http://bluehost.com BlueHost]==&lt;br /&gt;
&lt;br /&gt;
Overall BlueHost hosting seems to be somewhat hit or miss.  Many customers have found that BlueHost is slow and often returns 404 and 500 server error messages for no reason periodically.  These can not only cause a bad experience for viewers of your site but also break BackupBuddy backup functionality.  Though in general BackupBuddy should work the lack of consistency among the experiences of users of this host results in us not being able to recommend this host.&lt;br /&gt;
&lt;br /&gt;
PHP memory limit is 128MB at MOST.  This is low.  Hostgator for example provides 256MB which is double.&lt;br /&gt;
&lt;br /&gt;
*One customer had an Addhandler line in .htaccess which gave issues when migrated to another host.&lt;br /&gt;
&lt;br /&gt;
Bluehost requires a database name (and user) to have a prefix of your username, so to be of the form username_databasename.&lt;br /&gt;
&lt;br /&gt;
===Timeouts===&lt;br /&gt;
On the boards, a few people have complained about BackupBuddy timing out during backup. To resolve this, support recommends editing your php.ini file to change max execution time to 600.&lt;br /&gt;
&lt;br /&gt;
According to response from tech support these are the limits on how long a process can run before being killed off and are based on whether the customer has a dedicated IP address or uses the shared address.&lt;br /&gt;
&lt;br /&gt;
*Apache/Web (HTML/PHP/Downloads): With Dedicated IP: 12 Hours  |  Without: 10 Minutes (up from 5 minutes)&lt;br /&gt;
*SSH/Shell: With Dedicated IP: 2 Hours  |  Without: 1 Hour&lt;br /&gt;
*Cron Jobs: With Dedicated IP: 30 Minutes  |  Without: 30 Minutes&lt;br /&gt;
*Deamons: With Dedicated IP: Unlimited  |  Without: 10 Minutes&lt;br /&gt;
&lt;br /&gt;
==[http://www.bluerazor.com BlueRazor]==&lt;br /&gt;
No cPanel&lt;br /&gt;
&lt;br /&gt;
==[http://dreamhost.com Dreamhost] - D (maybe F)==&lt;br /&gt;
&lt;br /&gt;
Note: As of August 2012 we are working with Dreamhost to clarify or resolve issues noted below. We will update this as this progresses. Thank you Dreamhost for so kindly working with us!&lt;br /&gt;
&lt;br /&gt;
'''Issues'''&lt;br /&gt;
* Does not allow HTTP Loopbacks (PHP connects back to site via curl to Site URL - ie http://yoursite.com ).&lt;br /&gt;
* Unlimited plans terms of service PROHIBITS storing of backups in your account.  &amp;quot;Unlimited&amp;quot; is not truly unlimited.&lt;br /&gt;
* Resource related:&lt;br /&gt;
** Extremely slow zip generation.&lt;br /&gt;
** Problems reported with sites above 22mb (with zip compression on; off increases limit) due to slow processing.&lt;br /&gt;
** Possible workaround: Can create a custom php.ini to extend PHP timeout to increase BackupBuddy run-time.&lt;br /&gt;
* No cPanel (uses custom system) - See Resources below for manual unzip functionality.&lt;br /&gt;
* Configuration related:&lt;br /&gt;
** No native command-line zip. BackupBuddy will enter the slower, less reliable compatibility mode.&lt;br /&gt;
** Procwatch automatically kills off BackupBuddy if it uses too many resources in the process of making a backup.&lt;br /&gt;
'''Notes'''&lt;br /&gt;
* Verify your mysql server as it may not be the common default localhost (for ImportBuddy migrations).&lt;br /&gt;
'''Resources'''&lt;br /&gt;
* File Manager (allows for manual unzipping): https://webftp.dreamhost.com/&lt;br /&gt;
&lt;br /&gt;
==[http://godaddy.com GoDaddy] - F==&lt;br /&gt;
&lt;br /&gt;
Note: Godaddy is currently working with us to try and improve known issues.  We will update this pending improvements.&lt;br /&gt;
&lt;br /&gt;
'''Issues'''&lt;br /&gt;
* Custom control panel. Some changes take up to hours to take effect.&lt;br /&gt;
* Slow site load times on some servers.&lt;br /&gt;
* Some servers overloaded not leaving processing power for backups.&lt;br /&gt;
* System actively kills any PHP process working too hard or too long (ie backups).&lt;br /&gt;
&lt;br /&gt;
==[http://secure.hostgator.com/cgi-bin/affiliates/clickthru.cgi?id=ithemes HostGator] A==&lt;br /&gt;
'''Benefits'''&lt;br /&gt;
* Fast. Command-line zip available for best BackupBuddy experience.&lt;br /&gt;
* CPanel.&lt;br /&gt;
'''Issues'''&lt;br /&gt;
* Recently changed PHP runtime limit cap to 30 seconds for shared hosting.&lt;br /&gt;
** Possible work-around: http://ithemes.com/forum/index.php?/topic/5519-hostgator-timeout-fix-available/&lt;br /&gt;
** Only causes issues with large sites ( ~1GB or more )&lt;br /&gt;
&lt;br /&gt;
'''Info'''&lt;br /&gt;
* Current limits of their shared and reseller hosting (9/20/2011)&lt;br /&gt;
** safe mode = Off (cannot adjust) &lt;br /&gt;
** memory_limit = 64M (MAXIMUM) &lt;br /&gt;
** max_execution_time = 30 (MAXIMUM) &lt;br /&gt;
** max_input_time = 60 (MAXIMUM) &lt;br /&gt;
** post_max_size = 64M (MAXIMUM) &lt;br /&gt;
** upload_max_filesize = 64M (MAXIMUM) &lt;br /&gt;
** enable_dl = Off (cannot adjust)&lt;br /&gt;
&lt;br /&gt;
==[http://inmotionhosting InMotionHosting]==&lt;br /&gt;
* Slow page loads.&lt;br /&gt;
* Problems reported with sites above 85mb (with zip compression on; off increases limit).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==[http://ipower.com iPower]==&lt;br /&gt;
Minimal issues.&lt;br /&gt;
&lt;br /&gt;
Told a customer that they don't support linux command line zip.&lt;br /&gt;
&lt;br /&gt;
==[http://ipowerweb.com ipowerweb]==&lt;br /&gt;
Minimal issues.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==[http://www.rackspace.com/cloud/ Rackspace Cloud Hosting]==&lt;br /&gt;
* Some reports of failing path/directory detection due to symlink issues, preventing backups.&lt;br /&gt;
* We have not had success or failure reports for Cloudsites hosting in a long period so we cannot accurately report the status.&lt;br /&gt;
&lt;br /&gt;
==[http://justhost.com JustHost]==&lt;br /&gt;
* JustHost blocks the command line ZIP command which is required for BackupBuddy's normal functionality.&lt;br /&gt;
* Compatibility mode is available but is only recommended for moving away from JustHost hosting.&lt;br /&gt;
&lt;br /&gt;
==[http://wpengine.com/b/ WPEngine]==&lt;br /&gt;
* We do NOT reccomend WPEngine for BackupBuddy compatibility.&lt;br /&gt;
** Command line zip via PHP exec() is blocked. You MUST enable &amp;quot;Alternate zip method&amp;quot; under troubleshooting for best functionality. WPEngine does NOT meet BackupBuddy requirements due to this.&lt;br /&gt;
*** Note: Backups will be severely limited due to this restriction.&lt;br /&gt;
** Blocks downloading of backup files via web for enhanced security purposes.&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy</id>
		<title>BackupBuddy</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy"/>
				<updated>2012-10-29T10:36:36Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: /* Frequently Seen Support Issues */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* '''New to BackupBuddy?''' Check out the [[BackupBuddy:_Getting_Started|Getting Started]] page.&lt;br /&gt;
* '''Problems?''' Check out the [[BackupBuddy:_Frequent_Support_Issues|Frequently Seen Support Issues]] page.&lt;br /&gt;
* '''Need hosting?''' ''Hostgator Coupons'' are available to BackupBuddy customers [http://ithemes.com/forum/index.php?/topic/14012-hostgator-coupons-for-our-community/ here].&lt;br /&gt;
* '''[http://ithemes.com/codex/page/BackupBuddy_Multisite BackupBuddy Multisite Codex]'''&lt;br /&gt;
&lt;br /&gt;
=Tutorials=&lt;br /&gt;
&lt;br /&gt;
===Installing BackupBuddy===&lt;br /&gt;
&lt;br /&gt;
Check out the [[Installing BackupBuddy]] section to see how BackupBuddy can be uploaded and activated on Single sites or Multisite networks or Multisite sites.&lt;br /&gt;
&lt;br /&gt;
===Getting Started===&lt;br /&gt;
Check out the [[BackupBuddy:_Getting_Started|Getting Started]] page to backup your Single sites or Multisite networks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Restore or Migrate===&lt;br /&gt;
Learn to [[BackupBuddy:_ImportBuddy|Restore or Migrate]] your Single sites or Multisite networks with the latest importbuddy.php.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Settings Explained===&lt;br /&gt;
Get in depth information about the various [[BackupBuddy:_Settings|Settings]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Developing Locally===&lt;br /&gt;
Set up your computer to [[BackupBuddy:_Local_Development|Develop Sites Locally]] and then migrate them to your live site.&lt;br /&gt;
&lt;br /&gt;
=Specifications=&lt;br /&gt;
Server configuration is a very complex topic and varies wildly between hosts, server operating systems, and even the personal preference of the server administrator. Below are the bare minimum requirements for the plugin along with the recommended setup to get the most out of this plugin. You may use [[ServerBuddy]] to help you determine how your server compares to our minimum requirements &amp;amp; recommendations.&lt;br /&gt;
&lt;br /&gt;
===Server Recommendations (full functionality)===&lt;br /&gt;
* PHP 5.2+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2 currently requires PHP 5.2+]&lt;br /&gt;
* mySQL 5.x+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2 currently requires mySQL 5.0.15+]&lt;br /&gt;
* WordPress 3.1+ &lt;br /&gt;
* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.&lt;br /&gt;
** Backups will be stored in /wp-content/uploads/backupbuddy_backups/&lt;br /&gt;
** Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)&lt;br /&gt;
* Free disk space equal to or greater than the entire size of your site once compressed.&lt;br /&gt;
** SuPHP or environment so that file operations/zip run as user to prevent permissions issues.&lt;br /&gt;
** PHP exec() function enabled&lt;br /&gt;
** PHP ZipArchive class installed&lt;br /&gt;
* Linux:&lt;br /&gt;
** Command-line zip installed and accessible via exec().&lt;br /&gt;
* Windows (only supported for local development via Apache; IIS is not officially supported):&lt;br /&gt;
** Windows zip executable (available [http://pluginbuddy.com/wp-content/uploads/2010/05/backupbuddy_windows_unzip.zip here])&lt;br /&gt;
*** You must have the ability to configure your server to allow execution of this zip.exe file for it to function.&lt;br /&gt;
*** File permissions must also be set to allow access and execution of the zip executable.&lt;br /&gt;
* wp-config.php file must be in WordPress installation directory OR (starting with v3.0) in the parent directory.&lt;br /&gt;
&lt;br /&gt;
===Minimum Server Requirements (reduced functionality)===&lt;br /&gt;
'' NOTE: Some features of BackupBuddy will be unavailable or limited if running on minimum requirements without recommendations. Large sites may not be able to be backed up with these minimum features.'''&lt;br /&gt;
* PHP 5.2+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2 will require PHP 5.2+]&lt;br /&gt;
* mySQL 4.x+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2 will require mySQL 5.0.15+]&lt;br /&gt;
* WordPress 3.0+&lt;br /&gt;
** We are trying to maintain bare minimum backup functionality for legacy versions as far back as WordPress v2.6 (though it's not pretty nor guaranteed to work perfectly at this time; we recommend only performing backups &amp;amp; direct restores for older versions and use it for safety while upgrading to the latest WordPress).&lt;br /&gt;
* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.&lt;br /&gt;
* BackupBuddy requires the uploads directory to be in the standard WordPress location.&lt;br /&gt;
** Backups will be stored in /wp-content/uploads/backupbuddy_backups/&lt;br /&gt;
** Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)&lt;br /&gt;
* Free disk space equal to or greater than the entire size of your site once compressed.&lt;br /&gt;
* wp-config.php file must be in WordPress installation directory OR (starting with v3.0) in the parent directory.&lt;br /&gt;
&lt;br /&gt;
===Host Compatibility===&lt;br /&gt;
Compare various [[BackupBuddy:_Hosts|Hosts &amp;amp; Hosting Environments]] to see how your host/potential host compares.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Misc. Information===&lt;br /&gt;
Find out some [[BackupBuddy:_Misc_Information|Miscellaneous Information]] about BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
	&lt;br /&gt;
=Troubleshooting=&lt;br /&gt;
&lt;br /&gt;
===Frequently Seen Support Issues===&lt;br /&gt;
''Problems?'' We have compiled a list of issues and solutions to many problems that we have seen encountered before. [[BackupBuddy:_Frequent_Support_Issues|Frequently Seen Support Issues]] to attempt to narrow down your problem and find a solution.&lt;br /&gt;
&lt;br /&gt;
===BackupBuddy: Error Codes===&lt;br /&gt;
Receive an error code? Check out the [[BackupBuddy:_Error_Codes|Error Codes]] page for explanations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Manual Migration===&lt;br /&gt;
Import fails on file extraction? Learn how to perform a [[BackupBuddy:_Manual_Migration|Manual Migration]] ... it's easier than you'd think!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
&lt;br /&gt;
'''Tools'''&lt;br /&gt;
&lt;br /&gt;
* [http://ithemes.com/codex/page/File:Zip_test.zip Manually test command line zip functionality]&lt;br /&gt;
&lt;br /&gt;
=Multisite=&lt;br /&gt;
&lt;br /&gt;
BackupBuddy supports the following Multisite functionality:&lt;br /&gt;
* Export a Multisite subsite to standalone&lt;br /&gt;
* Import an exported Multisite subsite into an existing Network&lt;br /&gt;
* Import a standalone WordPress site into an existing Network&lt;br /&gt;
* Backup entire Network&lt;br /&gt;
* Restore entire Network WITHOUT URL migration for subsites within if migrating to a new URL (URL changes have limitations. Please see Multisite page for details)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://ithemes.com/codex/page/BackupBuddy_Multisite Check out the BackupBuddy Multisite Codex] and [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite Beta Today!]&lt;br /&gt;
&lt;br /&gt;
BETA indicates that Multisite functionality has known issues and is not reccomended for production use except at your own risk.  We do NOT guarantee its functionality or provide guaranteed support for beta products.&lt;br /&gt;
&lt;br /&gt;
'''Links'''&lt;br /&gt;
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]&lt;br /&gt;
# [http://ithemes.com/codex/page/BackupBuddy_Multisite BackupBuddy Multisite Codex]&lt;br /&gt;
# [http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy beta Multisite support announcement]&lt;br /&gt;
# [http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ BackupBuddy beta Multisite key points everyone is raving about!] &lt;br /&gt;
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]&lt;br /&gt;
# [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
# [http://pluginbuddy.com/support/ Support Forums]&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy</id>
		<title>BackupBuddy</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy"/>
				<updated>2012-10-29T10:34:08Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* '''New to BackupBuddy?''' Check out the [[BackupBuddy:_Getting_Started|Getting Started]] page.&lt;br /&gt;
* '''Problems?''' Check out the [[BackupBuddy:_Frequent_Support_Issues|Frequently Seen Support Issues]] page.&lt;br /&gt;
* '''Need hosting?''' ''Hostgator Coupons'' are available to BackupBuddy customers [http://ithemes.com/forum/index.php?/topic/14012-hostgator-coupons-for-our-community/ here].&lt;br /&gt;
* '''[http://ithemes.com/codex/page/BackupBuddy_Multisite BackupBuddy Multisite Codex]'''&lt;br /&gt;
&lt;br /&gt;
=Tutorials=&lt;br /&gt;
&lt;br /&gt;
===Installing BackupBuddy===&lt;br /&gt;
&lt;br /&gt;
Check out the [[Installing BackupBuddy]] section to see how BackupBuddy can be uploaded and activated on Single sites or Multisite networks or Multisite sites.&lt;br /&gt;
&lt;br /&gt;
===Getting Started===&lt;br /&gt;
Check out the [[BackupBuddy:_Getting_Started|Getting Started]] page to backup your Single sites or Multisite networks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Restore or Migrate===&lt;br /&gt;
Learn to [[BackupBuddy:_ImportBuddy|Restore or Migrate]] your Single sites or Multisite networks with the latest importbuddy.php.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Settings Explained===&lt;br /&gt;
Get in depth information about the various [[BackupBuddy:_Settings|Settings]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Developing Locally===&lt;br /&gt;
Set up your computer to [[BackupBuddy:_Local_Development|Develop Sites Locally]] and then migrate them to your live site.&lt;br /&gt;
&lt;br /&gt;
=Specifications=&lt;br /&gt;
Server configuration is a very complex topic and varies wildly between hosts, server operating systems, and even the personal preference of the server administrator. Below are the bare minimum requirements for the plugin along with the recommended setup to get the most out of this plugin. You may use [[ServerBuddy]] to help you determine how your server compares to our minimum requirements &amp;amp; recommendations.&lt;br /&gt;
&lt;br /&gt;
===Server Recommendations (full functionality)===&lt;br /&gt;
* PHP 5.2+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2 currently requires PHP 5.2+]&lt;br /&gt;
* mySQL 5.x+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2 currently requires mySQL 5.0.15+]&lt;br /&gt;
* WordPress 3.1+ &lt;br /&gt;
* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.&lt;br /&gt;
** Backups will be stored in /wp-content/uploads/backupbuddy_backups/&lt;br /&gt;
** Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)&lt;br /&gt;
* Free disk space equal to or greater than the entire size of your site once compressed.&lt;br /&gt;
** SuPHP or environment so that file operations/zip run as user to prevent permissions issues.&lt;br /&gt;
** PHP exec() function enabled&lt;br /&gt;
** PHP ZipArchive class installed&lt;br /&gt;
* Linux:&lt;br /&gt;
** Command-line zip installed and accessible via exec().&lt;br /&gt;
* Windows (only supported for local development via Apache; IIS is not officially supported):&lt;br /&gt;
** Windows zip executable (available [http://pluginbuddy.com/wp-content/uploads/2010/05/backupbuddy_windows_unzip.zip here])&lt;br /&gt;
*** You must have the ability to configure your server to allow execution of this zip.exe file for it to function.&lt;br /&gt;
*** File permissions must also be set to allow access and execution of the zip executable.&lt;br /&gt;
* wp-config.php file must be in WordPress installation directory OR (starting with v3.0) in the parent directory.&lt;br /&gt;
&lt;br /&gt;
===Minimum Server Requirements (reduced functionality)===&lt;br /&gt;
'' NOTE: Some features of BackupBuddy will be unavailable or limited if running on minimum requirements without recommendations. Large sites may not be able to be backed up with these minimum features.'''&lt;br /&gt;
* PHP 5.2+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2 will require PHP 5.2+]&lt;br /&gt;
* mySQL 4.x+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2 will require mySQL 5.0.15+]&lt;br /&gt;
* WordPress 3.0+&lt;br /&gt;
** We are trying to maintain bare minimum backup functionality for legacy versions as far back as WordPress v2.6 (though it's not pretty nor guaranteed to work perfectly at this time; we recommend only performing backups &amp;amp; direct restores for older versions and use it for safety while upgrading to the latest WordPress).&lt;br /&gt;
* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.&lt;br /&gt;
* BackupBuddy requires the uploads directory to be in the standard WordPress location.&lt;br /&gt;
** Backups will be stored in /wp-content/uploads/backupbuddy_backups/&lt;br /&gt;
** Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)&lt;br /&gt;
* Free disk space equal to or greater than the entire size of your site once compressed.&lt;br /&gt;
* wp-config.php file must be in WordPress installation directory OR (starting with v3.0) in the parent directory.&lt;br /&gt;
&lt;br /&gt;
===Host Compatibility===&lt;br /&gt;
Compare various [[BackupBuddy:_Hosts|Hosts &amp;amp; Hosting Environments]] to see how your host/potential host compares.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Misc. Information===&lt;br /&gt;
Find out some [[BackupBuddy:_Misc_Information|Miscellaneous Information]] about BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
	&lt;br /&gt;
=Troubleshooting=&lt;br /&gt;
&lt;br /&gt;
===Frequently Seen Support Issues===&lt;br /&gt;
''Problems?'' Start with the [[BackupBuddy:_Frequent_Support_Issues|Frequently Seen Support Issues]] to most quickly troubleshoot your problem.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===BackupBuddy: Error Codes===&lt;br /&gt;
Receive an error code? Check out the [[BackupBuddy:_Error_Codes|Error Codes]] page for explanations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Manual Migration===&lt;br /&gt;
Import fails on file extraction? Learn how to perform a [[BackupBuddy:_Manual_Migration|Manual Migration]] ... it's easier than you'd think!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
&lt;br /&gt;
'''Tools'''&lt;br /&gt;
&lt;br /&gt;
* [http://ithemes.com/codex/page/File:Zip_test.zip Manually test command line zip functionality]&lt;br /&gt;
&lt;br /&gt;
=Multisite=&lt;br /&gt;
&lt;br /&gt;
BackupBuddy supports the following Multisite functionality:&lt;br /&gt;
* Export a Multisite subsite to standalone&lt;br /&gt;
* Import an exported Multisite subsite into an existing Network&lt;br /&gt;
* Import a standalone WordPress site into an existing Network&lt;br /&gt;
* Backup entire Network&lt;br /&gt;
* Restore entire Network WITHOUT URL migration for subsites within if migrating to a new URL (URL changes have limitations. Please see Multisite page for details)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://ithemes.com/codex/page/BackupBuddy_Multisite Check out the BackupBuddy Multisite Codex] and [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite Beta Today!]&lt;br /&gt;
&lt;br /&gt;
BETA indicates that Multisite functionality has known issues and is not reccomended for production use except at your own risk.  We do NOT guarantee its functionality or provide guaranteed support for beta products.&lt;br /&gt;
&lt;br /&gt;
'''Links'''&lt;br /&gt;
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]&lt;br /&gt;
# [http://ithemes.com/codex/page/BackupBuddy_Multisite BackupBuddy Multisite Codex]&lt;br /&gt;
# [http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy beta Multisite support announcement]&lt;br /&gt;
# [http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ BackupBuddy beta Multisite key points everyone is raving about!] &lt;br /&gt;
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]&lt;br /&gt;
# [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
# [http://pluginbuddy.com/support/ Support Forums]&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy:_ImportBuddy</id>
		<title>BackupBuddy: ImportBuddy</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy:_ImportBuddy"/>
				<updated>2012-10-11T09:25:19Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{#ev:vimeo|22918787|400|right}}&lt;br /&gt;
==Getting Started==&lt;br /&gt;
===Getting the ImportBuddy tool===&lt;br /&gt;
The ImportBuddy tool can be downloaded in BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
# Navigate to the `Backup &amp;amp; Restore` page.&lt;br /&gt;
# Click on the `ImportBuddy` link or `Restore / Migrate` button depending on your version.&lt;br /&gt;
#* Alternatively you may click the `Send` link beneath the `Restore / Migrate` button to directly send the tool to a remote destination.&lt;br /&gt;
# Save the script to your computer. (You will next upload this script to your destination server to begin using it)&lt;br /&gt;
&lt;br /&gt;
===Uploading ImportBuddy to your destination server===&lt;br /&gt;
* Decide on the FTP directory that you would like to migrate or restore the backup to (using an empty directory is best) that corresponds to the web URL you want your destination site to be at.&lt;br /&gt;
** For example, if you want your new site's URL to be &amp;quot;http://your.com/mybuddy/&amp;quot; then your server directory MIGHT be something like this &amp;quot;/usr/skyler/public_html/mybuddy/&amp;quot;; this is the directory you will then put importbuddy.php into. The directory structure varies host to host but often follows a similar format.&lt;br /&gt;
* Upload importbuddy.php and the backup zip file (don't rename the zip file!) to that FTP directory that corresponds to the URL you want.&lt;br /&gt;
* Navigate to the importbuddy.php file in your web browser after it has been uploaded.&lt;br /&gt;
** Example: &amp;lt;nowiki&amp;gt;http://newsite.com/importbuddy.php&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
* Follow the directions provided for each ImportBuddy step.&lt;br /&gt;
* If you encounter problems note the logging information displayed on the problem step when contacting support.&lt;br /&gt;
&lt;br /&gt;
==Accessing the ImportBuddy tool==&lt;br /&gt;
&lt;br /&gt;
In your web browser go to the URL corresponding to the FTP directory you uploaded to. For example, if you uploaded importbuddy.php to /usr/skyler/public_html/undiscoveredcorner/importbuddy.php then your ImportBuddy URL MIGHT be http://your.com/undiscoveredcorner/importbuddy.php&lt;br /&gt;
Upon going to this URL you will be prompted to log in to begin the import / restore process.  Follow the on-screen directions.&lt;br /&gt;
&lt;br /&gt;
==Log In - Password Authentication==&lt;br /&gt;
&lt;br /&gt;
This step asks for the password associated with the importbuddy.php file. ImportBuddy requires this to protect unauthorized access to your site and backup files before you have finished restoring. This password was previously set by you (or someone) on BackupBuddy's Settings page.&lt;br /&gt;
&lt;br /&gt;
''Typical Usage''&lt;br /&gt;
* Enter your password.&lt;br /&gt;
* Submit the form to continue. (Click the button to submit / continue to the next step)&lt;br /&gt;
&lt;br /&gt;
Misc Notes:&lt;br /&gt;
* The password is encoded inside your importbuddy.php file when it is made, so:&lt;br /&gt;
** If you share this importbuddy.php file to another for usage with a backup file you will need to provide the corresponding password.&lt;br /&gt;
** If you change the password will need to download a new copy of importbuddy.php; changing the password will NOT change it in existing importbuddy.php files.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Step 1==&lt;br /&gt;
On this step a listing of backup files that were found in the same directory as the importbuddy.php script are listed for your selection to restore / migrate. If you have not already uploaded your backup file along with the importbuddy.php file an upload feature is available for convenience. However, ''FTP is the best way to upload your backup archives (.zip files), especially for larger files.''.&lt;br /&gt;
&lt;br /&gt;
''Typical Usage''&lt;br /&gt;
* Select the backup you want to restore or migrate to this destination.&lt;br /&gt;
* Select any optional advanced options if needed or directed by technical support.&lt;br /&gt;
* Submit the form to continue.&lt;br /&gt;
&lt;br /&gt;
===Advanced Troubleshooting Options===&lt;br /&gt;
ImportBuddy automatically accounts for many server configurations and troubleshooting settings.  However, when ImportBuddy cannot automatically account for some difficulty or cannot automatically assume to do so safely, you have the option to control server options and features which can aid with working around server problems or troubleshooting possible issues.&lt;br /&gt;
&lt;br /&gt;
''Features''&lt;br /&gt;
* Skip zip file extraction.&lt;br /&gt;
** If enabled then Step 2 of ImportBuddy will skip unzipping / extracting your backup ZIP file. You will need to manually unzip the file somehow, such as on your local system and then uploading all files, or with a server-side tool such as within your host's control panel file manager (if available).&lt;br /&gt;
* Wipe all database tables. - Use caution.&lt;br /&gt;
** This features wipes (erases / deletes) ALL tables within the database you will later select. Use extreme caution with this feature as it could release in permanent loss of data / sites / content in your database if used improperly. This is typically used to clear out a database and start fresh for this restored site. - Use caution.&lt;br /&gt;
* Wipe only database tables matching prefix.&lt;br /&gt;
** This feature is like the above EXCEPT it only erases tables with the same prefix you enter.  Ie if you enter wp_ only tables starting with wp_ will be erased. Use caution.  This is typically used to overwrite a single existing site.&lt;br /&gt;
* Skip import of database.&lt;br /&gt;
** Useful if you only want to restore files and not import anything into your current database. Note: Your database will still be migrated unless disabled below.&lt;br /&gt;
* Skip migration of database.&lt;br /&gt;
** Useful if you only want to migrate the data in the already imported database (ie: You already imported a database or have an existing one and just need things like URLs and paths migrated.) Note: Your database will still be imported unless disabled above.&lt;br /&gt;
* Error Logging to importbuddy.txt&lt;br /&gt;
* Ignore SQL errors &amp;amp; hide them. Rarely used option for hiding error messages. This can be used if your server is reporting incorrect errors/warnings caused by misconfiguration and it's preventing you from continuing the restore.&lt;br /&gt;
* Skip migration of .htaccess file.&lt;br /&gt;
** Rarely used for technical purposes only.&lt;br /&gt;
* Force medium speed compatibility mode (ZipArchive).&lt;br /&gt;
** Bypass attempting to use command line zip. Rarely needed; troubleshooting.&lt;br /&gt;
* Force slow speed compatibility mode (PCLZip).&lt;br /&gt;
** Bypass both high speed mode and medium speed mode, falling back all the way to PCLZip (slow speed). Rarely needed; troubleshooting.&lt;br /&gt;
* Show detailed PHP warnings.&lt;br /&gt;
* PHP Maximum Execution Time&lt;br /&gt;
** Setting this a little lower can help force importbuddy to chunk the importing and migration of the database into multiple steps if large&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Step 2==&lt;br /&gt;
The file extraction process occurs during this step. ImportBuddy attempts to unzip / extract your backup ZIP archive (.zip file) into the same directory as the importbuddy.php script.&lt;br /&gt;
&lt;br /&gt;
ImportBuddy attempts to use the following techniques to unzip on your server:&lt;br /&gt;
* Command line zip on both Linux and Windows systems (if zip.exe is provided and properly granted security access to run). (Very fast and reliable) - BEST&lt;br /&gt;
* PHP's ZipArchive library. (decent speed; reliable) - MEDIUM LEVEL&lt;br /&gt;
* PCLZip (extracts the zip file using a PHP script; very low performance; relies on PHP memory limits which are commonly low) - WORST CASE&lt;br /&gt;
&lt;br /&gt;
'''If you are having difficulties getting past this step it is often simplest to just manually unzip your site locally on your computer and upload the files to the destination directory by FTP (or using cpanel to unzip) and on Step 1 of ImportBuddy, select the 'Advanced troubleshooting option' to `Skip file extraction`.'''  See the frequently seen support questions page if you want to troubleshoot why the unzip is failing.&lt;br /&gt;
&lt;br /&gt;
==Step 3==&lt;br /&gt;
This step is used to set the URL and database connection information. The information shown in parentheses is what importbuddy sees the values where previously, useful for a restore when most if not all of the information will be the same.&lt;br /&gt;
* WordPress Address&lt;br /&gt;
** This field will be pre-set using the information for the current directory the user is restoring/migrating to.&lt;br /&gt;
* MySQL Server&lt;br /&gt;
** This is the address to the mySQL server where your database will be stored.  99% of the time this is localhost.  The location of your mySQL server will be provided to you by your host if it differs.&lt;br /&gt;
* Database Name&lt;br /&gt;
** This is the name of the database you want to import your blog into. The database user must have permissions to be able to access this database.  If you are migrating this blog to a new host you will need to create this database (ie using CPanel or phpmyadmin) and create a mysql database user with permissions.&lt;br /&gt;
* Database User&lt;br /&gt;
** This is the database user account that has permission to access the database name in the input above.  This user must be given permission to this database for the import to work.&lt;br /&gt;
* Database Pass&lt;br /&gt;
** This is the password for the database user.&lt;br /&gt;
* Database Prefix&lt;br /&gt;
** This is the prefix given to all tables in the database.  If you are cloning the site on the same server AND the same database name then you will want to change this or else the imported database will overwrite the existing tables.&lt;br /&gt;
** The most common prefix is wp_ which is fine to use but if you want to use something else that is fine.&lt;br /&gt;
After entering the database information there is a button labelled &amp;quot;test database settings&amp;quot; that will test the validity of that connection information.&lt;br /&gt;
&lt;br /&gt;
==Step 4==&lt;br /&gt;
The database information is imported straight into the database. Your database with any old URLs / paths from the source server exist temporarily on the destination server. The next step will update this data in the database.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Step 5==&lt;br /&gt;
If your destination URL and/or file paths need to be updating due to using a new site URL or server directory stucture then ImportBuddy will proceed to migrate various data inside your database. Importbuddy searches through the database and updates any URLs, paths, settings, etc. that match your source site's settings (BackupBuddy recorded these settings for you in the backup for this functionality to work). The wp-config.php information (such as any new database settings) is set.&lt;br /&gt;
* Use the link of the site provided to verify that the site is fully migrated and complete before continuing to step 6.&lt;br /&gt;
* Can choose which of the import files get deleted in next step if desired. By default is all of them.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Step 6==&lt;br /&gt;
Cleanup step. This step attempts to delete any temporary files created by ImportBuddy or uploaded by you. If your restore is fully complete you can delete all of these files (assuming you have your backup zip stored elsewhere). Leaving these files could potentially be a security risk. If ImportBuddy is unable to delete these files please use your FTP client or web host's file management tools to delete them.&lt;br /&gt;
* Backup zip archive (.zip file)&lt;br /&gt;
* ImportBuddy Tool - importbuddy.php file (the tool you are using right now)&lt;br /&gt;
* Any temporary import files (db_1.sql, backupbuddy_dat.php, etc.)&lt;br /&gt;
* importbuddy-XXXXXXX.txt log file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy:_ImportBuddy</id>
		<title>BackupBuddy: ImportBuddy</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy:_ImportBuddy"/>
				<updated>2012-10-11T09:15:14Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{#ev:vimeo|22918787|400|right}}&lt;br /&gt;
==Getting Started==&lt;br /&gt;
===Getting the ImportBuddy tool===&lt;br /&gt;
The ImportBuddy tool can be downloaded in BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
# Navigate to the `Backup &amp;amp; Restore` page.&lt;br /&gt;
# Click on the `ImportBuddy` link or `Restore / Migrate` button depending on your version.&lt;br /&gt;
#* Alternatively you may click the `Send` link beneath the `Restore / Migrate` button to directly send the tool to a remote destination.&lt;br /&gt;
# Save the script to your computer. (You will next upload this script to your destination server to begin using it)&lt;br /&gt;
&lt;br /&gt;
===Uploading ImportBuddy to your destination server===&lt;br /&gt;
* Decide on the FTP directory that you would like to migrate or restore the backup to (using an empty directory is best) that corresponds to the web URL you want your destination site to be at.&lt;br /&gt;
** For example, if you want your new site's URL to be &amp;quot;http://your.com/mybuddy/&amp;quot; then your server directory MIGHT be something like this &amp;quot;/usr/skyler/public_html/mybuddy/&amp;quot;; this is the directory you will then put importbuddy.php into. The directory structure varies host to host but often follows a similar format.&lt;br /&gt;
* Upload importbuddy.php and the backup zip file (don't rename the zip file!) to that FTP directory that corresponds to the URL you want.&lt;br /&gt;
* Navigate to the importbuddy.php file in your web browser after it has been uploaded.&lt;br /&gt;
** Example: &amp;lt;nowiki&amp;gt;http://newsite.com/importbuddy.php&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
* Follow the directions provided for each ImportBuddy step.&lt;br /&gt;
* If you encounter problems note the logging information displayed on the problem step when contacting support.&lt;br /&gt;
&lt;br /&gt;
==Log In - Password Authentication==&lt;br /&gt;
&lt;br /&gt;
This step asks for the password associated with the importbuddy.php file. ImportBuddy requires this to protect unauthorized access to your site and backup files before you have finished restoring. This password was previously set by you (or someone) on BackupBuddy's Settings page.&lt;br /&gt;
&lt;br /&gt;
''Typical Usage''&lt;br /&gt;
* Enter your password.&lt;br /&gt;
* Submit the form to continue. (Click the button to submit / continue to the next step)&lt;br /&gt;
&lt;br /&gt;
Misc Notes:&lt;br /&gt;
* The password is encoded inside your importbuddy.php file when it is made, so:&lt;br /&gt;
** If you share this importbuddy.php file to another for usage with a backup file you will need to provide the corresponding password.&lt;br /&gt;
** If you change the password will need to download a new copy of importbuddy.php; changing the password will NOT change it in existing importbuddy.php files.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Step 1==&lt;br /&gt;
On this step a listing of backup files that were found in the same directory as the importbuddy.php script are listed for your selection to restore / migrate. If you have not already uploaded your backup file along with the importbuddy.php file an upload feature is available for convenience. However, ''FTP is the best way to upload your backup archives (.zip files), especially for larger files.''.&lt;br /&gt;
&lt;br /&gt;
''Typical Usage''&lt;br /&gt;
* Select the backup you want to restore or migrate to this destination.&lt;br /&gt;
* Select any optional advanced options if needed or directed by technical support.&lt;br /&gt;
* Submit the form to continue.&lt;br /&gt;
&lt;br /&gt;
===Advanced Troubleshooting Options===&lt;br /&gt;
ImportBuddy automatically accounts for many server configurations and troubleshooting settings.  However, when ImportBuddy cannot automatically account for some difficulty or cannot automatically assume to do so safely, you have the option to control server options and features which can aid with working around server problems or troubleshooting possible issues.&lt;br /&gt;
&lt;br /&gt;
''Features''&lt;br /&gt;
* Skip zip file extraction.&lt;br /&gt;
** If enabled then Step 2 of ImportBuddy will skip unzipping / extracting your backup ZIP file. You will need to manually unzip the file somehow, such as on your local system and then uploading all files, or with a server-side tool such as within your host's control panel file manager (if available).&lt;br /&gt;
* Wipe all database tables. - Use caution.&lt;br /&gt;
** This features wipes (erases / deletes) ALL tables within the database you will later select. Use extreme caution with this feature as it could release in permanent loss of data / sites / content in your database if used improperly. This is typically used to clear out a database and start fresh for this restored site. - Use caution.&lt;br /&gt;
* Wipe only database tables matching prefix.&lt;br /&gt;
** This feature is like the above EXCEPT it only erases tables with the same prefix you enter.  Ie if you enter wp_ only tables starting with wp_ will be erased. Use caution.  This is typically used to overwrite a single existing site.&lt;br /&gt;
* Skip import of database.&lt;br /&gt;
** Useful if you only want to restore files and not import anything into your current database. Note: Your database will still be migrated unless disabled below.&lt;br /&gt;
* Skip migration of database.&lt;br /&gt;
** Useful if you only want to migrate the data in the already imported database (ie: You already imported a database or have an existing one and just need things like URLs and paths migrated.) Note: Your database will still be imported unless disabled above.&lt;br /&gt;
* Error Logging to importbuddy.txt&lt;br /&gt;
* Ignore SQL errors &amp;amp; hide them. Rarely used option for hiding error messages. This can be used if your server is reporting incorrect errors/warnings caused by misconfiguration and it's preventing you from continuing the restore.&lt;br /&gt;
* Skip migration of .htaccess file.&lt;br /&gt;
** Rarely used for technical purposes only.&lt;br /&gt;
* Force medium speed compatibility mode (ZipArchive).&lt;br /&gt;
** Bypass attempting to use command line zip. Rarely needed; troubleshooting.&lt;br /&gt;
* Force slow speed compatibility mode (PCLZip).&lt;br /&gt;
** Bypass both high speed mode and medium speed mode, falling back all the way to PCLZip (slow speed). Rarely needed; troubleshooting.&lt;br /&gt;
* Show detailed PHP warnings.&lt;br /&gt;
* PHP Maximum Execution Time&lt;br /&gt;
** Setting this a little lower can help force importbuddy to chunk the importing and migration of the database into multiple steps if large&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Step 2==&lt;br /&gt;
The file extraction process occurs during this step. ImportBuddy attempts to unzip / extract your backup ZIP archive (.zip file) into the same directory as the importbuddy.php script.&lt;br /&gt;
&lt;br /&gt;
ImportBuddy attempts to use the following techniques to unzip on your server:&lt;br /&gt;
* Command line zip on both Linux and Windows systems (if zip.exe is provided and properly granted security access to run). (Very fast and reliable) - BEST&lt;br /&gt;
* PHP's ZipArchive library. (decent speed; reliable) - MEDIUM LEVEL&lt;br /&gt;
* PCLZip (extracts the zip file using a PHP script; very low performance; relies on PHP memory limits which are commonly low) - WORST CASE&lt;br /&gt;
&lt;br /&gt;
'''If you are having difficulties getting past this step it is often simplest to just manually unzip your site locally on your computer and upload the files to the destination directory by FTP (or using cpanel to unzip) and on Step 1 of ImportBuddy, select the 'Advanced troubleshooting option' to `Skip file extraction`.'''  See the frequently seen support questions page if you want to troubleshoot why the unzip is failing.&lt;br /&gt;
&lt;br /&gt;
==Step 3==&lt;br /&gt;
This step is used to set the URL and database connection information. The information shown in parentheses is what importbuddy sees the values where previously, useful for a restore when most if not all of the information will be the same.&lt;br /&gt;
* WordPress Address&lt;br /&gt;
** This field will be pre-set using the information for the current directory the user is restoring/migrating to.&lt;br /&gt;
* MySQL Server&lt;br /&gt;
** This is the address to the mySQL server where your database will be stored.  99% of the time this is localhost.  The location of your mySQL server will be provided to you by your host if it differs.&lt;br /&gt;
* Database Name&lt;br /&gt;
** This is the name of the database you want to import your blog into. The database user must have permissions to be able to access this database.  If you are migrating this blog to a new host you will need to create this database (ie using CPanel or phpmyadmin) and create a mysql database user with permissions.&lt;br /&gt;
* Database User&lt;br /&gt;
** This is the database user account that has permission to access the database name in the input above.  This user must be given permission to this database for the import to work.&lt;br /&gt;
* Database Pass&lt;br /&gt;
** This is the password for the database user.&lt;br /&gt;
* Database Prefix&lt;br /&gt;
** This is the prefix given to all tables in the database.  If you are cloning the site on the same server AND the same database name then you will want to change this or else the imported database will overwrite the existing tables.&lt;br /&gt;
** The most common prefix is wp_ which is fine to use but if you want to use something else that is fine.&lt;br /&gt;
After entering the database information there is a button labelled &amp;quot;test database settings&amp;quot; that will test the validity of that connection information.&lt;br /&gt;
&lt;br /&gt;
==Step 4==&lt;br /&gt;
The database information is imported straight into the database.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Step 5==&lt;br /&gt;
Importbuddy looks through the database and updates any URLs, paths, settings, etc. The wp-config.php information is set and the links are changed during this step.&lt;br /&gt;
* Use the link of the site provided to verify that the site is fully migrated and complete before continuing to step 6.&lt;br /&gt;
* Can choose which of the import files get deleted in next step if desired. By default is all of them.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Step 6==&lt;br /&gt;
Cleanup step. This step attempts to delete&lt;br /&gt;
* backup zip archive&lt;br /&gt;
* importbuddy.php&lt;br /&gt;
* temporary import files (db_1.sql, backupbuddy_dat.php, etc.)&lt;br /&gt;
* importbuddy.txt log file&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/IThemes_Codex</id>
		<title>IThemes Codex</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/IThemes_Codex"/>
				<updated>2012-10-11T08:40:00Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: /* Internal Codex Pages */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Welcome to the iThemes Codex. The purpose of this codex is to be a central repository for documentation and tutorials for our [http://ithemes.com/ themes (iThemes)] and [http://pluginbuddy.com plugins (formerly PluginBuddy)].&lt;br /&gt;
&lt;br /&gt;
The information on this codex is available to everyone and not just our customers. Our hope is that this information will benefit not just our community but the larger WordPress community as well.&lt;br /&gt;
&lt;br /&gt;
While read access is open to all, the ability to modify this site's content is restricted to our customers. Members with access to the [http://ithemes.com/forum/ iThemes Support Forum] will automatically have access here. Simply log into the forum first and then visit the Codex.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Internal Codex Pages ==&lt;br /&gt;
* [[BackupBuddy]]&lt;br /&gt;
** [[BackupBuddy: ImportBuddy|ImportBuddy Tool - Restore &amp;amp; Migrate]]&lt;br /&gt;
** [[BackupBuddy Multisite|Multisite Support (bonus beta feature)]]&lt;br /&gt;
* [[Builder]]&lt;br /&gt;
* [[PluginBuddy|Plugins]]&lt;br /&gt;
* [[Themes]]&lt;br /&gt;
* [[Forum Related]]&lt;br /&gt;
* [[:Category:Advanced Topics|Advanced Topics]]&lt;br /&gt;
* [[General WordPress Related]]&lt;br /&gt;
&lt;br /&gt;
== External Web Links ==&lt;br /&gt;
* [http://ithemes.com/ iThemes.com]&lt;br /&gt;
* [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
* [http://webdesign.com/ WebDesign.com]&lt;br /&gt;
* [http://ithemes.com/forum Support Forum]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Theme Documentation ==&lt;br /&gt;
* [[Themes]] - an overview of all themes, and all theme related information&lt;br /&gt;
* [[ThemesFAQ|Frequently Asked Questions]] - not specifically theme related&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Resources ==&lt;br /&gt;
* [[Basics]] - List of resources for learning basics of HTML and CSS&lt;br /&gt;
* [[WordPress]] - todo&lt;br /&gt;
* [[CSS]] - List of resources for learning CSS online&lt;br /&gt;
* [[HTML]] - todo&lt;br /&gt;
* [[jQuery]] - List of resources for learning jQuery online&lt;br /&gt;
* [[PHP]] - List of resources for learning PHP online&lt;br /&gt;
&lt;br /&gt;
== Wiki Editing ==&lt;br /&gt;
* [http://www.mediawiki.org/wiki/Help:Formatting Wiki Formatting Help]&lt;br /&gt;
&lt;br /&gt;
== Support Policies ==&lt;br /&gt;
* [[Support Policies]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy_Multisite</id>
		<title>BackupBuddy Multisite</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy_Multisite"/>
				<updated>2012-09-20T00:07:35Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: /* Features &amp;amp; Limitation Notes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Introduction=&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Multisite (BETA) functionality is included with the normal BackupBuddy plugin.  As WordPress Multisite functionality is much more technically complex some BackupBuddy features available for standalone sites are NOT supports for Multisite environments.  Please carefully review the features, differences, and limitations so that you are aware of them and are sure it will meet your needs.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''BackupBuddy Multisite is a BETA product'''.  As such you ''may encounter issues'' using it and we cannot necessarily insure flawless functionality or that issues encountered will be resolved in as timely manner as non-beta features.  Usage of it in a production environment is at your own risk; Import/Export functionality is quite solid but Network migrations have some issues which require additional intervention to fully complete if the URL changes (see limitations below for full details). There is currently not a specific ETA on when the beta tag will be removed. It will be removed once we believe Multisite functionality to be as solid and reliable as the BackupBuddy standalone many have come to love.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Features &amp;amp; Limitation Notes=&lt;br /&gt;
&lt;br /&gt;
'''IMPORTANT: BackupBuddy Multisite does NOT support migrating entire Networks to a different URL. If you attempt to do so then only the main site URLs will be migrated and you must manually update all subsite URLs, for instance using the Server Information Page's Mass Database Replace Tool.'''&lt;br /&gt;
&lt;br /&gt;
* '''Backup entire Multisite Network'''&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a backup, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish backups under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Restore entire Multisite Network (same server &amp;amp; URLs)'''&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a restore, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish restores under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Migrate entire Multisite Network (different server or URLs)'''&lt;br /&gt;
** Limitation: When migrating a Network to a new server or changing URLs, domains, or moving a Network in or out of a subdirectory, BackupBuddy will only migrate the database tables associated with the MAIN site. Due to technical reasons BackupBuddy currently will not automatically migrate URLs or paths of any other subsites within the migrated network.  If the URLs or paths of subsites need to be updated you may perform this procedure by using the 'Mass Database Text Replacement' tool on the 'Server Information' page within BackupBuddy for each subsite you need to update.&lt;br /&gt;
** Limitation: You cannot change from sub-domains to sub-directory URL structure using BackupBuddy Multisite nor can you change from sub-directories to sub-domain URL structure.&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a migration, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish migrations under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Export a subsite from the Network'''&lt;br /&gt;
** Exported subsites may be imported back into the same network (AKA Duplicated), imported into another Network, or restored as a standalone WordPress site using the importbuddy.php tool.&lt;br /&gt;
** Limitation: The main Network [sub]site cannot be exported as it is tied to the Network. It is still included in the main Network backup however.&lt;br /&gt;
&lt;br /&gt;
* '''Import an exported subsite into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Import a backed up standalone site into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Restore or Migrate an exported subsite as a standalone site'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
=Running Backup, Migrating OR Restoring with BackupBuddy Multisite BETA=&lt;br /&gt;
&lt;br /&gt;
Here is an actual video, from one of our many webinars (we have many regular webinars planned), with details on how to migrate or restore with BackupBuddy. Note: Some functionality has changed and improved since this video was made. It is not the latest version.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|WYhLIK3KfK4|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
=Frequently Asked Questions=&lt;br /&gt;
&lt;br /&gt;
====Are multiple Multisite databases supported?====&lt;br /&gt;
No. A couple of plugins, such as Multi-DB allow Multisite networks to run on multiple databases instead of the normal one.  We do not currently support this custom 3rd party configuration.&lt;br /&gt;
&lt;br /&gt;
====WordPress Multisite Domain Mapping and BackupBuddy Multisite====&lt;br /&gt;
&lt;br /&gt;
Domain mapping was confirmed by customers to work in pre-v3.0 BackupBuddy versions. It has not been officially tested with &amp;gt; 3.0 versions. Customer reports of success/failure are welcomed. Note: Some functionality has changed and improved since this video was made. It is not the latest version.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|oDM5v2Ymk1M|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
====Support Questions====&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Multisite support questions can be asked in the official [http://ithemes.com/forum/backupbuddy-ms/ BackupBuddy Multisite Forums]. &lt;br /&gt;
&lt;br /&gt;
non-Multisite related BackupBuddy support questions can be asked in the official [http://ithemes.com/forum/backupbuddy/ BackupBuddy Forums].&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Pre-Sales questions, for Multisite OR non-Multisite backups and restores/migrations, can be asked on the [http://ithemes.com/forum/pre-sales-and-other-inquiries/ Pre-Sales Forums], via the Live Chat (the Panda icon on top of [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite] page), or by emailing sales@ithemes.com&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
====Official Pages====&lt;br /&gt;
*[http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy]&lt;br /&gt;
*[http://ithemes.com/codex/page/BackupBuddy BackupBuddy Codex - Self-Hosted and Multisite combined]&lt;br /&gt;
====Blog Posts====&lt;br /&gt;
*[http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ 5 Reasons to Love BackupBuddy with Multisite Support - Blog Article]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy Multisite Migration - Expanded Features in Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-ms-released-as-a-beta/ BackupBuddy Multisite Released as Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/how-backupbuddy-changed-my-business-model/ How BackupBuddy changed one of our customer's entire business model!]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/IThemes_Codex</id>
		<title>IThemes Codex</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/IThemes_Codex"/>
				<updated>2012-09-17T20:55:12Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Welcome to the iThemes Codex. The purpose of this codex is to be a central repository for documentation and tutorials for our [http://ithemes.com/ themes (iThemes)] and [http://pluginbuddy.com plugins (formerly PluginBuddy)].&lt;br /&gt;
&lt;br /&gt;
The information on this codex is available to everyone and not just our customers. Our hope is that this information will benefit not just our community but the larger WordPress community as well.&lt;br /&gt;
&lt;br /&gt;
While read access is open to all, the ability to modify this site's content is restricted to our customers. Members with access to the [http://ithemes.com/forum/ iThemes Support Forum] will automatically have access here. Simply log into the forum first and then visit the Codex.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Internal Codex Pages ==&lt;br /&gt;
* [[BackupBuddy]]&lt;br /&gt;
** [[BackupBuddy Multisite]]&lt;br /&gt;
* [[Builder]]&lt;br /&gt;
* [[PluginBuddy|Plugins]]&lt;br /&gt;
* [[Themes]]&lt;br /&gt;
* [[Forum Related]]&lt;br /&gt;
* [[:Category:Advanced Topics|Advanced Topics]]&lt;br /&gt;
* [[General WordPress Related]]&lt;br /&gt;
&lt;br /&gt;
== External Web Links ==&lt;br /&gt;
* [http://ithemes.com/ iThemes.com]&lt;br /&gt;
* [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
* [http://webdesign.com/ WebDesign.com]&lt;br /&gt;
* [http://ithemes.com/forum Support Forum]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Theme Documentation ==&lt;br /&gt;
* [[Themes]] - an overview of all themes, and all theme related information&lt;br /&gt;
* [[ThemesFAQ|Frequently Asked Questions]] - not specifically theme related&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Resources ==&lt;br /&gt;
* [[Basics]] - List of resources for learning basics of HTML and CSS&lt;br /&gt;
* [[WordPress]] - todo&lt;br /&gt;
* [[CSS]] - List of resources for learning CSS online&lt;br /&gt;
* [[HTML]] - todo&lt;br /&gt;
* [[jQuery]] - List of resources for learning jQuery online&lt;br /&gt;
* [[PHP]] - List of resources for learning PHP online&lt;br /&gt;
&lt;br /&gt;
== Wiki Editing ==&lt;br /&gt;
* [http://www.mediawiki.org/wiki/Help:Formatting Wiki Formatting Help]&lt;br /&gt;
&lt;br /&gt;
== Support Policies ==&lt;br /&gt;
* [[Support Policies]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/IThemes_Codex</id>
		<title>IThemes Codex</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/IThemes_Codex"/>
				<updated>2012-09-17T20:53:09Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Welcome to the iThemes Codex. The purpose of this codex is to be a central repository for documentation and tutorials for our [http://ithemes.com/ themes (iThemes)], [http://pluginbuddy.com plugins (formerly PluginBuddy)], and [http://webdesign.com training (WebDesign.com)].&lt;br /&gt;
&lt;br /&gt;
The information on this codex is available to everyone and not just our customers. Our hope is that this information will benefit not just our community but the larger WordPress community as well.&lt;br /&gt;
&lt;br /&gt;
While read access is open to all, the ability to modify this site's content is restricted to our customers. Members with access to the [http://ithemes.com/forum/ iThemes Support Forum] will automatically have access here. Simply log into the forum first and then visit the Codex.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Internal Codex Pages ==&lt;br /&gt;
* [[Builder]]&lt;br /&gt;
* [[BackupBuddy]]&lt;br /&gt;
** [[BackupBuddy Multisite]]&lt;br /&gt;
* [[PluginBuddy|PluginBuddy Plugins]]&lt;br /&gt;
* [[Forum Related]]&lt;br /&gt;
* [[:Category:Advanced Topics|Advanced Topics]]&lt;br /&gt;
* [[General WordPress Related]]&lt;br /&gt;
&lt;br /&gt;
== External Web Links ==&lt;br /&gt;
* [http://ithemes.com/ iThemes.com]&lt;br /&gt;
* [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
* [http://webdesign.com/ WebDesign.com]&lt;br /&gt;
* [http://ithemes.com/forum Support Forum]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Theme Documentation ==&lt;br /&gt;
* [[Themes]] - an overview of all themes, and all theme related information&lt;br /&gt;
* [[ThemesFAQ|Frequently Asked Questions]] - not specifically theme related&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Resources ==&lt;br /&gt;
* [[Basics]] - List of resources for learning basics of HTML and CSS&lt;br /&gt;
* [[WordPress]] - todo&lt;br /&gt;
* [[CSS]] - List of resources for learning CSS online&lt;br /&gt;
* [[HTML]] - todo&lt;br /&gt;
* [[jQuery]] - List of resources for learning jQuery online&lt;br /&gt;
* [[PHP]] - List of resources for learning PHP online&lt;br /&gt;
&lt;br /&gt;
== Wiki Editing ==&lt;br /&gt;
* [http://www.mediawiki.org/wiki/Help:Formatting Wiki Formatting Help]&lt;br /&gt;
&lt;br /&gt;
== Support Policies ==&lt;br /&gt;
* [[Support Policies]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/MediaWiki:Sidebar</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/MediaWiki:Sidebar"/>
				<updated>2012-09-17T20:51:46Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* iThemes Codex&lt;br /&gt;
** IThemes Codex|Codex Home&lt;br /&gt;
** BackupBuddy|BackupBuddy&lt;br /&gt;
** Builder|Builder Theme&lt;br /&gt;
** PluginBuddy|Plugins&lt;br /&gt;
** Themes|Themes&lt;br /&gt;
** ThemesFAQ|Theme FAQ&lt;br /&gt;
&lt;br /&gt;
** Support Policies|Support Policies&lt;br /&gt;
&lt;br /&gt;
* Codex Navigation&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** helppage|help&lt;br /&gt;
&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* SEARCH&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/MediaWiki:Sidebar</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/MediaWiki:Sidebar"/>
				<updated>2012-09-17T20:51:10Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* iThemes Codex&lt;br /&gt;
** IThemes Codex|Home&lt;br /&gt;
** BackupBuddy|BackupBuddy Docs&lt;br /&gt;
** Builder|Builder Theme Docs&lt;br /&gt;
** PluginBuddy|Plugin Docs&lt;br /&gt;
** Themes|Theme Docs&lt;br /&gt;
** ThemesFAQ|Theme FAQ&lt;br /&gt;
&lt;br /&gt;
** Support Policies|Support Policies&lt;br /&gt;
&lt;br /&gt;
* Codex Navigation&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** helppage|help&lt;br /&gt;
&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* SEARCH&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/MediaWiki:Sidebar</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/MediaWiki:Sidebar"/>
				<updated>2012-09-17T20:50:40Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* iThemes Codex&lt;br /&gt;
** IThemes Codex|Home&lt;br /&gt;
** BackupBuddy|BackupBuddy Docs&lt;br /&gt;
** Builder|Builder Theme Docs&lt;br /&gt;
** Plugins|Plugin Docs&lt;br /&gt;
** Themes|Theme Docs&lt;br /&gt;
** ThemesFAQ|Theme FAQ&lt;br /&gt;
&lt;br /&gt;
** Support Policies|Support Policies&lt;br /&gt;
&lt;br /&gt;
* Codex Navigation&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** helppage|help&lt;br /&gt;
&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* SEARCH&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/MediaWiki:Sidebar</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/MediaWiki:Sidebar"/>
				<updated>2012-09-17T20:50:14Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* iThemes Codex&lt;br /&gt;
** IThemes Codex|Codex Home&lt;br /&gt;
** BackupBuddy|BackupBuddy Docs&lt;br /&gt;
** Builder|Builder Theme&lt;br /&gt;
** Plugins|Plugin Docs&lt;br /&gt;
** Themes|Theme Docs&lt;br /&gt;
** ThemesFAQ|Theme FAQ&lt;br /&gt;
&lt;br /&gt;
** Support Policies|Support Policies&lt;br /&gt;
&lt;br /&gt;
* Codex Navigation&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** helppage|help&lt;br /&gt;
&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* SEARCH&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/MediaWiki:Sidebar</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/MediaWiki:Sidebar"/>
				<updated>2012-09-17T20:49:28Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* iThemes Codex&lt;br /&gt;
** IThemes Codex|Codex Home&lt;br /&gt;
** BackupBuddy|BackupBuddy&lt;br /&gt;
** Builder|Builder Theme&lt;br /&gt;
** Themes|Theme Documentation&lt;br /&gt;
** ThemesFAQ|Theme FAQ&lt;br /&gt;
** Plugins|Plugin Documentation&lt;br /&gt;
** Support Policies|Support Policies&lt;br /&gt;
&lt;br /&gt;
* Codex Navigation&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** helppage|help&lt;br /&gt;
&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* SEARCH&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/MediaWiki:Sidebar</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/MediaWiki:Sidebar"/>
				<updated>2012-09-17T20:49:11Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* iThemes Codex&lt;br /&gt;
** IThemes Codex|Codex Home&lt;br /&gt;
** BackupBuddy|BackupBuddy&lt;br /&gt;
** Builder|Builder&lt;br /&gt;
** Themes|Theme Documentation&lt;br /&gt;
** ThemesFAQ|Theme FAQ&lt;br /&gt;
* Plugins|Plugin Documentation&lt;br /&gt;
** Support Policies|Support Policies&lt;br /&gt;
&lt;br /&gt;
* Codex Navigation&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** helppage|help&lt;br /&gt;
&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* SEARCH&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/MediaWiki:Sidebar</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/MediaWiki:Sidebar"/>
				<updated>2012-09-17T20:47:39Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* iThemes Codex&lt;br /&gt;
** IThemes Codex|Codex Home&lt;br /&gt;
** BackupBuddy|BackupBuddy&lt;br /&gt;
** Builder|Builder&lt;br /&gt;
** Support Policies|Support Policies&lt;br /&gt;
&lt;br /&gt;
* Themes|Themes&lt;br /&gt;
** ThemesFAQ|Theme FAQ&lt;br /&gt;
** Themes|Theme Documentation&lt;br /&gt;
** Builder|Builder theme&lt;br /&gt;
&lt;br /&gt;
* Plugins|PluginBuddy&lt;br /&gt;
&lt;br /&gt;
* Codex Navigation&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** helppage|help&lt;br /&gt;
** TOOLBOX&lt;br /&gt;
&lt;br /&gt;
* SEARCH&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/MediaWiki:Sidebar</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/MediaWiki:Sidebar"/>
				<updated>2012-09-17T20:46:46Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* iThemes Codex&lt;br /&gt;
** IThemes Codex|Codex Home&lt;br /&gt;
** BackupBuddy|BackupBuddy&lt;br /&gt;
** Builder|Builder&lt;br /&gt;
** Support Policies|Support Policies&lt;br /&gt;
&lt;br /&gt;
* Themes|Themes&lt;br /&gt;
** ThemesFAQ|Theme FAQ&lt;br /&gt;
** Themes|Theme Documentation&lt;br /&gt;
** Builder|Builder theme&lt;br /&gt;
&lt;br /&gt;
* Plugins|PluginBuddy&lt;br /&gt;
&lt;br /&gt;
* Codex Navigation&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** helppage|help&lt;br /&gt;
* SEARCH&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/MediaWiki:Sidebar</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/MediaWiki:Sidebar"/>
				<updated>2012-09-17T20:44:09Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* iThemes Codex&lt;br /&gt;
** IThemes Codex|Codex Home&lt;br /&gt;
** BackupBuddy|BackupBuddy&lt;br /&gt;
** Builder|Builder&lt;br /&gt;
** Support Policies|Support Policies&lt;br /&gt;
&lt;br /&gt;
* Themes Navigation&lt;br /&gt;
** ThemesFAQ|Frequently Asked Questions&lt;br /&gt;
** Themes|Theme Documentation&lt;br /&gt;
** Builder|Builder theme&lt;br /&gt;
&lt;br /&gt;
* PluginBuddy Navigation&lt;br /&gt;
** PluginBuddy|Pluginbuddy&lt;br /&gt;
** BackupBuddy|BackupBuddy&lt;br /&gt;
&lt;br /&gt;
* Codex Navigation&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** helppage|help&lt;br /&gt;
* SEARCH&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/MediaWiki:Sidebar</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/MediaWiki:Sidebar"/>
				<updated>2012-09-17T20:41:29Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* iThemes Codex&lt;br /&gt;
** BackupBuddy|BackupBuddy&lt;br /&gt;
** Builder|Builder&lt;br /&gt;
** IThemes Codex|Codex Homepage&lt;br /&gt;
** Support Policies|Support Policies&lt;br /&gt;
&lt;br /&gt;
* Themes Navigation&lt;br /&gt;
** ThemesFAQ|Frequently Asked Questions&lt;br /&gt;
** Themes|Theme Documentation&lt;br /&gt;
** Builder|Builder theme&lt;br /&gt;
&lt;br /&gt;
* PluginBuddy Navigation&lt;br /&gt;
** PluginBuddy|Pluginbuddy&lt;br /&gt;
** BackupBuddy|BackupBuddy&lt;br /&gt;
&lt;br /&gt;
* Codex Navigation&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** helppage|help&lt;br /&gt;
* SEARCH&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/MediaWiki:Sidebar</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/MediaWiki:Sidebar"/>
				<updated>2012-09-17T20:41:11Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* iThemes Codex&lt;br /&gt;
** BackupBuddy&lt;br /&gt;
** Builder&lt;br /&gt;
** IThemes Codex|Codex Homepage&lt;br /&gt;
** Support Policies|Support Policies&lt;br /&gt;
&lt;br /&gt;
* Themes Navigation&lt;br /&gt;
** ThemesFAQ|Frequently Asked Questions&lt;br /&gt;
** Themes|Theme Documentation&lt;br /&gt;
** Builder|Builder theme&lt;br /&gt;
&lt;br /&gt;
* PluginBuddy Navigation&lt;br /&gt;
** PluginBuddy|Pluginbuddy&lt;br /&gt;
** BackupBuddy|BackupBuddy&lt;br /&gt;
&lt;br /&gt;
* Codex Navigation&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** helppage|help&lt;br /&gt;
* SEARCH&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/MediaWiki:Sidebar</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/MediaWiki:Sidebar"/>
				<updated>2012-09-17T20:40:57Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* iThemes Codex&lt;br /&gt;
** BackupBuddy&lt;br /&gt;
** Builder&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
** IThemes Codex|Codex Homepage&lt;br /&gt;
** Support Policies|Support Policies&lt;br /&gt;
&lt;br /&gt;
* Themes Navigation&lt;br /&gt;
** ThemesFAQ|Frequently Asked Questions&lt;br /&gt;
** Themes|Theme Documentation&lt;br /&gt;
** Builder|Builder theme&lt;br /&gt;
&lt;br /&gt;
* PluginBuddy Navigation&lt;br /&gt;
** PluginBuddy|Pluginbuddy&lt;br /&gt;
** BackupBuddy|BackupBuddy&lt;br /&gt;
&lt;br /&gt;
* Codex Navigation&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** helppage|help&lt;br /&gt;
* SEARCH&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/MediaWiki:Sidebar</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/MediaWiki:Sidebar"/>
				<updated>2012-09-17T20:40:42Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* iThemes Codex&lt;br /&gt;
* BackupBuddy&lt;br /&gt;
* Builder&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
** IThemes Codex|Codex Homepage&lt;br /&gt;
** Support Policies|Support Policies&lt;br /&gt;
&lt;br /&gt;
* Themes Navigation&lt;br /&gt;
** ThemesFAQ|Frequently Asked Questions&lt;br /&gt;
** Themes|Theme Documentation&lt;br /&gt;
** Builder|Builder theme&lt;br /&gt;
&lt;br /&gt;
* PluginBuddy Navigation&lt;br /&gt;
** PluginBuddy|Pluginbuddy&lt;br /&gt;
** BackupBuddy|BackupBuddy&lt;br /&gt;
&lt;br /&gt;
* Codex Navigation&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** helppage|help&lt;br /&gt;
* SEARCH&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/MediaWiki:Sidebar</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/MediaWiki:Sidebar"/>
				<updated>2012-09-17T20:40:30Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* iThemes Codex&lt;br /&gt;
* [[BackupBuddy]]&lt;br /&gt;
* [Builder]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
** IThemes Codex|Codex Homepage&lt;br /&gt;
** Support Policies|Support Policies&lt;br /&gt;
&lt;br /&gt;
* Themes Navigation&lt;br /&gt;
** ThemesFAQ|Frequently Asked Questions&lt;br /&gt;
** Themes|Theme Documentation&lt;br /&gt;
** Builder|Builder theme&lt;br /&gt;
&lt;br /&gt;
* PluginBuddy Navigation&lt;br /&gt;
** PluginBuddy|Pluginbuddy&lt;br /&gt;
** BackupBuddy|BackupBuddy&lt;br /&gt;
&lt;br /&gt;
* Codex Navigation&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** helppage|help&lt;br /&gt;
* SEARCH&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/MediaWiki:Sidebar</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/MediaWiki:Sidebar"/>
				<updated>2012-09-17T20:40:22Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* iThemes Codex&lt;br /&gt;
* [[BackupBudd]y]&lt;br /&gt;
* [Builder]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
** IThemes Codex|Codex Homepage&lt;br /&gt;
** Support Policies|Support Policies&lt;br /&gt;
&lt;br /&gt;
* Themes Navigation&lt;br /&gt;
** ThemesFAQ|Frequently Asked Questions&lt;br /&gt;
** Themes|Theme Documentation&lt;br /&gt;
** Builder|Builder theme&lt;br /&gt;
&lt;br /&gt;
* PluginBuddy Navigation&lt;br /&gt;
** PluginBuddy|Pluginbuddy&lt;br /&gt;
** BackupBuddy|BackupBuddy&lt;br /&gt;
&lt;br /&gt;
* Codex Navigation&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** helppage|help&lt;br /&gt;
* SEARCH&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/MediaWiki:Sidebar</id>
		<title>MediaWiki:Sidebar</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/MediaWiki:Sidebar"/>
				<updated>2012-09-17T20:40:04Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* iThemes Codex&lt;br /&gt;
* [BackupBuddy]&lt;br /&gt;
* [Builder]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
** IThemes Codex|Codex Homepage&lt;br /&gt;
** Support Policies|Support Policies&lt;br /&gt;
&lt;br /&gt;
* Themes Navigation&lt;br /&gt;
** ThemesFAQ|Frequently Asked Questions&lt;br /&gt;
** Themes|Theme Documentation&lt;br /&gt;
** Builder|Builder theme&lt;br /&gt;
&lt;br /&gt;
* PluginBuddy Navigation&lt;br /&gt;
** PluginBuddy|Pluginbuddy&lt;br /&gt;
** BackupBuddy|BackupBuddy&lt;br /&gt;
&lt;br /&gt;
* Codex Navigation&lt;br /&gt;
** recentchanges-url|recentchanges&lt;br /&gt;
** randompage-url|randompage&lt;br /&gt;
** helppage|help&lt;br /&gt;
* SEARCH&lt;br /&gt;
* TOOLBOX&lt;br /&gt;
* LANGUAGES&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy:_Hosts</id>
		<title>BackupBuddy: Hosts</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy:_Hosts"/>
				<updated>2012-08-24T07:14:44Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: /* WPEngine */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The information contained here is for shared hosting accounts unless specified otherwise. Some hosts include a letter grade next to them as a quick reference score of how well they perform.&lt;br /&gt;
&lt;br /&gt;
==[http://1and1.com 1and1]==&lt;br /&gt;
* Servers sometimes overloaded causing browsing sites hosted on them to take a very long time to load or time out.&lt;br /&gt;
&lt;br /&gt;
==[http://aplus.net aPlus.net]==&lt;br /&gt;
'''Issues'''&lt;br /&gt;
* Problems reported with sites above 450mb (with zip compression on; off increases limit).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==[http://bluehost.com BlueHost]==&lt;br /&gt;
&lt;br /&gt;
Overall BlueHost hosting seems to be somewhat hit or miss.  Many customers have found that BlueHost is slow and often returns 404 and 500 server error messages for no reason periodically.  These can not only cause a bad experience for viewers of your site but also break BackupBuddy backup functionality.  Though in general BackupBuddy should work the lack of consistency among the experiences of users of this host results in us not being able to recommend this host.&lt;br /&gt;
&lt;br /&gt;
PHP memory limit is 128MB at MOST.  This is low.  Hostgator for example provides 256MB which is double.&lt;br /&gt;
&lt;br /&gt;
*One customer had an Addhandler line in .htaccess which gave issues when migrated to another host.&lt;br /&gt;
&lt;br /&gt;
Bluehost requires a database name (and user) to have a prefix of your username, so to be of the form username_databasename.&lt;br /&gt;
&lt;br /&gt;
===Timeouts===&lt;br /&gt;
On the boards, a few people have complained about BackupBuddy timing out during backup. To resolve this, support recommends editing your php.ini file to change max execution time to 600.&lt;br /&gt;
&lt;br /&gt;
According to response from tech support these are the limits on how long a process can run before being killed off and are based on whether the customer has a dedicated IP address or uses the shared address.&lt;br /&gt;
&lt;br /&gt;
*Apache/Web (HTML/PHP/Downloads): With Dedicated IP: 12 Hours  |  Without: 10 Minutes (up from 5 minutes)&lt;br /&gt;
*SSH/Shell: With Dedicated IP: 2 Hours  |  Without: 1 Hour&lt;br /&gt;
*Cron Jobs: With Dedicated IP: 30 Minutes  |  Without: 30 Minutes&lt;br /&gt;
*Deamons: With Dedicated IP: Unlimited  |  Without: 10 Minutes&lt;br /&gt;
&lt;br /&gt;
==[http://www.bluerazor.com BlueRazor]==&lt;br /&gt;
No cPanel&lt;br /&gt;
&lt;br /&gt;
==[http://dreamhost.com Dreamhost] - D (maybe F)==&lt;br /&gt;
&lt;br /&gt;
Note: As of August 2012 we are working with Dreamhost to clarify or resolve issues noted below. We will update this as this progresses. Thank you Dreamhost for so kindly working with us!&lt;br /&gt;
&lt;br /&gt;
'''Issues'''&lt;br /&gt;
* Does not allow HTTP Loopbacks (PHP connects back to site via curl to Site URL - ie http://yoursite.com ).&lt;br /&gt;
* Unlimited plans terms of service PROHIBITS storing of backups in your account.  &amp;quot;Unlimited&amp;quot; is not truly unlimited.&lt;br /&gt;
* Resource related:&lt;br /&gt;
** Extremely slow zip generation.&lt;br /&gt;
** Problems reported with sites above 22mb (with zip compression on; off increases limit) due to slow processing.&lt;br /&gt;
** Possible workaround: Can create a custom php.ini to extend PHP timeout to increase BackupBuddy run-time.&lt;br /&gt;
* No cPanel (uses custom system) - See Resources below for manual unzip functionality.&lt;br /&gt;
* Configuration related:&lt;br /&gt;
** No native command-line zip. BackupBuddy will enter the slower, less reliable compatibility mode.&lt;br /&gt;
** Procwatch automatically kills off BackupBuddy if it uses too many resources in the process of making a backup.&lt;br /&gt;
'''Notes'''&lt;br /&gt;
* Verify your mysql server as it may not be the common default localhost (for ImportBuddy migrations).&lt;br /&gt;
'''Resources'''&lt;br /&gt;
* File Manager (allows for manual unzipping): https://webftp.dreamhost.com/&lt;br /&gt;
&lt;br /&gt;
==[http://godaddy.com GoDaddy] - F==&lt;br /&gt;
&lt;br /&gt;
Note: Godaddy is currently working with us to try and improve known issues.  We will update this pending improvements.&lt;br /&gt;
&lt;br /&gt;
'''Issues'''&lt;br /&gt;
* Custom control panel. Some changes take up to hours to take effect.&lt;br /&gt;
* Slow site load times on some servers.&lt;br /&gt;
* Some servers overloaded not leaving processing power for backups.&lt;br /&gt;
* System actively kills any PHP process working too hard or too long (ie backups).&lt;br /&gt;
&lt;br /&gt;
==[http://secure.hostgator.com/cgi-bin/affiliates/clickthru.cgi?id=ithemes HostGator] A==&lt;br /&gt;
'''Benefits'''&lt;br /&gt;
* Fast. Command-line zip available for best BackupBuddy experience.&lt;br /&gt;
* CPanel.&lt;br /&gt;
'''Issues'''&lt;br /&gt;
* Recently changed PHP runtime limit cap to 30 seconds for shared hosting.&lt;br /&gt;
** Possible work-around: http://ithemes.com/forum/index.php?/topic/5519-hostgator-timeout-fix-available/&lt;br /&gt;
** Only causes issues with large sites ( ~1GB or more )&lt;br /&gt;
&lt;br /&gt;
'''Info'''&lt;br /&gt;
* Current limits of their shared and reseller hosting (9/20/2011)&lt;br /&gt;
** safe mode = Off (cannot adjust) &lt;br /&gt;
** memory_limit = 64M (MAXIMUM) &lt;br /&gt;
** max_execution_time = 30 (MAXIMUM) &lt;br /&gt;
** max_input_time = 60 (MAXIMUM) &lt;br /&gt;
** post_max_size = 64M (MAXIMUM) &lt;br /&gt;
** upload_max_filesize = 64M (MAXIMUM) &lt;br /&gt;
** enable_dl = Off (cannot adjust)&lt;br /&gt;
&lt;br /&gt;
==[http://inmotionhosting InMotionHosting]==&lt;br /&gt;
* Slow page loads.&lt;br /&gt;
* Problems reported with sites above 85mb (with zip compression on; off increases limit).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==[http://ipower.com iPower]==&lt;br /&gt;
Minimal issues.&lt;br /&gt;
&lt;br /&gt;
Told a customer that they don't support linux command line zip.&lt;br /&gt;
&lt;br /&gt;
==[http://ipowerweb.com ipowerweb]==&lt;br /&gt;
Minimal issues.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==[http://www.rackspace.com/cloud/ Rackspace Cloud Hosting]==&lt;br /&gt;
* Some reports of failing path/directory detection due to symlink issues, preventing backups.&lt;br /&gt;
* We have not had success or failure reports for Cloudsites hosting in a long period so we cannot accurately report the status.&lt;br /&gt;
&lt;br /&gt;
==[http://justhost.com JustHost]==&lt;br /&gt;
* JustHost blocks the command line ZIP command which is required for BackupBuddy's normal functionality.&lt;br /&gt;
* Compatibility mode is available but is only recommended for moving away from JustHost hosting.&lt;br /&gt;
&lt;br /&gt;
==[http://wpengine.com/b/ WPEngine]==&lt;br /&gt;
* We do NOT reccomend WPEngine for BackupBuddy compatibility.&lt;br /&gt;
** Command line zip via PHP exec() is blocked. You MUST enable &amp;quot;Alternate zip method&amp;quot; under troubleshooting for best functionality. WPEngine does NOT meet BackupBuddy requirements due to this.&lt;br /&gt;
*** Note: Backups will be severely limited due to this restriction.&lt;br /&gt;
** Blocks downloading of backup files via web for enhanced security purposes.&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy:_Hosts</id>
		<title>BackupBuddy: Hosts</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy:_Hosts"/>
				<updated>2012-08-24T07:12:42Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: /* Rackspace Cloud Hosting */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The information contained here is for shared hosting accounts unless specified otherwise. Some hosts include a letter grade next to them as a quick reference score of how well they perform.&lt;br /&gt;
&lt;br /&gt;
==[http://1and1.com 1and1]==&lt;br /&gt;
* Servers sometimes overloaded causing browsing sites hosted on them to take a very long time to load or time out.&lt;br /&gt;
&lt;br /&gt;
==[http://aplus.net aPlus.net]==&lt;br /&gt;
'''Issues'''&lt;br /&gt;
* Problems reported with sites above 450mb (with zip compression on; off increases limit).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==[http://bluehost.com BlueHost]==&lt;br /&gt;
&lt;br /&gt;
Overall BlueHost hosting seems to be somewhat hit or miss.  Many customers have found that BlueHost is slow and often returns 404 and 500 server error messages for no reason periodically.  These can not only cause a bad experience for viewers of your site but also break BackupBuddy backup functionality.  Though in general BackupBuddy should work the lack of consistency among the experiences of users of this host results in us not being able to recommend this host.&lt;br /&gt;
&lt;br /&gt;
PHP memory limit is 128MB at MOST.  This is low.  Hostgator for example provides 256MB which is double.&lt;br /&gt;
&lt;br /&gt;
*One customer had an Addhandler line in .htaccess which gave issues when migrated to another host.&lt;br /&gt;
&lt;br /&gt;
Bluehost requires a database name (and user) to have a prefix of your username, so to be of the form username_databasename.&lt;br /&gt;
&lt;br /&gt;
===Timeouts===&lt;br /&gt;
On the boards, a few people have complained about BackupBuddy timing out during backup. To resolve this, support recommends editing your php.ini file to change max execution time to 600.&lt;br /&gt;
&lt;br /&gt;
According to response from tech support these are the limits on how long a process can run before being killed off and are based on whether the customer has a dedicated IP address or uses the shared address.&lt;br /&gt;
&lt;br /&gt;
*Apache/Web (HTML/PHP/Downloads): With Dedicated IP: 12 Hours  |  Without: 10 Minutes (up from 5 minutes)&lt;br /&gt;
*SSH/Shell: With Dedicated IP: 2 Hours  |  Without: 1 Hour&lt;br /&gt;
*Cron Jobs: With Dedicated IP: 30 Minutes  |  Without: 30 Minutes&lt;br /&gt;
*Deamons: With Dedicated IP: Unlimited  |  Without: 10 Minutes&lt;br /&gt;
&lt;br /&gt;
==[http://www.bluerazor.com BlueRazor]==&lt;br /&gt;
No cPanel&lt;br /&gt;
&lt;br /&gt;
==[http://dreamhost.com Dreamhost] - D (maybe F)==&lt;br /&gt;
&lt;br /&gt;
Note: As of August 2012 we are working with Dreamhost to clarify or resolve issues noted below. We will update this as this progresses. Thank you Dreamhost for so kindly working with us!&lt;br /&gt;
&lt;br /&gt;
'''Issues'''&lt;br /&gt;
* Does not allow HTTP Loopbacks (PHP connects back to site via curl to Site URL - ie http://yoursite.com ).&lt;br /&gt;
* Unlimited plans terms of service PROHIBITS storing of backups in your account.  &amp;quot;Unlimited&amp;quot; is not truly unlimited.&lt;br /&gt;
* Resource related:&lt;br /&gt;
** Extremely slow zip generation.&lt;br /&gt;
** Problems reported with sites above 22mb (with zip compression on; off increases limit) due to slow processing.&lt;br /&gt;
** Possible workaround: Can create a custom php.ini to extend PHP timeout to increase BackupBuddy run-time.&lt;br /&gt;
* No cPanel (uses custom system) - See Resources below for manual unzip functionality.&lt;br /&gt;
* Configuration related:&lt;br /&gt;
** No native command-line zip. BackupBuddy will enter the slower, less reliable compatibility mode.&lt;br /&gt;
** Procwatch automatically kills off BackupBuddy if it uses too many resources in the process of making a backup.&lt;br /&gt;
'''Notes'''&lt;br /&gt;
* Verify your mysql server as it may not be the common default localhost (for ImportBuddy migrations).&lt;br /&gt;
'''Resources'''&lt;br /&gt;
* File Manager (allows for manual unzipping): https://webftp.dreamhost.com/&lt;br /&gt;
&lt;br /&gt;
==[http://godaddy.com GoDaddy] - F==&lt;br /&gt;
&lt;br /&gt;
Note: Godaddy is currently working with us to try and improve known issues.  We will update this pending improvements.&lt;br /&gt;
&lt;br /&gt;
'''Issues'''&lt;br /&gt;
* Custom control panel. Some changes take up to hours to take effect.&lt;br /&gt;
* Slow site load times on some servers.&lt;br /&gt;
* Some servers overloaded not leaving processing power for backups.&lt;br /&gt;
* System actively kills any PHP process working too hard or too long (ie backups).&lt;br /&gt;
&lt;br /&gt;
==[http://secure.hostgator.com/cgi-bin/affiliates/clickthru.cgi?id=ithemes HostGator] A==&lt;br /&gt;
'''Benefits'''&lt;br /&gt;
* Fast. Command-line zip available for best BackupBuddy experience.&lt;br /&gt;
* CPanel.&lt;br /&gt;
'''Issues'''&lt;br /&gt;
* Recently changed PHP runtime limit cap to 30 seconds for shared hosting.&lt;br /&gt;
** Possible work-around: http://ithemes.com/forum/index.php?/topic/5519-hostgator-timeout-fix-available/&lt;br /&gt;
** Only causes issues with large sites ( ~1GB or more )&lt;br /&gt;
&lt;br /&gt;
'''Info'''&lt;br /&gt;
* Current limits of their shared and reseller hosting (9/20/2011)&lt;br /&gt;
** safe mode = Off (cannot adjust) &lt;br /&gt;
** memory_limit = 64M (MAXIMUM) &lt;br /&gt;
** max_execution_time = 30 (MAXIMUM) &lt;br /&gt;
** max_input_time = 60 (MAXIMUM) &lt;br /&gt;
** post_max_size = 64M (MAXIMUM) &lt;br /&gt;
** upload_max_filesize = 64M (MAXIMUM) &lt;br /&gt;
** enable_dl = Off (cannot adjust)&lt;br /&gt;
&lt;br /&gt;
==[http://inmotionhosting InMotionHosting]==&lt;br /&gt;
* Slow page loads.&lt;br /&gt;
* Problems reported with sites above 85mb (with zip compression on; off increases limit).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==[http://ipower.com iPower]==&lt;br /&gt;
Minimal issues.&lt;br /&gt;
&lt;br /&gt;
Told a customer that they don't support linux command line zip.&lt;br /&gt;
&lt;br /&gt;
==[http://ipowerweb.com ipowerweb]==&lt;br /&gt;
Minimal issues.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==[http://www.rackspace.com/cloud/ Rackspace Cloud Hosting]==&lt;br /&gt;
* Some reports of failing path/directory detection due to symlink issues, preventing backups.&lt;br /&gt;
* We have not had success or failure reports for Cloudsites hosting in a long period so we cannot accurately report the status.&lt;br /&gt;
&lt;br /&gt;
==[http://justhost.com JustHost]==&lt;br /&gt;
* JustHost blocks the command line ZIP command which is required for BackupBuddy's normal functionality.&lt;br /&gt;
* Compatibility mode is available but is only recommended for moving away from JustHost hosting.&lt;br /&gt;
&lt;br /&gt;
==[http://wpengine.com/b/ WPEngine]==&lt;br /&gt;
* Doesn't allow/support command line ZIP via PHP's exec() function.&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy</id>
		<title>BackupBuddy</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy"/>
				<updated>2012-08-20T21:36:39Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: /* Minimum Server Requirements (reduced functionality) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* '''New to BackupBuddy?''' Check out the [[BackupBuddy:_Getting_Started|Getting Started]] page.&lt;br /&gt;
* '''Problems?''' Check out the [[BackupBuddy:_Frequent_Support_Issues|Frequently Seen Support Issues]] page.&lt;br /&gt;
* '''Need hosting?''' ''Hostgator Coupons'' are available to BackupBuddy customers [http://ithemes.com/forum/index.php?/topic/14012-hostgator-coupons-for-our-community/ here].&lt;br /&gt;
* '''[http://ithemes.com/codex/page/BackupBuddy_Multisite BackupBuddy Multisite Codex]'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Multisite=&lt;br /&gt;
&lt;br /&gt;
As of version 2.2.14, BackupBuddy and Importbuddy include full BETA support for Multisite backups, imports and restorations.&lt;br /&gt;
&lt;br /&gt;
[http://ithemes.com/codex/page/BackupBuddy_Multisite Check out the BackupBuddy Multisite Codex] and [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite Beta Today!]&lt;br /&gt;
&lt;br /&gt;
BETA indicates that Multisite functionality has known issues and is not reccomended for production use except at your own risk.  We do NOT guarantee its functionality or provide guaranteed support for beta products.&lt;br /&gt;
&lt;br /&gt;
=Tutorials=&lt;br /&gt;
&lt;br /&gt;
===Installing BackupBuddy===&lt;br /&gt;
&lt;br /&gt;
Check out the [[Installing BackupBuddy]] section to see how BackupBuddy can be uploaded and activated on Single sites or Multisite networks or Multisite sites.&lt;br /&gt;
&lt;br /&gt;
===Getting Started===&lt;br /&gt;
Check out the [[BackupBuddy:_Getting_Started|Getting Started]] page to backup your Single sites or Multisite networks.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Restore or Migrate===&lt;br /&gt;
Learn to [[BackupBuddy:_ImportBuddy|Restore or Migrate]] your Single sites or Multisite networks with the latest importbuddy.php.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Settings Explained===&lt;br /&gt;
Get in depth information about the various [[BackupBuddy:_Settings|Settings]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Developing Locally===&lt;br /&gt;
Set up your computer to [[BackupBuddy:_Local_Development|Develop Sites Locally]] and then migrate them to your live site.&lt;br /&gt;
&lt;br /&gt;
=Specifications=&lt;br /&gt;
Server configuration is a very complex topic and varies wildly between hosts, server operating systems, and even the personal preference of the server administrator. Below are the bare minimum requirements for the plugin along with the recommended setup to get the most out of this plugin. You may use [[ServerBuddy]] to help you determine how your server compares to our minimum requirements &amp;amp; recommendations.&lt;br /&gt;
&lt;br /&gt;
===Server Recommendations (full functionality)===&lt;br /&gt;
* PHP 5.2+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2 currently requires PHP 5.2+]&lt;br /&gt;
* mySQL 5.x+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2 currently requires mySQL 5.0.15+]&lt;br /&gt;
* WordPress 3.1+ &lt;br /&gt;
* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.&lt;br /&gt;
** Backups will be stored in /wp-content/uploads/backupbuddy_backups/&lt;br /&gt;
** Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)&lt;br /&gt;
* Free disk space equal to or greater than the entire size of your site once compressed.&lt;br /&gt;
** SuPHP or environment so that file operations/zip run as user to prevent permissions issues.&lt;br /&gt;
** PHP exec() function enabled&lt;br /&gt;
** PHP ZipArchive class installed&lt;br /&gt;
* Linux:&lt;br /&gt;
** Command-line zip installed and accessible via exec().&lt;br /&gt;
* Windows (only supported for local development via Apache; IIS is not officially supported):&lt;br /&gt;
** Windows zip executable (available [http://pluginbuddy.com/wp-content/uploads/2010/05/backupbuddy_windows_unzip.zip here])&lt;br /&gt;
*** You must have the ability to configure your server to allow execution of this zip.exe file for it to function.&lt;br /&gt;
*** File permissions must also be set to allow access and execution of the zip executable.&lt;br /&gt;
* wp-config.php file must be in WordPress installation directory OR (starting with v3.0) in the parent directory.&lt;br /&gt;
&lt;br /&gt;
===Minimum Server Requirements (reduced functionality)===&lt;br /&gt;
'' NOTE: Some features of BackupBuddy will be unavailable or limited if running on minimum requirements without recommendations. Large sites may not be able to be backed up with these minimum features.'''&lt;br /&gt;
* PHP 5.2+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2 will require PHP 5.2+]&lt;br /&gt;
* mySQL 4.x+&lt;br /&gt;
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2 will require mySQL 5.0.15+]&lt;br /&gt;
* WordPress 3.0+&lt;br /&gt;
** We are trying to maintain bare minimum backup functionality for legacy versions as far back as WordPress v2.6 (though it's not pretty nor guaranteed to work perfectly at this time; we recommend only performing backups &amp;amp; direct restores for older versions and use it for safety while upgrading to the latest WordPress).&lt;br /&gt;
* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.&lt;br /&gt;
* BackupBuddy requires the uploads directory to be in the standard WordPress location.&lt;br /&gt;
** Backups will be stored in /wp-content/uploads/backupbuddy_backups/&lt;br /&gt;
** Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)&lt;br /&gt;
* Free disk space equal to or greater than the entire size of your site once compressed.&lt;br /&gt;
* wp-config.php file must be in WordPress installation directory OR (starting with v3.0) in the parent directory.&lt;br /&gt;
&lt;br /&gt;
===Host Compatibility===&lt;br /&gt;
Compare various [[BackupBuddy:_Hosts|Hosts &amp;amp; Hosting Environments]] to see how your host/potential host compares.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Misc. Information===&lt;br /&gt;
Find out some [[BackupBuddy:_Misc_Information|Miscellaneous Information]] about BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
	&lt;br /&gt;
=Troubleshooting=&lt;br /&gt;
&lt;br /&gt;
===Frequently Seen Support Issues===&lt;br /&gt;
''Problems?'' Start with the [[BackupBuddy:_Frequent_Support_Issues|Frequently Seen Support Issues]] to most quickly troubleshoot your problem.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===BackupBuddy: Error Codes===&lt;br /&gt;
Receive an error code? Check out the [[BackupBuddy:_Error_Codes|Error Codes]] page for explanations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Manual Migration===&lt;br /&gt;
Import fails on file extraction? Learn how to perform a [[BackupBuddy:_Manual_Migration|Manual Migration]] ... it's easier than you'd think!&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
&lt;br /&gt;
'''Tools'''&lt;br /&gt;
&lt;br /&gt;
* [http://ithemes.com/codex/page/File:Zip_test.zip Manually test command line zip functionality]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Links'''&lt;br /&gt;
# [http://pluginbuddy.com/purchase/backupbuddy/ Purchase BackupBuddy]&lt;br /&gt;
# [http://ithemes.com/codex/page/BackupBuddy_Multisite BackupBuddy Multisite Codex]&lt;br /&gt;
# [http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy beta Multisite support announcement]&lt;br /&gt;
# [http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ BackupBuddy beta Multisite key points everyone is raving about!] &lt;br /&gt;
# [http://pluginbuddy.com/tutorials/ PluginBuddy Tutorials]&lt;br /&gt;
# [http://pluginbuddy.com/ PluginBuddy.com]&lt;br /&gt;
# [http://pluginbuddy.com/support/ Support Forums]&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy:_Hosts</id>
		<title>BackupBuddy: Hosts</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy:_Hosts"/>
				<updated>2012-08-15T07:59:33Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: /* GoDaddy - F */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The information contained here is for shared hosting accounts unless specified otherwise. Some hosts include a letter grade next to them as a quick reference score of how well they perform.&lt;br /&gt;
&lt;br /&gt;
==[http://1and1.com 1and1]==&lt;br /&gt;
* Servers sometimes overloaded causing browsing sites hosted on them to take a very long time to load or time out.&lt;br /&gt;
&lt;br /&gt;
==[http://aplus.net aPlus.net]==&lt;br /&gt;
'''Issues'''&lt;br /&gt;
* Problems reported with sites above 450mb (with zip compression on; off increases limit).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==[http://bluehost.com BlueHost]==&lt;br /&gt;
&lt;br /&gt;
Overall BlueHost hosting seems to be somewhat hit or miss.  Many customers have found that BlueHost is slow and often returns 404 and 500 server error messages for no reason periodically.  These can not only cause a bad experience for viewers of your site but also break BackupBuddy backup functionality.  Though in general BackupBuddy should work the lack of consistency among the experiences of users of this host results in us not being able to recommend this host.&lt;br /&gt;
&lt;br /&gt;
PHP memory limit is 128MB at MOST.  This is low.  Hostgator for example provides 256MB which is double.&lt;br /&gt;
&lt;br /&gt;
*One customer had an Addhandler line in .htaccess which gave issues when migrated to another host.&lt;br /&gt;
&lt;br /&gt;
Bluehost requires a database name (and user) to have a prefix of your username, so to be of the form username_databasename.&lt;br /&gt;
&lt;br /&gt;
===Timeouts===&lt;br /&gt;
On the boards, a few people have complained about BackupBuddy timing out during backup. To resolve this, support recommends editing your php.ini file to change max execution time to 600.&lt;br /&gt;
&lt;br /&gt;
According to response from tech support these are the limits on how long a process can run before being killed off and are based on whether the customer has a dedicated IP address or uses the shared address.&lt;br /&gt;
&lt;br /&gt;
*Apache/Web (HTML/PHP/Downloads): With Dedicated IP: 12 Hours  |  Without: 10 Minutes (up from 5 minutes)&lt;br /&gt;
*SSH/Shell: With Dedicated IP: 2 Hours  |  Without: 1 Hour&lt;br /&gt;
*Cron Jobs: With Dedicated IP: 30 Minutes  |  Without: 30 Minutes&lt;br /&gt;
*Deamons: With Dedicated IP: Unlimited  |  Without: 10 Minutes&lt;br /&gt;
&lt;br /&gt;
==[http://www.bluerazor.com BlueRazor]==&lt;br /&gt;
No cPanel&lt;br /&gt;
&lt;br /&gt;
==[http://dreamhost.com Dreamhost] - D (maybe F)==&lt;br /&gt;
&lt;br /&gt;
Note: As of August 2012 we are working with Dreamhost to clarify or resolve issues noted below. We will update this as this progresses. Thank you Dreamhost for so kindly working with us!&lt;br /&gt;
&lt;br /&gt;
'''Issues'''&lt;br /&gt;
* Does not allow HTTP Loopbacks (PHP connects back to site via curl to Site URL - ie http://yoursite.com ).&lt;br /&gt;
* Unlimited plans terms of service PROHIBITS storing of backups in your account.  &amp;quot;Unlimited&amp;quot; is not truly unlimited.&lt;br /&gt;
* Resource related:&lt;br /&gt;
** Extremely slow zip generation.&lt;br /&gt;
** Problems reported with sites above 22mb (with zip compression on; off increases limit) due to slow processing.&lt;br /&gt;
** Possible workaround: Can create a custom php.ini to extend PHP timeout to increase BackupBuddy run-time.&lt;br /&gt;
* No cPanel (uses custom system) - See Resources below for manual unzip functionality.&lt;br /&gt;
* Configuration related:&lt;br /&gt;
** No native command-line zip. BackupBuddy will enter the slower, less reliable compatibility mode.&lt;br /&gt;
** Procwatch automatically kills off BackupBuddy if it uses too many resources in the process of making a backup.&lt;br /&gt;
'''Notes'''&lt;br /&gt;
* Verify your mysql server as it may not be the common default localhost (for ImportBuddy migrations).&lt;br /&gt;
'''Resources'''&lt;br /&gt;
* File Manager (allows for manual unzipping): https://webftp.dreamhost.com/&lt;br /&gt;
&lt;br /&gt;
==[http://godaddy.com GoDaddy] - F==&lt;br /&gt;
&lt;br /&gt;
Note: Godaddy is currently working with us to try and improve known issues.  We will update this pending improvements.&lt;br /&gt;
&lt;br /&gt;
'''Issues'''&lt;br /&gt;
* Custom control panel. Some changes take up to hours to take effect.&lt;br /&gt;
* Slow site load times on some servers.&lt;br /&gt;
* Some servers overloaded not leaving processing power for backups.&lt;br /&gt;
* System actively kills any PHP process working too hard or too long (ie backups).&lt;br /&gt;
&lt;br /&gt;
==[http://secure.hostgator.com/cgi-bin/affiliates/clickthru.cgi?id=ithemes HostGator] A==&lt;br /&gt;
'''Benefits'''&lt;br /&gt;
* Fast. Command-line zip available for best BackupBuddy experience.&lt;br /&gt;
* CPanel.&lt;br /&gt;
'''Issues'''&lt;br /&gt;
* Recently changed PHP runtime limit cap to 30 seconds for shared hosting.&lt;br /&gt;
** Possible work-around: http://ithemes.com/forum/index.php?/topic/5519-hostgator-timeout-fix-available/&lt;br /&gt;
** Only causes issues with large sites ( ~1GB or more )&lt;br /&gt;
&lt;br /&gt;
'''Info'''&lt;br /&gt;
* Current limits of their shared and reseller hosting (9/20/2011)&lt;br /&gt;
** safe mode = Off (cannot adjust) &lt;br /&gt;
** memory_limit = 64M (MAXIMUM) &lt;br /&gt;
** max_execution_time = 30 (MAXIMUM) &lt;br /&gt;
** max_input_time = 60 (MAXIMUM) &lt;br /&gt;
** post_max_size = 64M (MAXIMUM) &lt;br /&gt;
** upload_max_filesize = 64M (MAXIMUM) &lt;br /&gt;
** enable_dl = Off (cannot adjust)&lt;br /&gt;
&lt;br /&gt;
==[http://inmotionhosting InMotionHosting]==&lt;br /&gt;
* Slow page loads.&lt;br /&gt;
* Problems reported with sites above 85mb (with zip compression on; off increases limit).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==[http://ipower.com iPower]==&lt;br /&gt;
Minimal issues.&lt;br /&gt;
&lt;br /&gt;
Told a customer that they don't support linux command line zip.&lt;br /&gt;
&lt;br /&gt;
==[http://ipowerweb.com ipowerweb]==&lt;br /&gt;
Minimal issues.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==[http://www.rackspace.com/cloud/ Rackspace Cloud Hosting]==&lt;br /&gt;
* Currently fails path/directory detection preventing backups.&lt;br /&gt;
* We are working with Rackspace to try and get this issue resolved.&lt;br /&gt;
&lt;br /&gt;
==[http://justhost.com JustHost]==&lt;br /&gt;
* JustHost blocks the command line ZIP command which is required for BackupBuddy's normal functionality.&lt;br /&gt;
* Compatibility mode is available but is only recommended for moving away from JustHost hosting.&lt;br /&gt;
&lt;br /&gt;
==[http://wpengine.com/b/ WPEngine]==&lt;br /&gt;
* Doesn't allow/support command line ZIP via PHP's exec() function.&lt;br /&gt;
&lt;br /&gt;
[[Category:PluginBuddy]]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy_Multisite</id>
		<title>BackupBuddy Multisite</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy_Multisite"/>
				<updated>2012-08-13T05:20:43Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Introduction=&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Multisite (BETA) functionality is included with the normal BackupBuddy plugin.  As WordPress Multisite functionality is much more technically complex some BackupBuddy features available for standalone sites are NOT supports for Multisite environments.  Please carefully review the features, differences, and limitations so that you are aware of them and are sure it will meet your needs.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''BackupBuddy Multisite is a BETA product'''.  As such you ''may encounter issues'' using it and we cannot necessarily insure flawless functionality or that issues encountered will be resolved in as timely manner as non-beta features.  Usage of it in a production environment is at your own risk; Import/Export functionality is quite solid but Network migrations have some issues which require additional intervention to fully complete if the URL changes (see limitations below for full details). There is currently not a specific ETA on when the beta tag will be removed. It will be removed once we believe Multisite functionality to be as solid and reliable as the BackupBuddy standalone many have come to love.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Features &amp;amp; Limitation Notes=&lt;br /&gt;
&lt;br /&gt;
* '''Backup entire Multisite Network'''&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a backup, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish backups under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Restore entire Multisite Network (same server &amp;amp; URLs)'''&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a restore, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish restores under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Migrate entire Multisite Network (different server or URLs)'''&lt;br /&gt;
** Limitation: When migrating a Network to a new server or changing URLs, domains, or moving a Network in or out of a subdirectory, BackupBuddy will only migrate the database tables associated with the MAIN site. Due to technical reasons BackupBuddy currently will not automatically migrate URLs or paths of any other subsites within the migrated network.  If the URLs or paths of subsites need to be updated you may perform this procedure by using the 'Mass Database Text Replacement' tool on the 'Server Information' page within BackupBuddy for each subsite you need to update.&lt;br /&gt;
** Limitation: You cannot change from sub-domains to sub-directory URL structure using BackupBuddy Multisite nor can you change from sub-directories to sub-domain URL structure.&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a migration, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish migrations under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Export a subsite from the Network'''&lt;br /&gt;
** Exported subsites may be imported back into the same network (AKA Duplicated), imported into another Network, or restored as a standalone WordPress site using the importbuddy.php tool.&lt;br /&gt;
** Limitation: The main Network [sub]site cannot be exported as it is tied to the Network. It is still included in the main Network backup however.&lt;br /&gt;
&lt;br /&gt;
* '''Import an exported subsite into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Import a backed up standalone site into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Restore or Migrate an exported subsite as a standalone site'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Running Backup, Migrating OR Restoring with BackupBuddy Multisite BETA=&lt;br /&gt;
&lt;br /&gt;
Here is an actual video, from one of our many webinars (we have many regular webinars planned), with details on how to migrate or restore with BackupBuddy. Note: Some functionality has changed and improved since this video was made. It is not the latest version.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|WYhLIK3KfK4|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
=Frequently Asked Questions=&lt;br /&gt;
&lt;br /&gt;
====Are multiple Multisite databases supported?====&lt;br /&gt;
No. A couple of plugins, such as Multi-DB allow Multisite networks to run on multiple databases instead of the normal one.  We do not currently support this custom 3rd party configuration.&lt;br /&gt;
&lt;br /&gt;
====WordPress Multisite Domain Mapping and BackupBuddy Multisite====&lt;br /&gt;
&lt;br /&gt;
Domain mapping was confirmed by customers to work in pre-v3.0 BackupBuddy versions. It has not been officially tested with &amp;gt; 3.0 versions. Customer reports of success/failure are welcomed. Note: Some functionality has changed and improved since this video was made. It is not the latest version.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|oDM5v2Ymk1M|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
====Support Questions====&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Multisite support questions can be asked in the official [http://ithemes.com/forum/backupbuddy-ms/ BackupBuddy Multisite Forums]. &lt;br /&gt;
&lt;br /&gt;
non-Multisite related BackupBuddy support questions can be asked in the official [http://ithemes.com/forum/backupbuddy/ BackupBuddy Forums].&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Pre-Sales questions, for Multisite OR non-Multisite backups and restores/migrations, can be asked on the [http://ithemes.com/forum/pre-sales-and-other-inquiries/ Pre-Sales Forums], via the Live Chat (the Panda icon on top of [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite] page), or by emailing sales@ithemes.com&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
====Official Pages====&lt;br /&gt;
*[http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy]&lt;br /&gt;
*[http://ithemes.com/codex/page/BackupBuddy BackupBuddy Codex - Self-Hosted and Multisite combined]&lt;br /&gt;
====Blog Posts====&lt;br /&gt;
*[http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ 5 Reasons to Love BackupBuddy with Multisite Support - Blog Article]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy Multisite Migration - Expanded Features in Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-ms-released-as-a-beta/ BackupBuddy Multisite Released as Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/how-backupbuddy-changed-my-business-model/ How BackupBuddy changed one of our customer's entire business model!]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy_Multisite</id>
		<title>BackupBuddy Multisite</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy_Multisite"/>
				<updated>2012-08-13T05:06:39Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Introduction=&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Multisite (BETA) functionality is included with the normal BackupBuddy plugin.  As WordPress Multisite functionality is much more technically complex some BackupBuddy features available for standalone sites are NOT supports for Multisite environments.  Please carefully review the features, differences, and limitations so that you are aware of them and are sure it will meet your needs.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''BackupBuddy Multisite is a BETA product'''.  As such you ''may encounter issues'' using it and we cannot necessarily insure flawless functionality or that issues encountered will be resolved in as timely manner as non-beta features.  Usage of it in a production environment is at your own risk; Import/Export functionality is quite solid but Network migrations have some issues which require additional intervention to fully complete if the URL changes (see limitations below for full details). There is currently not a specific ETA on when the beta tag will be removed. It will be removed once we believe Multisite functionality to be as solid and reliable as the BackupBuddy standalone many have come to love.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Features &amp;amp; Limitation Notes=&lt;br /&gt;
&lt;br /&gt;
* '''Backup entire Multisite Network'''&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a backup, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish backups under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Restore entire Multisite Network (same server &amp;amp; URLs)'''&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a restore, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish restores under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Migrate entire Multisite Network (different server or URLs)'''&lt;br /&gt;
** Limitation: When migrating a Network to a new server or changing URLs, domains, or moving a Network in or out of a subdirectory, BackupBuddy will only migrate the database tables associated with the MAIN site. Due to technical reasons BackupBuddy currently will not automatically migrate URLs or paths of any other subsites within the migrated network.  If the URLs or paths of subsites need to be updated you may perform this procedure by using the 'Mass Database Text Replacement' tool on the 'Server Information' page within BackupBuddy for each subsite you need to update.&lt;br /&gt;
** Limitation: You cannot change from sub-domains to sub-directory URL structure using BackupBuddy Multisite nor can you change from sub-directories to sub-domain URL structure.&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a migration, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish migrations under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Export a subsite from the Network'''&lt;br /&gt;
** Exported subsites may be imported back into the same network (AKA Duplicated), imported into another Network, or restored as a standalone WordPress site using the importbuddy.php tool.&lt;br /&gt;
** Limitation: The main Network subsite cannot be exported as it is tied to the Network. It is still included in the main Network backup however.&lt;br /&gt;
&lt;br /&gt;
* '''Import an exported subsite into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Import a backed up standalone site into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Restore or Migrate an exported subsite as a standalone site'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Running Backup, Migrating OR Restoring with BackupBuddy Multisite BETA=&lt;br /&gt;
&lt;br /&gt;
Here is an actual video, from one of our many webinars (we have many regular webinars planned), with details on how to migrate or restore with BackupBuddy. Note: Some functionality has changed and improved since this video was made. It is not the latest version.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|WYhLIK3KfK4|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
=Frequently Asked Questions=&lt;br /&gt;
&lt;br /&gt;
====Are multiple Multisite databases supported?====&lt;br /&gt;
No. A couple of plugins, such as Multi-DB allow Multisite networks to run on multiple databases instead of the normal one.  We do not currently support this custom 3rd party configuration.&lt;br /&gt;
&lt;br /&gt;
====WordPress Multisite Domain Mapping and BackupBuddy Multisite====&lt;br /&gt;
&lt;br /&gt;
Domain mapping was confirmed by customers to work in pre-v3.0 BackupBuddy versions. It has not been officially tested with &amp;gt; 3.0 versions. Customer reports of success/failure are welcomed. Note: Some functionality has changed and improved since this video was made. It is not the latest version.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|oDM5v2Ymk1M|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
====Support Questions====&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Multisite support questions can be asked in the official [http://ithemes.com/forum/backupbuddy-ms/ BackupBuddy Multisite Forums]. &lt;br /&gt;
&lt;br /&gt;
non-Multisite related BackupBuddy support questions can be asked in the official [http://ithemes.com/forum/backupbuddy/ BackupBuddy Forums].&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Pre-Sales questions, for Multisite OR non-Multisite backups and restores/migrations, can be asked on the [http://ithemes.com/forum/pre-sales-and-other-inquiries/ Pre-Sales Forums], via the Live Chat (the Panda icon on top of [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite] page), or by emailing sales@ithemes.com&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
====Official Pages====&lt;br /&gt;
*[http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy]&lt;br /&gt;
*[http://ithemes.com/codex/page/BackupBuddy BackupBuddy Codex - Self-Hosted and Multisite combined]&lt;br /&gt;
====Blog Posts====&lt;br /&gt;
*[http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ 5 Reasons to Love BackupBuddy with Multisite Support - Blog Article]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy Multisite Migration - Expanded Features in Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-ms-released-as-a-beta/ BackupBuddy Multisite Released as Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/how-backupbuddy-changed-my-business-model/ How BackupBuddy changed one of our customer's entire business model!]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy_Multisite</id>
		<title>BackupBuddy Multisite</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy_Multisite"/>
				<updated>2012-08-13T05:03:46Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: /* Features &amp;amp; Limitation Notes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Introduction=&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Multisite (BETA) functionality is included with the normal BackupBuddy plugin.  As WordPress Multisite functionality is much more technically complex some BackupBuddy features available for standalone sites are NOT supports for Multisite environments.  Please carefully review the features, differences, and limitations so that you are aware of them and are sure it will meet your needs.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''BackupBuddy Multisite is a BETA product'''.  As such you ''may encounter issues'' using it and we cannot necessarily insure flawless functionality or that issues encountered will be resolved in as timely manner as non-beta features.  Usage of it in a production environment is at your own risk; Import/Export functionality is quite solid but Network migrations have some issues which require additional intervention to fully complete if the URL changes (see limitations below for full details). There is currently not a specific ETA on when the beta tag will be removed. It will be removed once we believe Multisite functionality to be as solid and reliable as the BackupBuddy standalone many have come to love.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Features &amp;amp; Limitation Notes=&lt;br /&gt;
&lt;br /&gt;
* '''Backup entire Multisite Network'''&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a backup, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish backups under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Restore entire Multisite Network (same server &amp;amp; URLs)'''&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a restore, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish restores under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Migrate entire Multisite Network (different server or URLs)'''&lt;br /&gt;
** Limitation: When migrating a Network to a new server or changing URLs, domains, or moving a Network in or out of a subdirectory, BackupBuddy will only migrate the database tables associated with the MAIN site. Due to technical reasons BackupBuddy currently will not automatically migrate URLs or paths of any other subsites within the migrated network.  If the URLs or paths of subsites need to be updated you may perform this procedure by using the 'Mass Database Text Replacement' tool on the 'Server Information' page within BackupBuddy for each subsite you need to update.&lt;br /&gt;
** Limitation: You cannot change from sub-domains to sub-directory URL structure using BackupBuddy Multisite nor can you change from sub-directories to sub-domain URL structure.&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a migration, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish migrations under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Export a subsite from the Network'''&lt;br /&gt;
** Exported subsites may be imported back into the same network (AKA Duplicated), imported into another Network, or restored as a standalone WordPress site using the importbuddy.php tool.&lt;br /&gt;
** Limitation: The main Network subsite cannot be exported as it is tied to the Network. It is still included in the main Network backup however.&lt;br /&gt;
&lt;br /&gt;
* '''Import an exported subsite into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Import a backed up standalone site into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Restore or Migrate an exported subsite as a standalone site'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
=Running Backup, Migrating OR Restoring with BackupBuddy Multisite BETA=&lt;br /&gt;
&lt;br /&gt;
Here is an actual video, from one of our many webinars (we have many regular webinars planned), with details on how to migrate or restore with BackupBuddy. Note: Some functionality has changed and improved since this video was made. It is not the latest version.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|WYhLIK3KfK4|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
=Frequently Asked Questions=&lt;br /&gt;
&lt;br /&gt;
====WordPress Multisite Domain Mapping and BackupBuddy Multisite====&lt;br /&gt;
&lt;br /&gt;
Domain mapping was confirmed by customers to work in pre-v3.0 BackupBuddy versions. It has not been officially tested with &amp;gt; 3.0 versions. Customer reports of success/failure are welcomed. Note: Some functionality has changed and improved since this video was made. It is not the latest version.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|oDM5v2Ymk1M|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
====Support Questions====&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Multisite support questions can be asked in the official [http://ithemes.com/forum/backupbuddy-ms/ BackupBuddy Multisite Forums]. &lt;br /&gt;
&lt;br /&gt;
non-Multisite related BackupBuddy support questions can be asked in the official [http://ithemes.com/forum/backupbuddy/ BackupBuddy Forums].&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Pre-Sales questions, for Multisite OR non-Multisite backups and restores/migrations, can be asked on the [http://ithemes.com/forum/pre-sales-and-other-inquiries/ Pre-Sales Forums], via the Live Chat (the Panda icon on top of [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite] page), or by emailing sales@ithemes.com&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
====Official Pages====&lt;br /&gt;
*[http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy]&lt;br /&gt;
*[http://ithemes.com/codex/page/BackupBuddy BackupBuddy Codex - Self-Hosted and Multisite combined]&lt;br /&gt;
====Blog Posts====&lt;br /&gt;
*[http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ 5 Reasons to Love BackupBuddy with Multisite Support - Blog Article]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy Multisite Migration - Expanded Features in Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-ms-released-as-a-beta/ BackupBuddy Multisite Released as Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/how-backupbuddy-changed-my-business-model/ How BackupBuddy changed one of our customer's entire business model!]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy_Multisite</id>
		<title>BackupBuddy Multisite</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy_Multisite"/>
				<updated>2012-08-13T05:01:34Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: /* WordPress Multisite Domain Mapping and BackupBuddy Multisite */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Introduction=&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Multisite (BETA) functionality is included with the normal BackupBuddy plugin.  As WordPress Multisite functionality is much more technically complex some BackupBuddy features available for standalone sites are NOT supports for Multisite environments.  Please carefully review the features, differences, and limitations so that you are aware of them and are sure it will meet your needs.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''BackupBuddy Multisite is a BETA product'''.  As such you ''may encounter issues'' using it and we cannot necessarily insure flawless functionality or that issues encountered will be resolved in as timely manner as non-beta features.  Usage of it in a production environment is at your own risk; Import/Export functionality is quite solid but Network migrations have some issues which require additional intervention to fully complete if the URL changes (see limitations below for full details). There is currently not a specific ETA on when the beta tag will be removed. It will be removed once we believe Multisite functionality to be as solid and reliable as the BackupBuddy standalone many have come to love.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Features &amp;amp; Limitation Notes=&lt;br /&gt;
&lt;br /&gt;
* '''Backup entire Multisite Network'''&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a backup, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish backups under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Restore entire Multisite Network (same server &amp;amp; URLs)'''&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a restore, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish restores under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Migrate entire Multisite Network (different server or URLs)'''&lt;br /&gt;
** Limitation: When migrating a Network to a new server or changing URLs, domains, or moving a Network in or out of a subdirectory, BackupBuddy will only migrate the database tables associated with the MAIN site. Due to technical reasons BackupBuddy currently will not automatically migrate URLs or paths of any other subsites within the migrated network.  If the URLs or paths of subsites need to be updated you may perform this procedure by using the 'Mass Database Text Replacement' tool on the 'Server Information' page within BackupBuddy for each subsite you need to update.&lt;br /&gt;
** Limitation: You cannot change from sub-domains to sub-directory URL structure using BackupBuddy Multisite nor can you change from sub-directories to sub-domain URL structure.&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a migration, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish migrations under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Export a subsite from the Network'''&lt;br /&gt;
* Exported subsites may be imported back into the same network (AKA Duplicated), imported into another Network, or restored as a standalone WordPress site using the importbuddy.php tool.&lt;br /&gt;
** Limitation: The main Network subsite cannot be exported as it is tied to the Network. It is still included in the main Network backup however.&lt;br /&gt;
&lt;br /&gt;
* '''Import an exported subsite into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Import a backed up standalone site into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Restore or Migrate an exported subsite as a standalone site'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Running Backup, Migrating OR Restoring with BackupBuddy Multisite BETA=&lt;br /&gt;
&lt;br /&gt;
Here is an actual video, from one of our many webinars (we have many regular webinars planned), with details on how to migrate or restore with BackupBuddy. Note: Some functionality has changed and improved since this video was made. It is not the latest version.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|WYhLIK3KfK4|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
=Frequently Asked Questions=&lt;br /&gt;
&lt;br /&gt;
====WordPress Multisite Domain Mapping and BackupBuddy Multisite====&lt;br /&gt;
&lt;br /&gt;
Domain mapping was confirmed by customers to work in pre-v3.0 BackupBuddy versions. It has not been officially tested with &amp;gt; 3.0 versions. Customer reports of success/failure are welcomed. Note: Some functionality has changed and improved since this video was made. It is not the latest version.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|oDM5v2Ymk1M|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
====Support Questions====&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Multisite support questions can be asked in the official [http://ithemes.com/forum/backupbuddy-ms/ BackupBuddy Multisite Forums]. &lt;br /&gt;
&lt;br /&gt;
non-Multisite related BackupBuddy support questions can be asked in the official [http://ithemes.com/forum/backupbuddy/ BackupBuddy Forums].&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Pre-Sales questions, for Multisite OR non-Multisite backups and restores/migrations, can be asked on the [http://ithemes.com/forum/pre-sales-and-other-inquiries/ Pre-Sales Forums], via the Live Chat (the Panda icon on top of [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite] page), or by emailing sales@ithemes.com&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
====Official Pages====&lt;br /&gt;
*[http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy]&lt;br /&gt;
*[http://ithemes.com/codex/page/BackupBuddy BackupBuddy Codex - Self-Hosted and Multisite combined]&lt;br /&gt;
====Blog Posts====&lt;br /&gt;
*[http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ 5 Reasons to Love BackupBuddy with Multisite Support - Blog Article]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy Multisite Migration - Expanded Features in Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-ms-released-as-a-beta/ BackupBuddy Multisite Released as Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/how-backupbuddy-changed-my-business-model/ How BackupBuddy changed one of our customer's entire business model!]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy_Multisite</id>
		<title>BackupBuddy Multisite</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy_Multisite"/>
				<updated>2012-08-13T05:01:23Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: /* Running Backup, Migrating OR Restoring with BackupBuddy Multisite BETA */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Introduction=&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Multisite (BETA) functionality is included with the normal BackupBuddy plugin.  As WordPress Multisite functionality is much more technically complex some BackupBuddy features available for standalone sites are NOT supports for Multisite environments.  Please carefully review the features, differences, and limitations so that you are aware of them and are sure it will meet your needs.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''BackupBuddy Multisite is a BETA product'''.  As such you ''may encounter issues'' using it and we cannot necessarily insure flawless functionality or that issues encountered will be resolved in as timely manner as non-beta features.  Usage of it in a production environment is at your own risk; Import/Export functionality is quite solid but Network migrations have some issues which require additional intervention to fully complete if the URL changes (see limitations below for full details). There is currently not a specific ETA on when the beta tag will be removed. It will be removed once we believe Multisite functionality to be as solid and reliable as the BackupBuddy standalone many have come to love.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Features &amp;amp; Limitation Notes=&lt;br /&gt;
&lt;br /&gt;
* '''Backup entire Multisite Network'''&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a backup, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish backups under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Restore entire Multisite Network (same server &amp;amp; URLs)'''&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a restore, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish restores under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Migrate entire Multisite Network (different server or URLs)'''&lt;br /&gt;
** Limitation: When migrating a Network to a new server or changing URLs, domains, or moving a Network in or out of a subdirectory, BackupBuddy will only migrate the database tables associated with the MAIN site. Due to technical reasons BackupBuddy currently will not automatically migrate URLs or paths of any other subsites within the migrated network.  If the URLs or paths of subsites need to be updated you may perform this procedure by using the 'Mass Database Text Replacement' tool on the 'Server Information' page within BackupBuddy for each subsite you need to update.&lt;br /&gt;
** Limitation: You cannot change from sub-domains to sub-directory URL structure using BackupBuddy Multisite nor can you change from sub-directories to sub-domain URL structure.&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a migration, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish migrations under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Export a subsite from the Network'''&lt;br /&gt;
* Exported subsites may be imported back into the same network (AKA Duplicated), imported into another Network, or restored as a standalone WordPress site using the importbuddy.php tool.&lt;br /&gt;
** Limitation: The main Network subsite cannot be exported as it is tied to the Network. It is still included in the main Network backup however.&lt;br /&gt;
&lt;br /&gt;
* '''Import an exported subsite into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Import a backed up standalone site into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Restore or Migrate an exported subsite as a standalone site'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Running Backup, Migrating OR Restoring with BackupBuddy Multisite BETA=&lt;br /&gt;
&lt;br /&gt;
Here is an actual video, from one of our many webinars (we have many regular webinars planned), with details on how to migrate or restore with BackupBuddy. Note: Some functionality has changed and improved since this video was made. It is not the latest version.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|WYhLIK3KfK4|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
=Frequently Asked Questions=&lt;br /&gt;
&lt;br /&gt;
====WordPress Multisite Domain Mapping and BackupBuddy Multisite====&lt;br /&gt;
&lt;br /&gt;
Domain mapping was confirmed by customers to work in pre-v3.0 BackupBuddy versions. It has not been officially tested with &amp;gt; 3.0 versions. Customer reports of success/failure are welcomed.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|oDM5v2Ymk1M|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Support Questions====&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Multisite support questions can be asked in the official [http://ithemes.com/forum/backupbuddy-ms/ BackupBuddy Multisite Forums]. &lt;br /&gt;
&lt;br /&gt;
non-Multisite related BackupBuddy support questions can be asked in the official [http://ithemes.com/forum/backupbuddy/ BackupBuddy Forums].&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Pre-Sales questions, for Multisite OR non-Multisite backups and restores/migrations, can be asked on the [http://ithemes.com/forum/pre-sales-and-other-inquiries/ Pre-Sales Forums], via the Live Chat (the Panda icon on top of [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite] page), or by emailing sales@ithemes.com&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
====Official Pages====&lt;br /&gt;
*[http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy]&lt;br /&gt;
*[http://ithemes.com/codex/page/BackupBuddy BackupBuddy Codex - Self-Hosted and Multisite combined]&lt;br /&gt;
====Blog Posts====&lt;br /&gt;
*[http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ 5 Reasons to Love BackupBuddy with Multisite Support - Blog Article]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy Multisite Migration - Expanded Features in Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-ms-released-as-a-beta/ BackupBuddy Multisite Released as Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/how-backupbuddy-changed-my-business-model/ How BackupBuddy changed one of our customer's entire business model!]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	<entry>
		<id>http://ithemes.com/codex/page/BackupBuddy_Multisite</id>
		<title>BackupBuddy Multisite</title>
		<link rel="alternate" type="text/html" href="http://ithemes.com/codex/page/BackupBuddy_Multisite"/>
				<updated>2012-08-13T05:00:18Z</updated>
		
		<summary type="html">&lt;p&gt;Dustin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Introduction=&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Multisite (BETA) functionality is included with the normal BackupBuddy plugin.  As WordPress Multisite functionality is much more technically complex some BackupBuddy features available for standalone sites are NOT supports for Multisite environments.  Please carefully review the features, differences, and limitations so that you are aware of them and are sure it will meet your needs.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''BackupBuddy Multisite is a BETA product'''.  As such you ''may encounter issues'' using it and we cannot necessarily insure flawless functionality or that issues encountered will be resolved in as timely manner as non-beta features.  Usage of it in a production environment is at your own risk; Import/Export functionality is quite solid but Network migrations have some issues which require additional intervention to fully complete if the URL changes (see limitations below for full details). There is currently not a specific ETA on when the beta tag will be removed. It will be removed once we believe Multisite functionality to be as solid and reliable as the BackupBuddy standalone many have come to love.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Features &amp;amp; Limitation Notes=&lt;br /&gt;
&lt;br /&gt;
* '''Backup entire Multisite Network'''&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a backup, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish backups under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Restore entire Multisite Network (same server &amp;amp; URLs)'''&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a restore, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish restores under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Migrate entire Multisite Network (different server or URLs)'''&lt;br /&gt;
** Limitation: When migrating a Network to a new server or changing URLs, domains, or moving a Network in or out of a subdirectory, BackupBuddy will only migrate the database tables associated with the MAIN site. Due to technical reasons BackupBuddy currently will not automatically migrate URLs or paths of any other subsites within the migrated network.  If the URLs or paths of subsites need to be updated you may perform this procedure by using the 'Mass Database Text Replacement' tool on the 'Server Information' page within BackupBuddy for each subsite you need to update.&lt;br /&gt;
** Limitation: You cannot change from sub-domains to sub-directory URL structure using BackupBuddy Multisite nor can you change from sub-directories to sub-domain URL structure.&lt;br /&gt;
** Limitation: As a Network can contain many subsites, each subsite increases the amount of time needed to perform a migration, especially if the sites are large.  This can demand more server resources or more PHP runtime.  Most shared hosting does not permit increasing these resources so BackupBuddy may not be able to finish migrations under these conditions.  If you have access to modify these settings, Maximum PHP runtime is a key setting to increase as needed.&lt;br /&gt;
&lt;br /&gt;
* '''Export a subsite from the Network'''&lt;br /&gt;
* Exported subsites may be imported back into the same network (AKA Duplicated), imported into another Network, or restored as a standalone WordPress site using the importbuddy.php tool.&lt;br /&gt;
** Limitation: The main Network subsite cannot be exported as it is tied to the Network. It is still included in the main Network backup however.&lt;br /&gt;
&lt;br /&gt;
* '''Import an exported subsite into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Import a backed up standalone site into the Network'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
* '''Restore or Migrate an exported subsite as a standalone site'''&lt;br /&gt;
** No known limitations beyond those of normal BackupBuddy.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Running Backup, Migrating OR Restoring with BackupBuddy Multisite BETA=&lt;br /&gt;
&lt;br /&gt;
Here is an actual video, from one of our many webinars (we have many regular webinars planned), with details on how to migrate or restore with BackupBuddy:&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|WYhLIK3KfK4|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Frequently Asked Questions=&lt;br /&gt;
&lt;br /&gt;
====WordPress Multisite Domain Mapping and BackupBuddy Multisite====&lt;br /&gt;
&lt;br /&gt;
Domain mapping was confirmed by customers to work in pre-v3.0 BackupBuddy versions. It has not been officially tested with &amp;gt; 3.0 versions. Customer reports of success/failure are welcomed.&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|oDM5v2Ymk1M|600|BackupBuddy Multisite}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Support Questions====&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Multisite support questions can be asked in the official [http://ithemes.com/forum/backupbuddy-ms/ BackupBuddy Multisite Forums]. &lt;br /&gt;
&lt;br /&gt;
non-Multisite related BackupBuddy support questions can be asked in the official [http://ithemes.com/forum/backupbuddy/ BackupBuddy Forums].&lt;br /&gt;
&lt;br /&gt;
BackupBuddy Pre-Sales questions, for Multisite OR non-Multisite backups and restores/migrations, can be asked on the [http://ithemes.com/forum/pre-sales-and-other-inquiries/ Pre-Sales Forums], via the Live Chat (the Panda icon on top of [http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy Multisite] page), or by emailing sales@ithemes.com&lt;br /&gt;
&lt;br /&gt;
=Additional Resources=&lt;br /&gt;
====Official Pages====&lt;br /&gt;
*[http://pluginbuddy.com/purchase/backupbuddy/ Get BackupBuddy]&lt;br /&gt;
*[http://ithemes.com/codex/page/BackupBuddy BackupBuddy Codex - Self-Hosted and Multisite combined]&lt;br /&gt;
====Blog Posts====&lt;br /&gt;
*[http://pluginbuddy.com/5-reasons-to-love-backupbuddy-with-new-wordpress-multisite-support/ 5 Reasons to Love BackupBuddy with Multisite Support - Blog Article]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-multisite-migration-expanded-features-in-beta-coming-soon/ BackupBuddy Multisite Migration - Expanded Features in Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/backupbuddy-ms-released-as-a-beta/ BackupBuddy Multisite Released as Beta - Announcement]&lt;br /&gt;
*[http://pluginbuddy.com/how-backupbuddy-changed-my-business-model/ How BackupBuddy changed one of our customer's entire business model!]&lt;/div&gt;</summary>
		<author><name>Dustin</name></author>	</entry>

	</feed>