* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.

* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.

** Backups will be stored in /wp-content/uploads/backupbuddy_backups/

** Backups will be stored in /wp-content/uploads/backupbuddy_backups/

Line 48:

Line 41:

** PHP exec() function enabled

** PHP exec() function enabled

** PHP ZipArchive class installed

** PHP ZipArchive class installed

−

* Linux:

+

* Linux (Apache):

** Command-line zip installed and accessible via exec().

** Command-line zip installed and accessible via exec().

* Windows (only supported for local development via Apache; IIS is not officially supported):

* Windows (only supported for local development via Apache; IIS is not officially supported):

Line 54:

Line 47:

*** You must have the ability to configure your server to allow execution of this zip.exe file for it to function.

*** 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.

*** 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 v3.0) in the parent directory.

+

* 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)===

===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.'''

'' 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.'''

** 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 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.

* Write permissions to /wp-content/uploads/ for the user running BackupBuddy.

* BackupBuddy requires the uploads directory to be in the standard WordPress location.

* BackupBuddy requires the uploads directory to be in the standard WordPress location.

Line 69:

Line 62:

** Temporary files will be stored in /wp-content/uploads/backupbuddy_temp/xxxxxxx/ (temporarily generated at each backup)

** 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.

* 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 v3.0) in the parent directory.

+

* wp-config.php file must be in WordPress installation directory OR (starting with BackupBuddy v3.0) in the parent directory.

===Host Compatibility===

===Host Compatibility===

Line 82:

Line 75:

===Frequently Seen Support Issues===

===Frequently Seen Support Issues===

−

''Problems?'' Start with the [[BackupBuddy:_Frequent_Support_Issues|Frequently Seen Support Issues]] to most quickly troubleshoot your problem.

+

''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.

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.

Settings Explained

Developing Locally

Specifications

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 & recommendations.

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.

Host Compatibility

Misc. Information

Troubleshooting

Frequently Seen Support Issues

Problems? We have compiled a list of issues and solutions to many problems that we have seen encountered before. Frequently Seen Support Issues to attempt to narrow down your problem and find a solution.

BackupBuddy: Error Codes

Receive an error code? Check out the Error Codes page for explanations.

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.