Restoring Databases or Applications: Key Considerations

Key considerations for successfully restoring databases or applications include the following.

Additional steps may be required

Successfully restoring some databases or applications requires that you perform preliminary steps, then restore your data through MyLiveVault, and then follow up with some additional steps.

If you are restoring one of the following applications, see the related help topic for information specific to restoring that application:

Iterative restores may be required

You can restore either the most current version that has been backed up or a historic version. The currency of the "most current version" depends on the backup schedule for your associated database/application backup configuration. However, in a data corruption event, the most current backed up version may be corrupted. This is dependent on when the corruption occurred and whether the corrupted data has already been backed up. You may need to perform several restores, current then historic, until you restore a version from before the corruption occurred.

Suspending backup if restoring over the Internet

If you are restoring a database or application due to corruption and are planning to restore the data over the Internet, you may choose to suspend backup of the computer whose data you are restoring for the duration of the restore. Suspending backup can make the process of restoring the database/application data easier in the event you need to perform iterative restores due to corruption.

Important: Suspending backup means that all backup is suspended until you resume it. If this is an issue for you, please contact Customer Service for assistance.

If you choose to suspend backup during the restore, you must remember to resume backup after completing the restore.

Modified file dates and data currency

When selecting files to restore, the Files to Restore tab on the Computer Restore page displays each files size and modified date.

The modified date reflects when the file was last closed. This may not necessarily reflect the last time you modified the file (or the "modified" date you see on for the file on the Agent computer itself) nor the currency of the backed up version. For example, some database files will remain open for long periods of time (for example, weeks) yet during that time transactions have been committed to the database and LiveVault Online Backup Service has backed up those transactions and has at least one good historic copy each day. In addition some applications will keep files open on the Agent and as a result the modified date in MyLiveVault will not reflect the actual last modified date you may expect.

When you specify the version of the data to restore (either current or a historic version), the tree view in the Files to Restore tab will display the data that was backed up as of the selected time and date, and you will restore the latest version of each selected file and directory that was stored in the backup server as of this time and date as you requested.

Related Information

Restoring Files and Directories, or Databases
Restoring Your Data: An Overview