Title: WP STAGING &#8212; Backups &amp; Restore, Migration &amp; Clone Plugin &#8212; Cloud Backups, Scheduled Backups
Author: Rene Hermenau
Published: <strong>05.08.2015</strong>
Last modified: 09.10.2026

---

Поиск плагинов

![](https://ps.w.org/wp-staging/assets/banner-772x250.png?rev=2602209)

![](https://ps.w.org/wp-staging/assets/icon-256x256.png?rev=2972932)

# WP STAGING — Backups & Restore, Migration & Clone Plugin — Cloud Backups, Scheduled Backups

 Автор: [Rene Hermenau](https://profiles.wordpress.org/renehermi/)

[Скачать](https://downloads.wordpress.org/plugin/wp-staging.4.17.0.zip)

[Предпросмотр в реальном времени](https://ru.wordpress.org/plugins/wp-staging/?preview=1)

 * [Детали](https://ru.wordpress.org/plugins/wp-staging/#description)
 * [Отзывы](https://ru.wordpress.org/plugins/wp-staging/#reviews)
 *  [Установка](https://ru.wordpress.org/plugins/wp-staging/#installation)
 * [Разработка](https://ru.wordpress.org/plugins/wp-staging/#developers)

 [Поддержка](https://wordpress.org/support/plugin/wp-staging/)

## Описание

### WordPress Backup, Restore, Staging, Cloning & Migration — All in One

WP STAGING is the all-in-one WordPress backup, restore, staging, cloning, and migration
plugin, built for professional workflows with 100% unit-tested code, thousands of
automated tests, and extensive end-to-end testing across supported PHP versions.

Create a full backup or an exact clone or copy of your website in minutes. Use it
to duplicate your site, test plugin and theme updates safely, restore your site 
when needed, move or migrate WordPress to another server, transfer your site to 
a new host, or build a staging copy before making changes. WP STAGING also works
as a WordPress duplicator, so you do not need a separate duplicator plugin to copy
your website.

WP STAGING reliably backs up, clones, and migrates WooCommerce stores too, including
orders, products, and customer data.

WP STAGING is developed in Germany and designed for agencies, developers, and businesses
that need reliable WordPress backup, recovery, staging, restore, and migration workflows.

[WP STAGING | PRO](https://wp-staging.com/backup-wordpress) also includes advanced
workflows such as [Remote Sync](https://wp-staging.com/docs/pull-a-wordpress-site-from-one-server-to-another/),
which lets you pull a WordPress site securely from one server to another using an
API key, and [WP STAGING CLI](https://wp-staging.com/cli/upgrade), which can turn
a WP STAGING backup into a local Docker-based development site.

All data stays on your server unless you choose a transfer or remote storage workflow.
WP STAGING is designed for speed, reliability, and low-resource environments, including
shared hosting.

WP STAGING automatically performs search and replace for links and paths during 
cloning, backup, restore, and migration workflows.

**This staging and backup plugin can clone your website quickly and efficiently,
even if it is running on a weak shared hosting server.**

### WP STAGING FREE — BACKUP & STAGING FEATURES

 * Clone the entire production site into a subdirectory like example.com/staging-
   site.
 * High-performance backup and cloning, even for websites with very large databases.
 * Create full or partial backups — full-site backup, database-only, or files-only
   backups.
 * Scheduled backups with automatic daily backups.
 * Easy to use: create a clone or backup in one click.
 * Efficient background processing without slowing down your website.
 * No Software as a Service and no external account required.
 * All your data stays on your server. Your data belongs to you only.
 * No server timeouts on huge websites or weak servers.
 * Fast backup, clone, and restore workflows depending on site size and server resources.
 * Use the clone as part of your backup and update strategy.
 * Only administrators can access the cloned or backup website.
 * SEO-friendly staging sites with login protection and no-index handling.
 * The admin bar on the staging / backup website is orange colored and shows when
   you work on the staging site.
 * Extensive logging features.
 * Supports Apache, Nginx, Microsoft IIS, and LiteSpeed Server.
 * Every release passes extensive automated tests to keep the plugin robust, reliable,
   and fast.
 * Fast and professional support team.

### WP STAGING | PRO — BACKUP & STAGING FEATURES

The features below are available in [WP STAGING | PRO](https://wp-staging.com/backup-pro-features).

 * Remote Sync — Pull a WordPress site securely from one server to another.
 * WP STAGING CLI — Turn a backup into a local Docker-based development site.
 * Migrate and transfer WordPress to another host or domain.
 * Push staging changes to production (staging to live), including plugins, themes,
   and media files, with one click.
 * Clone a backup or staging site to a separate database.
 * Choose a custom directory for a backup or cloned site.
 * Select a custom subdomain destination like dev.example.com.
 * Define user roles for accessing the clone or backup site. This can be clients
   or external developers.
 * Multisite support for migration, backup, and cloning.
 * Schedule recurring backups by time and interval.
 * Download and upload backups to another server for migration and transfer.
 * Backup retention settings.
 * Custom backup names.
 * Email notifications if a backup cannot be created.
 * WordPress multisite backup and restore.
 * Cloud backup, offsite backup, and remote backups to external storage providers.
 * Backup to Google Drive.
 * Backup to Amazon S3.
 * Backup to (S)FTP.
 * Backup to Dropbox.
 * Custom backup folder destinations for cloud storage providers.
 * Priority support.

### DOCUMENTATION

**How to Backup and Restore WordPress**
 [Backup and Restore WordPress](https://wp-staging.com/docs/how-to-backup-and-restore-your-wordpress-website/)

**Backup & Transfer WordPress Site to Another Host**
 [How to Migrate Your WordPress Site to a New Host](https://wp-staging.com/docs/how-to-migrate-your-wordpress-site-to-a-new-host/)

**Remote Sync**
 [Pull a WordPress Site from One Server to Another](https://wp-staging.com/docs/pull-a-wordpress-site-from-one-server-to-another/)

**Local Docker Development with WP STAGING CLI**
 [WP STAGING CLI – Upgrade Now](https://wp-staging.com/cli/upgrade)

**All Backup Guides**
 [All Backup Guides](https://wp-staging.com/docs/category/backup-restore/)

**Working with Staging Sites**
 [Working with Staging Sites](https://wp-staging.com/docs/category/working-with-wp-staging/)

**FAQ for Backup & Cloning**
 [FAQ for Backup & Cloning](https://wp-staging.com/docs/category/frequently-asked-questions/)

**Troubleshooting Backup & Cloning**
 [Troubleshooting Backup & Cloning](https://wp-staging.com/docs/category/troubleshooting/)

### WP STAGING BACKUP & CLONING TECHNICAL REQUIREMENTS & INFORMATION

 * Works on latest version of WordPress
 * Minimum Supported WordPress Version 3.8
 * Cloning and Backup work on all webhosts
 * No extra libraries required
 * Backup & cloning supports huge websites
 * Custom backup format is much faster and smaller than any tar or zip compression
 * Backup & cloning works in low memory & shared hosting environments

### SUPPORT

[WP STAGING Backup & Cloning](https://wp-staging.com/backup-wordpress)

## Скриншоты

[⌊Create new WordPress staging / backup site (Dark Mode)⌉⌊Create new WordPress staging/
backup site (Dark Mode)⌉[

Create new WordPress staging / backup site (Dark Mode)

[⌊Create new WordPress staging / backup site (Lite Mode)⌉⌊Create new WordPress staging/
backup site (Lite Mode)⌉[

Create new WordPress staging / backup site (Lite Mode)

[⌊Select name for staging / backup site (Lite Mode)⌉⌊Select name for staging / backup
site (Lite Mode)⌉[

Select name for staging / backup site (Lite Mode)

[⌊Create Full Site Backup (Dark Mode)⌉⌊Create Full Site Backup (Dark Mode)⌉[

Create Full Site Backup (Dark Mode)

[⌊Create Full Site Backup (Lite Mode)⌉⌊Create Full Site Backup (Lite Mode)⌉[

Create Full Site Backup (Lite Mode)

[⌊Cloning / backup processing (Dark Mode)⌉⌊Cloning / backup processing (Dark Mode
)⌉[

Cloning / backup processing (Dark Mode)

[⌊Backup Complete (Dark Mode)⌉⌊Backup Complete (Dark Mode)⌉[

Backup Complete (Dark Mode)

[⌊Login to staging site⌉⌊Login to staging site⌉[

Login to staging site

[⌊Staging demo site⌉⌊Staging demo site⌉[

Staging demo site

## Установка

#### Installation via admin plugin search

 1. Go to Plugins > Add new. Select «Author» from the dropdown near search input.
 2. Search for «WP STAGING». Searching for «WPStaging» in one word works as well.
 3. Find «WP STAGING — WordPress Backup, Restore & Migration» and click the «Install
    Now» button.
 4. Activate the plugin.
 5. The plugin should be shown below settings menu.

#### Admin Installer via zip

 1. Visit the Add New plugin screen and click the «Upload Plugin» button.
 2. Click the «Browse…» button and select the zip file of our plugin.
 3. Click «Install Now» button.
 4. Once uploading is done, activate WP STAGING — WordPress Backup, Restore & Migration.
 5. The plugin should be shown below the settings menu.

## Часто задаваемые вопросы

### Why should I use a staging site and backup workflow?

Plugin updates, theme changes, and custom code should be tested before they reach
your live site. A staging workflow lets you clone your production website, test 
changes safely, and keep a working backup ready in case something goes wrong. Safe
updates and update testing on a staging copy protect your live site from broken 
releases.

Usually, it is best to run the staging site on an environment as close as possible
to the production server. That is the best way to catch compatibility issues before
they affect your live site.

WP STAGING combines backup, restore, staging, and migration in one workflow, so 
you can protect your live website, reduce downtime risk, and ship changes with more
confidence.

### Is WP STAGING a backup plugin?

Yes. WP STAGING started as a staging plugin and grew into a complete WordPress backup
plugin, with restore, staging, cloning, and migration in one tool.

Even the free version lets you create backups and restore them when needed. [WP STAGING | PRO](https://wp-staging.com/backup-wordpress)
adds more advanced backup workflows, cloud storage destinations, migration tools,
and developer-focused features.

### How is WP STAGING different from other backup plugins?

WP STAGING combines backup, restore, staging, cloning, and migration in one workflow.
While many backup plugins focus mainly on archive-based backups or simple migration,
WP STAGING also helps you create a working staging copy, test updates safely, and
restore your site when needed.

Some backup plugins focus mainly on creating backup archives, while WP STAGING also
creates working staging copies for safer testing and rollback workflows. This is
especially useful when you want production-like validation before pushing changes
live.

Some backup plugins may not fully support custom tables in all scenarios. WP STAGING
is designed to work reliably with staging workflows and custom table prefixes used
by its own cloned environments.

[WP STAGING | PRO](https://wp-staging.com/backup-wordpress) also includes advanced
workflows such as [Remote Sync](https://wp-staging.com/docs/pull-a-wordpress-site-from-one-server-to-another/)
and [WP STAGING CLI](https://wp-staging.com/cli/upgrade), which can turn a backup
into a local Docker-based development site. That makes WP STAGING especially attractive
for developers, agencies, and site owners who want more than a basic backup plugin.

### How do I back up and restore a WordPress site?

After installing WP STAGING, go to the backup section in the plugin and create a
full-site backup. You can then restore that backup if a plugin update, theme change,
deployment, or unexpected issue breaks your site.

WP STAGING is designed to make backup and restore simple, even on shared hosting
and large WordPress installations.

### What is Remote Sync in WP STAGING Pro?

Remote Sync is a Pro feature that lets you pull a WordPress site securely from one
server to another using an API key. Instead of manually exporting databases and 
copying files, you connect the two sites and start the sync from inside WP STAGING.

This is especially useful for agencies, developers, and site owners who want a faster
and more reliable workflow for moving content between WordPress installs.

Learn more:
 [Remote Sync: Pull a WordPress Site from One Server to Another](https://wp-staging.com/docs/pull-a-wordpress-site-from-one-server-to-another/)

### How can I turn a backup into a local Docker development site?

[WP STAGING | PRO](https://wp-staging.com/backup-wordpress) includes access to [WP STAGING CLI](https://wp-staging.com/cli/upgrade),
which can turn a WP STAGING backup into a local Docker-based WordPress site with
one command.

This is ideal for debugging, QA, development, and reproducing client issues locally.
It helps you create repeatable local environments without building custom Docker
setups for every project.

Learn more:
 [WP STAGING CLI – Upgrade Now](https://wp-staging.com/cli/upgrade)

### How do I move, migrate, or transfer a WordPress site to a new host?

[WP STAGING | PRO](https://wp-staging.com/backup-wordpress) includes migration and
transfer workflows that help you move a WordPress website to another host, transfer
your WordPress site to a new host, change the domain, or move to another server.
You can move your website between hosts without manual database exports.

If you want a guided step-by-step walkthrough, see:
 [How to Migrate Your WordPress Site to a New Host](https://wp-staging.com/docs/how-to-migrate-your-wordpress-site-to-a-new-host/)

### How do I duplicate or clone a WordPress site?

WP STAGING works as a WordPress duplicator: it can duplicate or clone a WordPress
site in a few clicks and create an exact copy of your site for testing, development,
or as a safety net. Duplication runs in the background, so you can duplicate even
large WordPress sites on shared hosting. If you have used a plugin like Duplicator
before, WP STAGING covers the same clone and copy workflows and adds backup, restore,
and staging.

### Is WP STAGING a good Duplicator alternative?

Yes. If you are looking for a Duplicator alternative, WP STAGING covers the same
use cases: duplicate a WordPress site, create a full-site copy, and move or transfer
it to another host. In addition to the duplicator workflow, you get one-click staging
sites, scheduled backups, and restore in the same plugin.

### Why do I need a backup plugin at all?

Consistent website backups are the foundation of a robust disaster recovery strategy.
They protect your website against failed updates, user mistakes, malware cleanup,
hosting issues, hardware failures, software malfunctions, and data loss.

Backups should include website files, databases, user data, and configuration data.
A combination of full backups and incremental backups can improve storage efficiency
while keeping restore points current.

If your website generates leads, sales, traffic, or customer trust, regular backups
are not optional. A reliable backup, restore, and recovery workflow lets you roll
back your WordPress site and can save hours of downtime and expensive recovery work.

### Can I activate permalinks on the staging site?

Permalinks are disabled on the staging site after the first cloning process.

Read this guide to activate permalinks on your staging site:
 [Activate Permalinks on the Staging Site](https://wp-staging.com/docs/activate-permalinks-staging-site/)

### I cannot log in to the staging or backup site

If you use a security plugin such as Wordfence, iThemes Security, All In One WP 
Security & Firewall, or a plugin that hides the default WordPress login URL, make
sure you are running the latest version of WP STAGING.

If you still cannot log in, go to WP STAGING > Settings and disable WP STAGING extra
authentication. Your admin dashboard will still remain protected.

### Can I just use my local WordPress development system for testing and backup?

You can always test your website locally, but if your local hardware and software
environment is not an exact clone of your production server, there is no guarantee
that every aspect of your local copy will behave the same way.

Differences in PHP version, server stack, memory, CPU performance, and filesystem
behavior can all lead to unexpected results on production. That is why staging on
infrastructure close to production remains valuable.

[WP STAGING | PRO](https://wp-staging.com/backup-wordpress) also gives you a more
advanced local workflow through [WP STAGING CLI](https://wp-staging.com/cli/upgrade),
which can turn a backup into a local Docker-based development site.

### Is WP STAGING available in multiple languages?

Yes. WP STAGING is available in multiple languages, and several translations are
already complete or nearly complete.

You can view translated plugin pages here:

[English](https://wordpress.org/plugins/wp-staging/)
 [French](https://fr.wordpress.org/plugins/wp-staging/)
[German](https://de.wordpress.org/plugins/wp-staging/) [Spanish](https://es.wordpress.org/plugins/wp-staging/)
[Croatian](https://hr.wordpress.org/plugins/wp-staging/) [Dutch](https://nl.wordpress.org/plugins/wp-staging/)
[Finnish](https://fi.wordpress.org/plugins/wp-staging/) [Greek](https://el.wordpress.org/plugins/wp-staging/)
[Hungarian](https://hu.wordpress.org/plugins/wp-staging/) [Indonesian](https://id.wordpress.org/plugins/wp-staging/)
[Italian](https://it.wordpress.org/plugins/wp-staging/) [Persian](https://fa.wordpress.org/plugins/wp-staging/)
[Polish](https://pl.wordpress.org/plugins/wp-staging/) [Portuguese (Brazil)](https://br.wordpress.org/plugins/wp-staging/)
[Russian](https://ru.wordpress.org/plugins/wp-staging/) [Turkish](https://tr.wordpress.org/plugins/wp-staging/)
[Vietnamese](https://vi.wordpress.org/plugins/wp-staging/)

If you want to help improve translations, please get in touch with us through the
support forum.

### Can I give feedback for WP STAGING?

Yes. If something does not work as expected, please open a support request and describe
the issue in as much detail as possible.

We continuously improve WP STAGING based on user feedback, real-world hosting environments,
and developer use cases.

Open support:
 [WP STAGING Support Forum](https://wordpress.org/support/plugin/wp-staging/)

## Отзывы

![](https://secure.gravatar.com/avatar/68e1ccf061561e528c8a7ca474287a669cc10910a559a065decbe46dd9ac1b24?
s=60&d=retro&r=g)

### 󠀁[Hace lo que dice, sencillo y práctico](https://wordpress.org/support/topic/hace-lo-que-dice-sencillo-y-practico/)󠁿

 [Tio Tom](https://profiles.wordpress.org/treswdoble/) 09.10.2026

Es un plugin excelente de sencilla manejo, es un excelente servicio para los que
tienen un hosting que no dispone del servicio de staging, crea un clon 100% operativo
y la opcion de backup funciona a la perfección. Buen plugin

![](https://secure.gravatar.com/avatar/b900c36f648b10c83c24bda2efed3abe6559fde5ddc3f71c0aba16c92b443370?
s=60&d=retro&r=g)

### 󠀁[Super Plugin](https://wordpress.org/support/topic/super-plugin-1399/)󠁿

 [katzenfluestern](https://profiles.wordpress.org/katzenfluestern/) 07.10.2026

Super Plugin. DANKE.

![](https://secure.gravatar.com/avatar/bf76f31349ce8f4a4661c87e69c5845e1e7251ea7df7c2421ae4f85d3cc4174a?
s=60&d=retro&r=g)

### 󠀁[Awesome plugin](https://wordpress.org/support/topic/awesome-plugin-7530/)󠁿

 [Filippo Tinnirello](https://profiles.wordpress.org/tinnydev/) 15.09.2026

A delightful plugin, a life saver when updating wordpress core, themes, plugins.
You can do much with the free version, but the pro version is the non plus ultra.

![](https://secure.gravatar.com/avatar/7d1098df8e01e0b616fb143d62c412aeb4eca7acf4172b30f6e868a9cf1b7632?
s=60&d=retro&r=g)

### 󠀁[Fantastic Support](https://wordpress.org/support/topic/fantastic-support-635/)󠁿

 [auteur](https://profiles.wordpress.org/auteur/) 09.09.2026

I'm on the PRO version. This plugin has made my life easier. No more migrating databases.
BONUS was the fast support response for an emergency (GOING LIVE NOW) moment. The
error was on my side but they were very fast, responsive and helpful. When you have
a ton of balls in the air at one time, it's nice to have support like this available.

![](https://secure.gravatar.com/avatar/9f53b48fde4bccae19979fa16cf8f13bebf30ca64f44c077a4959a62e6a19b4e?
s=60&d=retro&r=g)

### 󠀁[Great Tool, Great Support](https://wordpress.org/support/topic/great-tool-great-support-48/)󠁿

 [Ray](https://profiles.wordpress.org/raywebde/) 28.08.2026

Really great tool for staging, backup and developing. The desktop client helps a
lot to develop on local machine and bring it to the live server. Support fast, friendly
and always with detailed informations. Would recommend it.

![](https://secure.gravatar.com/avatar/ae11b5b0e8e831442acb96cfcc4b9855a287835ba065c9bce4557ccee15c4856?
s=60&d=retro&r=g)

### 󠀁[Wonderfully simple, yet complex](https://wordpress.org/support/topic/wonderfully-simple-yet-complex/)󠁿

 [lilaeule](https://profiles.wordpress.org/lilaeule/) 20.08.2026

Offers everything you need. Clear. Easy to understand. Helpful. Unobtrusive. Multi-
layered.

 [ Посмотреть все 2 468 отзывов ](https://wordpress.org/support/plugin/wp-staging/reviews/)

## Участники и разработчики

«WP STAGING — Backups & Restore, Migration & Clone Plugin — Cloud Backups, Scheduled
Backups» — проект с открытым исходным кодом. В развитие плагина внесли свой вклад
следующие участники:

Участники

 *   [ Rene Hermenau ](https://profiles.wordpress.org/renehermi/)
 *   [ WP STAGING ](https://profiles.wordpress.org/wp-staging/)
 *   [ WP STAGING | BACKUP ](https://profiles.wordpress.org/wpstagingbackup/)
 *   [ lucatume ](https://profiles.wordpress.org/lucatume/)
 *   [ lucasbustamante ](https://profiles.wordpress.org/lucasbustamante/)
 *   [ alaasalama ](https://profiles.wordpress.org/alaasalama/)
 *   [ fayyazfayzi ](https://profiles.wordpress.org/fayyazfayzi/)

«WP STAGING — Backups & Restore, Migration & Clone Plugin — Cloud Backups, Scheduled
Backups» переведён на 11 языков. Благодарим [переводчиков](https://translate.wordpress.org/projects/wp-plugins/wp-staging/contributors)
за их работу.

[Перевести «WP STAGING — Backups & Restore, Migration & Clone Plugin — Cloud Backups, Scheduled Backups» на ваш язык.](https://translate.wordpress.org/projects/wp-plugins/wp-staging)

### Заинтересованы в разработке?

[Посмотрите код](https://plugins.trac.wordpress.org/browser/wp-staging/), проверьте
[SVN репозиторий](https://plugins.svn.wordpress.org/wp-staging/), или подпишитесь
на [журнал разработки](https://plugins.trac.wordpress.org/log/wp-staging/) по [RSS](https://plugins.trac.wordpress.org/log/wp-staging/?limit=100&mode=stop_on_copy&format=rss).

## Журнал изменений

#### 4.17.0

 * New: Add secure transfer sessions for backup downloads. Backups are no longer
   offered as permanent public URLs. Instead Download Backup and Share Backup Link
   create a short-lived, tokenized transfer link on click that the webserver serves
   statically, so PHP never streams the backup and large downloads can not run into
   PHP timeouts. #5449
 * New: Protect the permanent backup directory against direct HTTP access on Apache
   and IIS, and add a backup folder security self-test with a small, expandable 
   notice that says what to ask the hosting provider when the folder is still reachable.#
   5449
 * Enh: Advertise the Pro auto login feature below the button that opens a new staging
   site in the free version. #6360
 * Enh: Ask OneDrive for a whole page of entries when listing backups, instead of
   leaving Microsoft Graph on its default of 200 per request. (Pro) #5913
 * Enh: Limit «Create Blank WP Site» to the Business plan and above. (Pro) #6725
 * Enh: Show the ten newest remote backups first and keep the rest behind a «Show
   more» button, so a large remote backup folder does not slow the backup list down.(
   Pro) #5913
 * Fix: A backup no longer fails when a theme, plugin or media file has a modification
   date before 1970 or after 2106. #6582
 * Fix: A second cancellation that starts while one is still running now waits for
   it instead of stopping it silently. #6623
 * Fix: Background jobs could fail to find their queue table on sites that use SQLite.#
   6756
 * Fix: Clone the subsite that source-blog-id names in the WP-CLI staging-site-create
   command instead of the current blog. (Pro) #6268
 * Fix: Correct the .htaccess rewrite base for multisite network clones. (Pro) #
   6137
 * Fix: Delete the Remote Sync settings when WP Staging Pro is uninstalled. (Pro)#
   6764
 * Fix: Finish deleting a split backup once every part was deleted, instead of ending
   the request without a reply. (Pro) #6784
 * Fix: Finish the remote backup list when one of several storages answers with 
   an error, instead of leaving the loading indicator running and the «No remote
   Backups found» message out of date. (Pro) #5913
 * Fix: Hash the whole backup once instead of twice when a remote upload checks 
   a file already on the remote storage. (Pro) #6498
 * Fix: Include Remote Sync logs and timestamps in bundled downloads. (Pro) #6640
 * Fix: Keep bundled log downloads inside the 14-day retention window instead of
   including logs of any age. #6713
 * Fix: Keep every job log entry on one line, so a line break in an error message
   can no longer forge log entries. #6758
 * Fix: Keep passwords out of corrupted staging sites reports and remove temporary
   report files. #6131
 * Fix: Keep storage access tokens out of the request error that reaches the job
   log and the debug log. (Pro) #6631
 * Fix: Keep the live site’s database prefix while listing a push’s tables, so the
   rest of that request no longer reads or writes the staging site’s tables. (Pro)#
   6772
 * Fix: Keep the run day and the missed-run record of a backup plan when only its
   retention is changed. (Pro) #6479
 * Fix: Keep the staging creation screen open after pressing Stop instead of reporting
   the job as cancelled from another page or opening a status error popup. #6455
 * Fix: Let the Delete wpstg-restore.php button remove the restore tool without 
   a Developer or Agency license. (Pro) #6706
 * Fix: Make wp wpstg status report running, finished and failed jobs correctly.(
   Pro) #6787
 * Fix: Name the failed backup in upload failure reports. (Pro) #6551
 * Fix: Offer the staging site’s login page instead of a session-expired error when
   the license is not active. (Pro) #6708
 * Fix: Open the backup explorer on backups with many files instead of failing with
   an HTTP 500 memory error. #6667
 * Fix: Post every failed scheduled backup upload to Slack, a repeated one at most
   once per hour, and send Slack error reports even with error emails off. (Pro)#
   6551
 * Fix: Preserve clone settings when continuing past the database grant warning.(
   Pro) #6712
 * Fix: Preserve production wpstg_queue and wpstg_settings during Legacy Push. (
   Pro) #6693
 * Fix: Purge the LiteSpeed page cache after a restore, also when the restore replaced
   or deactivated the LiteSpeed Cache plugin. #6779
 * Fix: Read every page of the backup listing on Google Drive, OneDrive and the 
   S3 storages, so the backup list and retention see every stored backup. (Pro) #
   5913
 * Fix: Reading and checking plugin settings could hang or come back empty on sites
   that use SQLite. #6751
 * Fix: Refuse a subsite backup whose blog ID names no subsite of the current network,
   or names one that is archived, suspended or deleted. #6403
 * Fix: Remote Sync push no longer logs a setTmpDatabasePrefix() TypeError on every
   queue tick. (Pro) #6773
 * Fix: Repair a missing queue column when the stored schema version is current.#
   6693
 * Fix: Report a backup file that reached the server’s file size limit as such, 
   with what to do about it, instead of as a full disk. #6862
 * Fix: Retry a scheduled backup report email that could not be sent. #6551
 * Fix: Retry opening the Google Drive upload session after a network error instead
   of cancelling the upload. (Pro) #6681
 * Fix: Run the optimizer preflight with the current mu-plugin and retry unverified
   checks. #5659
 * Fix: Send identical backup report emails at most once per hour. #6551
 * Fix: Show an Activate License button in the Pro header when the site is not activated
   on its license. (Pro) #6707
 * Fix: Show why Run Now could not start a backup plan, and mark the plan’s last
   run as failed when its subsite backup is refused. #6403
 * Fix: Skip hashing the whole backup when a remote upload finds the remote copy
   at a different size. (Pro) #6823
 * Fix: Stop PHP 8.4 deprecation notice in the search & replace step of staging 
   site cloning and pushing. #5623
 * Fix: Stop a killed backup request from adding the same files twice, which threw
   finished backups away at the file-count check. #6578
 * Fix: Stop a remote backup upload when a wrong-sized file of the same name cannot
   be deleted first, and retry a pCloud deletion that timed out. (Pro) #6496
 * Fix: Stop a retried Next-Gen push, or staging site creation, update or reset,
   from replaying database rows and failing with a duplicate PRIMARY key. #6577
 * Fix: Stop a second «Success» dialog from covering the next dialog opened after
   creating a staging site. #6664
 * Fix: Stop duplicate PHP time-limit warnings for successful scheduled backups.#
   6551
 * Fix: Stop expired temporary-login records from logging out an existing administrator
   who signed in with their password. (Pro) #6840
 * Fix: Stop reporting a backup as failed when its status check fails right after
   pressing Stop. #6455
 * Fix: Stop the backup of a subsite from silently backing up the current blog when
   the blog ID cannot be resolved. #6403
 * Fix: Stop two simultaneous FTP / SFTP profile saves from both claiming the same
   folder. (Pro) #6559
 * Fix: The Upload Backup to Cloud and Create Backup modals no longer reopen by 
   themselves on a later visit to Backups after connecting Google Drive with your
   own API credentials. (Pro) #6139
 * Fix: Warn when a backup listing could not be read in full on Google Drive, OneDrive,
   Dropbox or any of the S3 storages, instead of showing a short list as the whole
   folder. (Pro) #5913
 * Fix: Write database passwords, users and names containing an apostrophe, double
   quote or backslash correctly to wp-config.php in the standalone restore tool.(
   Pro) #6794
 * Dev: Add the Pro 6.16.0 features to the Free vs Pro comparison. #6716
 * Dev: Check the backup cancel and error modals themselves instead of the whole
   page, which now quotes the cancel modal title in the newsfeed. #6715
 * Dev: Confirm each dummy backup in the cloud storage integration tests through
   the listing, and upload it again when a transient network error lost it. #6624
 * Dev: Delete the OneDrive integration test folder after each run instead of leaving
   it in the shared account. #6682
 * Dev: Document which existing backup, Remote Sync and CLI parts the planned hosted
   deploy service can reuse. #6744
 * Dev: Drop the second approval and let two clean role reviews make a pull request
   ready to merge. #6736
 * Dev: Expect a backup cancel to end as cancelled when a status check fails during
   it. #6728
 * Dev: Find a fix already in flight under another issue before an agent works on
   one. #6800
 * Dev: Hand the dismissal of a changes-requested review to the author or the project
   owner, since agents are denied it. #6759
 * Dev: Keep the live license check out of the Remote Sync pull database spec. #
   6711
 * Dev: Let a worktree run a Playwright spec that reads the database. #6368
 * Dev: Let agents post review thread replies through `dev/ci-watch.sh reply`. #
   6748
 * Dev: Let the lifecycle controller accept a Codex review in place of Copilot’s.#
   6868
 * Dev: Let the lifecycle controller act on pull requests whose mergeability is 
   still being computed. #6798
 * Dev: Lower the CPU each E2E test spends on screen recording and looping animations.#
   6695
 * Dev: Make the WP-CLI staging-site polling example stop when the job finishes 
   or fails. #6785
 * Dev: Make the fatal-error guard detect fatals in hidden markup. #6505
 * Dev: Record migration as a Pro-only feature in the licence feature matrix. #6788
 * Dev: Resume an issue with make worktree from its branch on origin instead of 
   starting a second branch from master. #6803
 * Dev: Retry WordPress plugin and theme downloads during site setup. #5303
 * Dev: Run the release pipeline on the branch it was dispatched on instead of one
   named after the current month. #6692
 * Dev: Search for an existing issue before an agent opens a new one. #6503
 * Dev: Settle a pull request in one review round: a push after a role review no
   longer asks its reviewer again. #6657
 * Dev: Shard Pro Single Staging and Pro Single Backup in the release suite’s PHP
   7.4 gate. #6698
 * Dev: Start the full PHP matrix from the lifecycle controller once the review 
   is settled. #6739
 * Dev: Start the lifecycle controller after a role review is posted, so the review-
   role labels come off at once. #6832
 * Dev: Stop StagingSiteHttpDetectorTest failing with 301 instead of 300 when a 
   second passes between scheduling two staging sites. #6762
 * Dev: Stop the lifecycle controller from holding back a pull request that is only
   behind master. #6790
 * Dev: Tell the lifecycle controller when a Fast tests or E2E run it started has
   finished, instead of waiting for its two-hourly sweep. #6814
 * Dev: Turn off wp-browser’s temporary-table rewrite in four unit test classes 
   that need real tables. #6763
 * Dev: Write owner decision requests on pull requests in product terms, without
   code names. #6804

WP STAGING Backup & Cloning | Full changelog:
 [https://wp-staging.com/wp-staging-changelog](https://wp-staging.com/wp-staging-changelog)

## Коммерческий плагин

Этот плагин бесплатный, но предлагает дополнительные платные коммерческие улучшения
или поддержку. [Посмотреть поддержку](https://wordpress.org/support/plugin/wp-staging/)

## Мета

 *  Версия **4.17.0**
 *  Обновление: **4 дня назад**
 *  Активных установок: **100 000+**
 *  Версия WordPress ** 3.6 или выше **
 *  Совместим вплоть до: **7.1.3**
 *  Версия PHP ** 7.0 или выше **
 *  Языки
 * [Dutch](https://nl.wordpress.org/plugins/wp-staging/), [English (US)](https://wordpress.org/plugins/wp-staging/),
   [French (France)](https://fr.wordpress.org/plugins/wp-staging/), [Galician](https://gl.wordpress.org/plugins/wp-staging/),
   [German](https://de.wordpress.org/plugins/wp-staging/), [German (Austria)](https://de-at.wordpress.org/plugins/wp-staging/),
   [German (Switzerland)](https://de-ch.wordpress.org/plugins/wp-staging/), [Persian](https://fa.wordpress.org/plugins/wp-staging/),
   [Serbian](https://sr.wordpress.org/plugins/wp-staging/), [Spanish (Spain)](https://es.wordpress.org/plugins/wp-staging/),
   [Spanish (Venezuela)](https://ve.wordpress.org/plugins/wp-staging/) и [Vietnamese](https://vi.wordpress.org/plugins/wp-staging/).
 *  [Перевести на ваш язык](https://translate.wordpress.org/projects/wp-plugins/wp-staging)
 * Метки:
 * [backup](https://ru.wordpress.org/plugins/tags/backup/)[move](https://ru.wordpress.org/plugins/tags/move/)
   [restore](https://ru.wordpress.org/plugins/tags/restore/)[transfer](https://ru.wordpress.org/plugins/tags/transfer/)
   [wordpress backup](https://ru.wordpress.org/plugins/tags/wordpress-backup/)
 *  [Дополнительно](https://ru.wordpress.org/plugins/wp-staging/advanced/)

## Оценки

 4.8 из 5 звёзд.

 *  [  2 315 5-звездный отзыв     ](https://wordpress.org/support/plugin/wp-staging/reviews/?filter=5)
 *  [  66 4-звездный отзыв     ](https://wordpress.org/support/plugin/wp-staging/reviews/?filter=4)
 *  [  13 3-звездный отзыв     ](https://wordpress.org/support/plugin/wp-staging/reviews/?filter=3)
 *  [  8 2-звездный отзыв     ](https://wordpress.org/support/plugin/wp-staging/reviews/?filter=2)
 *  [  66 1-звездный отзыв     ](https://wordpress.org/support/plugin/wp-staging/reviews/?filter=1)

[Ваш отзыв](https://wordpress.org/support/plugin/wp-staging/reviews/#new-post)

[Посмотреть всеотзывы](https://wordpress.org/support/plugin/wp-staging/reviews/)

## Участники

 *   [ Rene Hermenau ](https://profiles.wordpress.org/renehermi/)
 *   [ WP STAGING ](https://profiles.wordpress.org/wp-staging/)
 *   [ WP STAGING | BACKUP ](https://profiles.wordpress.org/wpstagingbackup/)
 *   [ lucatume ](https://profiles.wordpress.org/lucatume/)
 *   [ lucasbustamante ](https://profiles.wordpress.org/lucasbustamante/)
 *   [ alaasalama ](https://profiles.wordpress.org/alaasalama/)
 *   [ fayyazfayzi ](https://profiles.wordpress.org/fayyazfayzi/)

## Поддержка

Решено проблем за последние 2 месяца:

     26 из 26

 [Перейти в форум поддержки](https://wordpress.org/support/plugin/wp-staging/)

## Пожертвование

Хотите поддержать улучшение этого плагина?

 [ Пожертвовать на развитие плагина ](https://wp-staging.com/backup-wordpress)