SQL Backup - 7.2
Scheduling restores: specify the file locations
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 specifying where the database files are restored to.
Restoring from a folder and file name pattern
If you have selected Restore from folder and file name pattern on step 1, you must specify where the database files are restored to using one of three options:
- All files to default locations
- Data and log files to specified locations
- Individual files to specified locations
If you have launched the Schedule Restore Jobs wizard from a reminder, Individual files to specified locations is selected by default and and the locations are populated with details from the scheduled backup job.
All files to default locations
- If you have selected Overwrite existing database on step 2, the existing database's data and log files will be overwritten. Other files which previously belonged to the database but which are not overwritten will be deleted.
The existing database should use the same paths for the data and log files (either on the same server or a different server) as the source database, otherwise the restore will fail. For example, if the source database's files are stored in C:\Program Files\Microsoft SQL Server\MSSQL\Data, the data and log files of the database being overwritten should also be stored in C:\Program Files\Microsoft SQL Server\MSSQL\Data, whether on the same server or a different server.
- If you have selected Create new database on step 2, the database files will be restored to the locations defined in the backup file.
If the database files of the source database are still in the locations defined in the backup when the job runs, the restore will fail because the files already exist. SQL Backup cannot overwrite the database files because creating a new database does not add WITH REPLACE to the RESTORE command. To avoid this, do one of the following:
- move or rename the source database files before the job runs.
- select Data and log files to specified locations and specify alternative locations (the files will be restored using the file names defined in the backup).
- select Individual files to specified locations to specify a location and file name for each database file.
If the locations defined in the backup do not exist on the destination server when the job runs, the restore will fail. This may happen if you are restoring to a different server and the path defined in the backup does not exist on that server. Select Data and log files to specified locations or Individual files to specified locations to specify locations (either on the destination server or another server).
Data and log files to specified locations
Select Data and log files to specified locations to specify the locations each type of database file is restored to. You can specify a location for data files, log files, filestreams and full text catalogs. The files will be restored to the specified locations using the file names defined in the backup.
- Type the path or click to open the Folder Browser and select a location or make a new folder. The files will be restored to the specified folders using the file names defined in the backup file.
- If the database includes filestreams (SQL Server 2008 and later) or full text catalogs (SQL Server 2005), you can specify the locations that they are restored to.
If the database contains more than one filestream or full text catalog, a subfolder will be created for each one within the specified folder.
If the database includes filestreams or full text catalogs and you do not specify a location, they will be restored to the default locations (see above).
Individual files to specified locations
If you have launched the Schedule Restore Jobs wizard from a reminder, this option is selected by default and populated with the logical names of the database files from the source database. The restore locations are populated using the default file locations for the destination server and file names composed of the source database name, followed by _Verification_, followed by the existing file name, for example AdventureWorksDW_Verification_AdventureWorksLog.ldf.
Select Individual files to specified locations to specify the location and file name that each data and log file will be restored to. You can also specify where filestreams or full text catalogs are restored to. Any files that you do not specify will be restored to the default location (see above).
For each database file:
- Click Add File to specify where a database file will be restored to.
- Under Logical Name, type the logical name of the file.
- Under Restore To, type the location or click to open the File Browser and select the location or create a new folder to restore the file to. You can also rename the file by entering a new file name.
- To specify a location for another file, click Add file.
For information about finding the logical names and other details of database files, see Finding database files.
Restoring from specific backup files
If you have selected Restore from specific backup files on step 1, the details of the database files are populated from the backup.
Database files will be restored to the default SQL Server Data Directory, unless you change the file locations. You can select Original Database Data Directory from the drop-down list, or specify the location by selecting Other (Custom) and clicking to open the Folder Browser or File Browser.
For information about how to specify file names on remote servers, see Specifying file paths.
Note that if you have selected Overwrite an existing database on step 2, any files listed under Filegroups and files will be overwritten; other files that are not shown in the list but which previously belonged to the database being overwritten will be deleted.
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