Page History
...
SQL Safe includes the following failure scenarios that may occur during an instant restore.
Component | Failure | Resolution |
---|---|---|
Server | Crashes | If the server suffers a catastrophic crash and is no longer available, no recovery is available. |
Server | Reboots | If the server reboots because of a power failure, automatic software update, or other similar situation, and comes back online correctly, the SQL Safe Filter Service restarts and then resumes hydration. |
Server | Runs out of resources | If the server runs out of memory or other resources, and the SQL Safe Filter Service cannot allocate the additional resources during hydration, SQL Safe uses the following steps:
|
Server | Suffers a disk failure | If the database or InstantRestore support files is corrupted by a disk failure, no recovery is available. |
Service | Restarts | If one or all of the following items restarts, hydration should resume after the restart is complete:
If the database did not go into Suspect mode during this process, hydration resumes from the point where it left off when the SQL Safe Filter Service restarted. If the database is in Suspect mode, the SQL Safe Filter Service brings the database out of Suspect mode, and then resumes hydration. |
Filter Service | Crashes | If the SQL Safe Filter Service crashes, hydration resumes once the service restarts. If the SQL Safe Filter Service crashes again, you may need to recover any new data added since the first crash. |
Backup file | Is corrupt | If the backup file is corrupt or there is a read problem when accessing the network, the SQL Safe Filter Service fails to decompress during hydration. If the backup file is corrupt, and you have another copy of the backup file, you can restart hydration using the non-corrupt backup file. If the issue is a read problem when accessing the network, you can restart hydration once you address the network issue. |
Backup file | Is inaccessible due to a network failure | If the backup file is inaccessible due to a network failure, InstantRestore attempts a retry. If the retry fails, and the maximum retry attempts is reached, the Hydration operation status transitions to the Failure state. Once you correct the network issue or relocate the backup file, you can resume hydration. If the Hydration fails, you may need to restart InstantRestore. |
Backup file | Is inaccessible due to a lack of access permissions | If the SQL Safe Filter Service restarts and is unable to open the backup file because the account attempting to read the file does not have the proper permissions, you must provide the account permission, and then resume hydration. |
Does SQL Safe include new characteristics specific to the InstantRestore feature?
...
For more information about available instant restore options, see the usage statements in the CLI Help. To view the CLI Help, type SQLsafeCmd help instantrestore.