The backup is ready.
Can work resume?
A successful backup confirms that a job ran. A recovery test answers a different question: can you use that backup to run the service and complete an important task? Plan a test that protects live data.
At a glance
- Test data, configuration and application dependencies.
- Measure restoration of operations, not just downloading a file.
- Record results, limitations and necessary fixes.
What exactly are you restoring?
Choose a process, such as accepting an order, reading a document or using an application. Record the backup version and everything needed to run it: files, database, configuration, licences and dependencies. For each component, identify an owner and a task that will verify its operation. Before testing, check that the backup covers these components and that the restored data will be consistent.
Agree how much recent data the business can afford to lose and how long work may stop. These requirements come from operations. Do not choose them solely because a backup schedule is already configured.
Prepare a safe test environment.
Restore into an agreed environment without overwriting production. Restrict access to restored data. Before starting, disable email delivery, payments and jobs that could affect customers. A test copy should not accidentally become a second live shop.
Plesk documents backup creation and restoration separately. Check the selected operation’s scope and its effect on existing data. If the test requires personal data, apply suitable safeguards and remove the test copy according to the agreed process.
Test the task that matters to operations.
Illustrative example: the restored system displays a sign-in screen but cannot generate a document because a template is missing. The server is running, yet the process has not been restored. Testing sign-in, data access and document generation reveals the actual state.
- Compare selected records and files with the expected backup state.
- Complete the agreed business task without affecting production.
- Record the time from starting the test to confirmed operation.
What belongs in the test record?
In the test record, include the backup identifier, environment and operator. For each check, record the expected result, actual result and evidence. List a missing template or an untested integration as an open matter with an owner and a next step. If the test covered only sign-in and document generation, its result applies to those tasks. Other processes need their own checks.
Assign an action and a verification method to each gap. Choose the next test based on risk and environment changes. One test does not guarantee recovery from every future failure; it provides evidence for the scenario tested.
Sources and next step
These sources describe mechanisms and good practices. They do not confirm your company’s configuration or compliance. The examples in this guide are illustrative.
To apply these questions to your business, explore the related service. A description of your situation is enough for an initial discussion; do not send passwords or confidential data through the form.
Explore our managed hosting services