Edara Backup

Restoring from backup

A restore brings back data from an available earlier recovery point. Businesses may need it after accidental deletion, an incorrect update, or damage to working data.

1. 1

   Request the right recovery point

   Tell Edara which files or system are affected, when the problem started, and when the data was last correct. Ask which successful recovery points are available within retention. For example, a file deleted on Tuesday may be recovered from Monday's copy if it exists and is still retained.

2. 2

   Confirm what will be replaced

   Restoring an older version can replace newer valid changes. Agree the destination, whether existing data will be overwritten, and who can approve the operation. After recovery, check important files and business functions before considering the work complete. A backup's existence alone does not prove a particular restore will succeed.

3. 3

   Standard and priority restores

   Backup 100 includes one standard restore per month and Backup 500 includes two. Backup 1 TB lists priority restore handling; that label does not specify unlimited requests. Confirm its allowance with Edara. Standard describes the normal handling queue; priority affects handling order, not a guaranteed completion time. Ask about scope and cost if you need requests beyond your allowance.

4. 4

   How long will it take?

   Time depends on the amount of data, the requested scope, access, and checks needed afterward. Restore time is not guaranteed unless explicitly covered by an SLA in your agreement. Explain business urgency when you request help, and confirm whether a complex recovery needs separately scoped work.