Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

SQL Safe includes the following failure scenarios that may occur during an instant restore.

ComponentFailureResolution
ServerCrashesIf the server suffers a catastrophic crash and is no longer available, no recovery is available.
ServerRebootsIf 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.
ServerRuns out of resourcesIf 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:
  1. If the offending process is identified:
    1. The user must stop the process.
    2. The user can manually restart the SQL Safe Filter Service (if stopped).
    3. If hydration does not resume once the SQL Safe Filter Service restarts, the user can manually restart the operation.
  2. If the offending process is not identified, the user may reboot the server.
ServerSuffers a disk failureIf the database or InstantRestore support files is corrupted by a disk failure, no recovery is available.
ServiceRestartsIf one or all of the following items restarts, hydration should resume after the restart is complete:
  • SQL Server
  • SQL Safe Backup Agent
  • SQL Safe Filter Service

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 ServiceCrashes

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 fileIs 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 fileIs inaccessible due to a network failureIf 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 fileIs inaccessible due to a lack of access permissionsIf 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?

...

You can also perform an instant restore through the CLI. Additional options can be set in the SQL Safe Restore wizard, from which you can generate a CLI script that includes the specified wizard settings.

...

SQLsafeCmd.exe InstantRestore <database> <full_backup> -diff <diff_backup> -log <log_

...

backup> 

The following three options are specific to a backup set:

  • BackupFile   (if the backup set is striped).
  • BackupSet.
  • Password   (or or EncryptedRestorePassword).

Where these options appear in the command determines to which backup set they are applied. When you encounter one of these options, it is applied to the full if no -Diff/-Log option is yet encountered, otherwise it is applied to the most recent -Diff/-Log. For example, if you want to instantly restore the following backups:

  • Full backup, 2 stripes, backupset 2, encryption key "full".
  • Diff backup, 2 stripes, backupset 3, encryption key "diff".
  • Log backup, 2 stripes, backupset 4, encryption key "log".

Use the command:

SQL SafeCmd SQLsafeCmd InstantRestore Northwind "C:\Backup\Northwind_Full (1 of 2).safe" -BackupFile "C:\Backup\Northwind_Full (2 of 2).safe" -BackupSet 2 -Password "full" -Diff "C:\Backup\Northwind_Diff (1 of 2).safe" -BackupFile "C:\Backup\Northwind_Diff (2 of 2).safe" -BackupSet 3 -Password "diff" -Log "C:\Backup\Northwind_Log (1 of 2).safe" -BackupFile "C:\Backup\Northwind_Log (2 of 2).safe" -BackupSet 4 -Password "log"

For more information about available available instant restore options, see the usage statements in the CLI Help. To view the CLI Help, type SQLsafeCmd help instantrestore.



Legal
Scroll pdf ignore
Newtabfooter
aliasIDERA
urlhttp://www.idera.com
 | 
Newtabfooter
aliasProducts
urlhttps://www.idera.com/productssolutions/sqlserver
 
Newtabfooter
aliasPurchase
urlhttps://www.idera.com/buynow/onlinestore
 | 
Newtabfooter
aliasSupport
urlhttps://idera.secure.force.com/
 | 
Newtabfooter
aliasCommunity
urlhttp://community.idera.com
 
|
 
Newtabfooter
aliasResources
urlhttp://www.idera.com/resourcecentral
 | 
Newtabfooter
aliasAbout Us
urlhttp://www.idera.com/about/aboutus
 
Newtabfooter
aliasLegal
urlhttps://www.idera.com/legal/termsofuse
SQL Safe is a high-performance backup and recovery solution for your SQL Servers. Learn more > >
IDERA WebsiteProductsPurchaseSupportCommunityAbout UsResources