BackupBuddy Specifications: Server Configuration and Minimum Requirements

From IThemes Codex
(Difference between revisions)
Jump to: navigation, search
(See also)
(Minimum Server Requirements (Reduced Functionality))
 
(4 intermediate revisions by 2 users not shown)
Line 7: Line 7:
 
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires mySQL 5.0.15+]
 
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires mySQL 5.0.15+]
 
** For best results, use MySQL 5.1+
 
** For best results, use MySQL 5.1+
* WordPress 3.4+  
+
* WordPress 3.5+  
 
* Write permissions to <code>/wp-content/uploads/</code> for the user running BackupBuddy.
 
* Write permissions to <code>/wp-content/uploads/</code> for the user running BackupBuddy.
 
** Backups will be stored in <code>/wp-content/uploads/backupbuddy_backups/</code>
 
** Backups will be stored in <code>/wp-content/uploads/backupbuddy_backups/</code>
Line 29: Line 29:
 
* mySQL 5.x+
 
* mySQL 5.x+
 
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires mySQL 5.0.15+]
 
** [http://wordpress.org/news/2010/07/eol-for-php4-and-mysql4/ WordPress v3.2+ requires mySQL 5.0.15+]
* WordPress 3.3+
+
* WordPress 3.4+
 
** 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 & direct restores for older versions and use it for safety while upgrading to the latest WordPress).
 
** 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 & direct restores for older versions and use it for safety while upgrading to the latest WordPress).
 
* Write permissions to <code>/wp-content/uploads/</code> for the user running BackupBuddy.
 
* Write permissions to <code>/wp-content/uploads/</code> for the user running BackupBuddy.
Line 43: Line 43:
 
* [[BackupBuddy_Specifications:_Server_Configuration_and_Minimum_Requirements|Specifications: Server Configuration & Minimum Requirements]]
 
* [[BackupBuddy_Specifications:_Server_Configuration_and_Minimum_Requirements|Specifications: Server Configuration & Minimum Requirements]]
 
* [[BackupBuddy:_Host_Compatibility|Host Compatibility]]
 
* [[BackupBuddy:_Host_Compatibility|Host Compatibility]]
 +
*[[BackupBuddy:_Downloading|Downloading]]
 
* [[BackupBuddy:_Installation|Installation]]
 
* [[BackupBuddy:_Installation|Installation]]
 
* [[BackupBuddy:_Quick_Setup|Quick Setup]]
 
* [[BackupBuddy:_Quick_Setup|Quick Setup]]
Line 50: Line 51:
  
 
<br />
 
<br />
[[:BackupBuddy_Test|← Back to BackupBuddy Codex Home]]
+
[[:BackupBuddy|← Back to BackupBuddy Codex Home]]

Latest revision as of 07:25, October 29, 2013

Server configuration is a very complex topic and varies widely between hosts, server operating systems and even the personal preference of the server administrator. The following are server recommendations for full BackupBuddy functionality.

Server Recommendations (Full Functionality)

  • PHP 5.2+
  • mySQL 5.x+
  • WordPress 3.5+
  • Write permissions to /wp-content/uploads/ for the user running BackupBuddy.
    • Backups will be stored in /wp-content/uploads/backupbuddy_backups/
    • Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)
  • Free disk space equal to or greater than the entire size of your site once compressed.
    • SuPHP or environment so that file operations/zip run as user to prevent permissions issues.
    • PHP exec() function enabled
    • PHP ZipArchive class installed
  • Linux (Apache; Some Litespeed server setups have broken performance inhibiting BackupBuddy):
    • Command-line zip installed and accessible via exec().
  • Windows (only supported for local development via Apache; IIS is not officially supported):
    • Windows zip executable (available here)
      • You must have the ability to configure your server to allow execution of this zip.exe file for it to function.
      • File permissions must also be set to allow access and execution of the zip executable.
  • wp-config.php file must be in WordPress installation directory OR (starting with BackupBuddy v3.0) in the parent directory.

Minimum Server Requirements (Reduced Functionality)

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.

  • PHP 5.2+
  • mySQL 5.x+
  • WordPress 3.4+
    • 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 & direct restores for older versions and use it for safety while upgrading to the latest WordPress).
  • Write permissions to /wp-content/uploads/ for the user running BackupBuddy.
  • BackupBuddy requires the uploads directory to be in the standard WordPress location.
    • Backups will be stored in /wp-content/uploads/backupbuddy_backups/
    • Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)
  • Free disk space equal to or greater than the entire size of your site once compressed.
  • wp-config.php file must be in WordPress installation directory OR (starting with BackupBuddy v3.0) in the parent directory.

See also


← Back to BackupBuddy Codex Home

Personal tools
Namespaces
Variants
Actions
iThemes Codex
Codex Navigation
Toolbox