Defining How the Restoration Process Is Performed

When restoring data, you can also do the following:

1. Temporarily suspend websites during restoration.
2. Configure the restoration utility to include more details in backup
   reports.
3. Ignore warnings about backup files corruption or modification.

Suspending Websites

If you are going to restore websites, we recommend that you suspend them
during the restoration by using the -suspend option. This will help
you avoid possible errors in the restored sites that may be caused by
changes done to the site configuration or content during the
restoration.

The suspension is made up to be as short as possible: each site is
suspended only for the time it is being restored: The site is started
automatically as soon as the data are processed.

Defining Level of Restore Verbosity

pleskrestore works in one of the following verbosity modes:

1. Non-verbose mode. Default mode. The minimum level, only general
   errors are displayed, like, for example, syntax errors (no or wrong
   command specified, invalid input parameters), runtime errors and
   unhandled exceptions, and so on.
2. Verbose mode. Restore runs with verbosity level which additionally
   includes deployer errors, information about conflicts (read about
   restore conflicts in the section Conflict Resolution Rules and
   Policies), and so on. Enabled by adding the
   -verbose option to the pleskrestore command.

Ignoring Warnings About Backup Corruption or Modification

When you attempt to restore a backup file by means of the
pleskrestore utility, Plesk checks the file and does not restore it
if any of the following problems are found:

• The file is corrupted.

• The file was modified manually after downloading from the server.

• The file was created on another server.

• The file was created in a Plesk version earlier than 11.5.

  Note: Actually, files created in earlier Plesk versions are not a
  problem. Plesk marks such backups as problematic because they lack
  backup signatures. A bakcup signature, introduced in Plesk 11.5,
  enables Plesk to check backups.

To skip checking and restore a backup disregarding potential problems,
use the -ignore-sign option.

Another way for Plesk administrators to restore backups with problems is
through the Plesk GUI by selecting the corresponding option on the
backup restoration page. Note that customers and resellers are unable to
restore such backups by default. However, you can allow all users to
restore any backups disregarding potential problems. To do this, add the
following lines to the
panel.ini
configuration file:

[pmm]
allowRestoreModifiedDumps = on

To return to the default restrictions, remove these lines or change the
second line to the following:

allowRestoreModifiedDumps = off