SQL Backup - 7.2
Scheduling restores: select the destination server and backups to restore
Scheduling restores > Select destination server and backups to restore > Select destination database > Specify file locations > Specify verification options > Configure restore options > Create restore schedule > Review summary
This topic describes the Schedule Restore Jobs wizard page for selecting the server to restore on and the backups to restore.
From the Select destination server drop-down list, choose the server on which you want to restore the backups. This does not have to be server on which the backups are stored.
If you have launched the wizard from a reminder, this option is populated with the server on which the backup job was created. If you change to a different server, you must update the path under Folder to refer to the location on the original server.
Restoring from a folder and file name pattern
You can create a scheduled restore job to restore the latest backup of a database each time the job runs. Restore from a folder and file name pattern if either of the following are true:
- a backup of the database does not already exist
- backups will be created with different file names each time the job runs.
This is useful if you have created a scheduled backup job and opted to name the files automatically using tags to include the date and time of creation in the file name.
If you have launched the Schedule Restore Jobs wizard from a reminder, this option is selected by default and the page is populated with details to identify the latest backup created by the scheduled backup job. The job details, including the password, are populated from the backup job stored on the server, and are not copied elsewhere.
Setting up the folder and file name pattern manually
If you have not launched the Schedule Restore Jobs wizard from a reminder, enter the details to identify the latest backup:
- From the Restore from drop-down list select Folder and file name pattern.
- Specify the name of the backed up database in the Source database name box.
- Choose between restoring the latest full backup of the source database (Latest full backup) or the latest set of backups (Latest backup set) of the source database.
If you select Latest backup set, the latest full backup, the latest subsequent differential backup (if available), and all subsequent log backups (if available) will be restored.
- Click Add folder to specify the folders where the backups will be stored. When the restore job runs, SQL Backup will search the specified folders for the latest backup or set of backups of the source database that matches the specified file name pattern.
You can specify more than one folder and file name pattern. This is useful if you store your backups in multiple locations (for example, separate folders for full, differential and log backups) or split backups into multiple files across different folders. SQL Backup will search all specified folders for the latest full backup or set of backups of the source database using the specified file name pattern.
- Under Folder, specify the folder(s) in which the backup file(s) will be stored when the job runs. The default backup location for the destination server is supplied. To edit the path, type or click to open the Folder Browser.
Specify the location in which the backup file(s) will be stored; SQL Backup will not search subfolders of the specified folder. If the folder does not exist yet (for example, because it is due to be created by a scheduled backup job), type the path or create the folder from the Folder Browser.
Local drives refer to the destination server. Use the Folder Browser to view locations on a different server by selecting a different machine from the Server drop-down list. If the server you require is not displayed, click Add Server and enter the server name or IP address. See Specifying file paths for more information.
Note: only servers visible to the destination server are available for browsing. If the server you require cannot be added, ensure the destination server has the appropriate permissions to access it.
- Under File name pattern, specify a file name pattern to search the folder for backups of the source database. By default, the * wildcard character is used to replace the entire file name (
*.sqb). SQL Backup will identify the most recent backup in the folder which matches the source database name.
You can combine fixed text with wildcard characters to limit the search to particular files in the folder; SQL Backup will identify the most recent backup of the source database which matches the specified pattern. This is useful if you store backups for two or more databases of the same name in the same folder. For example:
- (local)_AdventureWorksDW_FULL_*.sqb would match files such as (local)_AdventureWorksDW_FULL_20120229.sqb but not TESTSERVER_AdventureWorksDW_FULL_20120228.sqb
- *Database1_ 201201*.sqb would match files such as FULL_Database1_ 20120125.sqb and DIFF_Database1_ 20120127.sqb
You may find it helpful to set the default backup folder and file name format for the server (see File management options) and select Name file automatically when you create scheduled backup jobs using the Schedule Backup Jobs wizard.
You must supply the password for any backups that will be encrypted. If you have selected Latest backup set, the same password will be applied to all encrypted backups. Any backups in the set which are not encrypted will also be included in the restore job.
Restoring from specific backup files
You can schedule a restore job for specific backup files which already exist. The file of that exact name will be restored every time the job runs. You may wish to select this option if you always back up to the same file name, for example TestDB_FullBackup.sqb, and store the file in the same location.
- From the Restore from drop-down list, select Specific backup files.
- Click Add files to display the File Browser. The backup files in the destination server's default backup location are displayed.
To view files on a different server, select a different machine from the Server drop-down list. If the server you require is not displayed, click Add Server and type the name or IP address of the server you want to add.
Note that only servers visible to the destination server are available for browsing. If the server you require cannot be added, ensure the destination server has the appropriate permissions to access it.
- You can restore only one database at a time; you can select either one full backup or a full backup, a subsequent differential backup and/or subsequent transaction log backups of the same database. If a backup is split into multiple files, you must select all the files which form the backup.
Note that it is not possible to restore a differential backup or transaction log backup without a corresponding full backup.
- If there is a problem with a backup file, is displayed. Move your mouse pointer over the icon to see details of the error.
is displayed next to encrypted backups. Type the password into Password and click Decrypt. is displayed next to all backups to which the password applies. The selected backups must be decrypted before you can move on to the next step of the wizard.
Was this article helpful?
Thanks for your feedback!
- Backups stop working when the SQL account passwords are changed
- Backups and restores taking longer each time they run
- Improving performance by leveraging multi-processor hardware
- Checking the status of a backup or restore
- SQL Backup Agent doesn't start on named instance
- No backup files are erased when the verify option is also used
- Log shipping initialisation failing with error 3176
- Installing SQL Backup unattended
- Issues faced when upgrading an MSCS cluster server
- Cannot schedule log shipping on case-sensitive servers
- Activation fails because response does not match registration properties
- SQL error -1 on backup with 64-bit
- Could not find procedure 'master...sqbutility'
- 'Does not exist' error manually creating a generic service resource
- Backing up log shipping standby databases
- Stopping a backup or restore whilst in progress
- Backing up full-text catalogs using SQL Backup
- Cannot resolve collation conflict
- Microsoft cluster installation (version 4)
- Informing the SQL Agent of job failures
- Database log files may continue to grow even though transaction logs are backed up
- Cannot load xp_sqlbackup.dll
- Minimum Windows Rights Required for SQL Backup Agent
- Bringing a log shipping standby database online
- Console does not support editing the command you selected
- Malformed database disk image error
- Cannot use a local account to run SQL Backup Agent on cluster
- Preparing SQL Servers for remote installation
- SQL error 18210 and VDI error 1010
- Log shipping jobs not deleting old .sqb files
- Scheduled backups may not include new databases
- VDI error 1010 due to an abort request
- Cannot save or see backup templates
- Not all databases appear in the log shipping wizard
- No mapping between account names and security IDs was done
- SQL error 3101 (database is in use) during log shipping
- Insufficient quota to complete the requested service
- Configuring SQL Server procedure memory
- Backing up and restoring on SQL Server Express Edition
- Cannot run two database backups at the same time
- Restoring database backups across a local network
- In some situations the last compressed data block fails to be written to disk
- Configuring permissions for the SQL Backup Agent service
- Restoring backups from one server to a second server using the user interface
- Using SQL Backup tags to automate backup file naming
- VDI 1010 Error
- SQL Backup 5 cannot connect to servers running SQL Backup 4.0
- Files are created when NOWRITE or NOCOMPRESSWRITE is used in conjunction with multiple threads
- Cannot backup a database when full-text catalogs are not online
- Moving a full-text catalog on RESTORE
- Preventing backups over the network from timing out
- Deleting backup history manually
- SQL Backup installation from SQL Toolbelt installer only installs the console
- Console taking a long time to start up
- Reporting across multiple servers, login fails for user NT AUTHORITY\ANONYMOUS LOGON
- SQL Backup Agent cannot start due to account lookup error
- IO Error on backup or restore restart-checkpoint file
- Unable to edit SQL Backup Scheduled Jobs via the Jobs Tab in the SQL Backup GUI (version 5)
- VDI error 1000 caused by improperly installed VDI interface
- VDI Error 1000 caused by account lookup failure
- VDI error 1000 caused by insufficient permissions
- Error 193: %1 is not a valid Win32 application.
- Installing SQL Backup on a cluster
- Restoring the SQL Server MASTER database
- VDI Error 1010: Failed to get the configuration from the server because the timeout interval has elapsed
- Changing the default data location used by SQL Backup
- Index was outside the bounds of the array error during registration
- Repairing the SQL Backup server-side data store
- Troubleshooting slow backup and restore tasks
- Completed backup jobs showing "in progress" status (version 5)
- Restore wizard: files incorrectly labeled 'Missing' when browsing for a backup file to restore.
- When creating a backup job using the wizards some of the user databases may not be listed
- How to restore a filegroup
- System error 1453 while backing up (Insufficient quota to complete the requested service)
- SQL Backup VDI 1030: Failed to create VirtualServiceSet component
- Backups fail on named instances on custom ports
- SQL error 3101 (database is in use) during full database restore
- Error acquiring mutex occurring during use
- Transaction log continually growing on disaster recovery database
- Reseeding a disaster recovery database
- SMTP mail options not being saved
- SQL Backup Activation NullReferenceException Error
- Scheduling SQL Backup restore jobs
- SQL Backup Error 880: permission denied in database
- Deleting remote backup files after a specified time period (version 5)
- SQL Backup Unable to Login to Perform Backup or Restore
- Restore operation errors with exitcode 680
- "Failed to initialize local data store" error
- Trouble browsing network shares when backing up or restoring
- System error 32 (The process cannot access the file because it is being used by another process)
- Log backup failing because there is no current database backup
- Error locating server or instance of SQL Server
- How to set up log shipping between machines on different domains
- SQL Backup and CPU affinity
- SQL Backup mirrored backups
- Error trying to run backup job
- "Access to the database file is not allowed" error
- The server principal NT AUTHORITY\SYSTEM is not able to access the database
- Browsing while using SQL Server authentication is disabled on the selected server
- Cannot generate SSPI context message
- Log ship to multiple servers
- File browser does not work for remote servers
- Configuring Log Shipping to two Target Databases
- Previous backups not deleted according to ERASEFILES setting
- SQL Backup Reporting fails after upgrading to Version 6 from Version 5 for Multiple
- VDI error 1010 error on log backup when no backup is available
- SQL Backup failed with exit code: 1010 SQL error code: 3101 [SQLSTATE 42000] (Error 50000). The step failed.
- Log backup for a database failing to get copied to the log shipping share
- Mirrorfile backup jobs producing corrupt files
- Activity monitor showing sqlbackup status as wait type MSQL_XP
- Backup and restore processes using high percentage of CPU resources
- Warning 485: File does not exist encountered during a restore (but the process completes successfully)
- Log Shipping error 130 when moving restored file
- SQL Backup "Warning 110" generated
- Attempting to restore data into a SQL Express database that exceeds limit
- SQL error 3241 when restoring database
- A nonrecoverable I/O error encountered on Backup or restore operation
- SQL error 15404
- General log-in problem: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
- Warning: System error 1450 when Backing up
- Problems with "Auto-Close" option set when backing up
- Warning: System error 64 (The specified network name is no longer available) on backing up across a network
- SQL error 4208 encountered on backing up
- Warning 170: "Log files are not in sequence" - on log shipping (restore) operation
- Warning: System error 121 (The semaphore timeout period has expired)
- Changing your participation in the quality improvement program
- Installing SQL Backup server components unattended
- Changing your participation in the quality improvement program
- Verifying backups of the master database
- Log files
all SQL products
- Compatibility of Red Gate tools in 64-bit environments
- Application has encountered an error and needs to close
- Error message after installing SQL Toolbelt - The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found.
- Changing the temporary directory used by the installer
- Toolbelt Installer "hanging" while "scanning volumes"
- Login failing with "trusted SQL Server connection" error when using RunAs
- Some Red Gate products identified as containing a trojan by Anti-Virus software
- Activation may fail with Unknown Error -1
- Product uses web help although a CHM file is available locally
- Argument exception resulting from missing environment variable
- Check for updates may fail when used through proxies
- 'Unidentified Publisher' error when repairing or uninstalling
- Licensing activates product as standard edition
- Moving Red Gate software products to another machine
- Red Gate tools log locations
- The application UI opening slowly when there is no internet access
- Getting help offline
- Using SQL Backup to back up to a network share
- Manually installing SQL Backup server components on clusters (Windows Server 2003)
- Manually installing SQL Backup server components on clusters (Windows Server 2008)
- Using SQL Backup log shipping to maintain a standby server
- SQL Backup release notes - version 6.xx
- SQL Backup release notes - version 7.xx
- Working with the new features in SQL Backup 6
- Using flexible licensing with SQL Backup Pro and SQL HyperBac
- Using SQL Backup Pro and SQL HyperBac together on the same server
all SQL products
- Red Gate product acknowledgements
- Activating your products
- Activating your products
- Red Gate bundle history
- Check for updates
- Troubleshooting Check for Updates errors
- Current versions
- Deactivating your products
- Installing Red Gate products from the .msi file
- Requesting additional activations
- Serial numbers for bundles
- Reactivating using a different serial number
- Extending your trial
- Finding your serial numbers
- Moving a serial number from one computer to another
- No response received for manual activation
- Licensing and activation resources
- Licensing and activation resources
- Troubleshooting licensing and activation errors
- Licensing and activation FAQs
- Red Gate tools log file locations
- Download old versions of products
- Download product prerequisites & utilities
- Support & upgrades
- Upgrading your software
- Upgrading FAQs