File search pattern not provided. Using default search pattern of '*.sqb' for folder: <value>

When restoring from a backup or backup set, you can specify a file search pattern to identify the most recent backup in the folder. For example:

RESTORE DATABASE [AdventureWorks] FROM DISK = 'C:\Backups\*AdventureWorks*.sqb' LATEST_ALL

If no file search pattern is specified, the default pattern, *.sqb, is used.

For more information, see The RESTORE command.

Failed to save primary log file: <value>

The primary log file records details of backup and restore operations.

Check that the startup account for the SQL Backup Agent service has rights to create files in the reported directory. Also check that the directory has sufficient free space. By default, the log files will be stored in the following folder on the machine on which the SQL Backup server components are installed:

• %PROGRAMDATA%\Red Gate\SQL Backup\Log\<instance> on Windows Vista, Windows 2008 and later, or 
• %ALLUSERSPROFILE%\ Application Data\Red Gate\SQL Backup\Log\<instance> on Windows XP and Windows 2003.

You can change the location of the log file using the file management options. For more information, see SQL Backup log files.

LOGTO error: Failed to save log file: <value>

This log file, specified by the LOGTO option, records details of backup and restore operations.

Check that the account the SQL Backup Agent service logs on as (the startup account) has rights to create files in the listed directory. Also check that the directory has sufficient free space.

For more information about the LOGTO option, see LOGTO in The BACKUP command.

LOGTO error: Folder does not exist: <value>

The LOGTO option specifies a log file for recording details of backup and restore operations. SQL Backup couldn't create the directory for this log file.

Check that the account the SQL Backup Agent service logs on as (the startup account) has rights to create the directory.

For more information about the LOGTO option, see LOGTO  in The BACKUP command.

LOGTO error: Default log file folder does not exist: <value>. Log file will be saved in folder: <value>.

The LOGTO option specifies a log file for recording details of backup and restore operations. SQL Backup couldn't create the log file in the default directory, but has successfully created the log file in the reported directory.

heck that the account the SQL Backup Agent service logs on as (the startup account) has rights to create files in the default directory.

For more information about the LOGTO option, see LOGTO  in The BACKUP command.

MOVETO error: Failed to move file: <value>

SQL Backup failed to move a file to the specified directory. Check the error message for the cause of the failure.

In most cases, this problem occurs when the account the SQL Backup Agent service logs on as (the startup account) does not have appropriate rights. The startup account must be able to write to the specified directory, and delete the source file.

If this error arises during log shipping, it is often because the MOVETO parameter is not moving files out of the network share. Edit the Log Restore job so that the restored log files are moved to a different folder. You will need to do this via a SQL application such as SQL Server Management Studio. See Configuring log shipping for more information.

MOVETO error: Failed to execute MOVETO command.

SQL Backup failed to move the file as specified by the MOVETO command. Check the error message for the cause of the failure.

MOVETO error: Folder does not exist: <value>

SQL Backup failed to move the file as specified by the MOVETO command, because the specified directory does not exist.

COPYTO error: Destination file already exists. Will not overwrite: <value>

SQL Backup failed to copy the file to the directory specified by the COPYTO command. The file already exists in this directory.

To force the file to be overwritten, specify a FILEOPTIONS parameter that includes the bit-masked value "4". For more information, see FILEOPTIONS in The BACKUP command.

COPYTO error: Unable to copy <source> to <target>

SQL Backup failed to copy the file to the target directory specified by the COPYTO command.

In most cases, this problem occurs when the account the SQL Backup Agent service logs on as (the startup account) does not have appropriate rights. The startup account must be able to write to the target directory. For more information on permissions required by the SQL Backup Agent service, see Permissions.

COPYTO error: Unable to copy <source> to <target>. Error message: <value>

SQL Backup failed to copy the file to the target directory specified by the COPYTO command. Check the error message for the cause of the failure.

COPYTO error: Failed to copy file: <value>

SQL Backup could not process the files to be copied. Check the error message for the cause of the failure.

COPYTO made multiple attempts to copy the file: <value>

SQL Backup made multiple attempts to copy the file specified by the COPYTO command.

The error message shows the number of copy attempts, and the reason why each copy attempt failed.

MAILTO error: SMTP host name not defined.

SQL Backup could not send an email notification because the SMTP host name was not defined.

To specify an SMTP host name for this SQL Server instance, open the SQL Backup GUI and from the Tools menu select Server Options, then open the Email Settings tab. For more information, see Email Settings.

MAILTO error: Failed to send mail.

SQL Backup failed to send an email notification. Check the error message for the cause of the failure.

ERASEFILES error: Failed to delete file: <value>

SQL Backup could not delete the file that was marked for deletion.

ERASEFILES error: Failed to delete file: <value>. Error code: <value>

SQL Backup could not delete the file that was marked for deletion. Check the error message for the cause of the failure.

Failed to delete log file: <value>. Error code: <value>

The log file records details of backup and restore operations.

SQL Backup could not delete the log file that was marked for deletion. Check the error message for the cause of the failure.

Failed to delete backup entries in msdb tables: <value>

SQL Backup could not delete old backup and restore records from the msdb history tables. Check the error message for the cause of the failure.

Failed to delete old entries in local history tables: <value>

SQL Backup could not delete backup and restore records from the local SQL Server Compact database. This may be caused by corruption of the SQL Backup local data store. The local data store is a SQL Server Compact Edition database, which is used to cache backup and restore history.

By default, it is installed in %PROGRAMDATA%\Red Gate\SQL Backup\Data\<instance name>\data.sdf for Windows Server 2008, Windows Server 2008 R2, Windows Vista, and Windows 7, or %ALLUSERSPROFILE%\Application Data\Red Gate\SQL Backup\Data\<instance name>\data.sdf for Windows Server 2003 and Windows XP.

To fix the problem, repair the data.sdf file. For more information, see 'To repair a database' in How to: Maintain a Database on MSDN.

Failed to get database size from server.

While calculating the compression ratio for a database, SQL Backup could not retrieve the current database size from SQL Server. Check the error message for the cause of the failure.

Failed to identify filestream files.

While calculating the current database size, SQL Backup could not retrieve the details of files used to store filestream data. Check the error message for the cause of the failure.

Validation error when processing the list of transaction log backups.

SQL Backup could not process the list of transaction log backups required to restore a database. Check the error message for further details.

If the error message reports that the log files are not in sequence, this may be because the Log Sequence Numbers cannot be read or are missing from the header file. You can manually restore the log files, specifying WITH NORECOVERY or WITH STANDBY, using the extended stored procedure or the command line. See The RESTORE command for more information.

In a log shipping scenario, this error may be due to a large log backup taking a long time to copy to the network share, allowing later (smaller) log files to be copied to the network share before it, and a restore of these attempted. This problem should sort itself out over time. You can avoid the problem by increasing the log restore job interval so that it is at least the transfer time of the largest backup. For more information, see Log shipping.

Another process might be locking this file: <value> (attempt <value>) (<value>)

This is an informational message. The backup file was locked, preventing SQL Backup from updating the file at the first attempt. SQL Backup succeeded in updating the file after further attempts.

Other applications may be accessing backup files. This may cause errors in the future if those applications maintain locks on the backup files.

Failed to update backup history table (BACKUPMEDIAFAMILY).

SQL Backup could not update details of the backup process in the BACKUPMEDIAFAMILY table in the msdb database. Check the error message for the cause of the failure.

Error creating backup file: <value>

SQL Backup could not create the backup file. Check the error message for the cause of the failure.

Multiple attempts were made to create the backup file.

This is an informational message. SQL Backup could not create the backup file at the first attempt, but succeeded after further attempts.

This indicates potential problems with storing backup files at the specified locations.

Multiple attempts were made to restore from the backup file.

This is an informational message. SQL Backup could not restore from the backup file on the first attempt, but succeeded after further attempts.

Error writing to backup file: <value>

This is an informational message. SQL Backup could not write backup data to disk at the first attempt, but succeeded after further attempts.

This indicates potential problems with storing backup files at the specified locations.

Error setting file pointer position: <value>

This is an informational message. SQL Backup could not continue to write backup data to disk following a previous failure, but succeeded after further attempts.

This indicates potential problems with storing backup files at the specified locations.

Insufficient disk space <value>: required <value>; available <value>

There was insufficient disk space to create the backup file. Before attempting the backup process again, create more free space on the disk, or back up to a different location.

No log files found to be restored.

SQL Backup could not find any relevant transaction log files to restore from the locations you specified.

Check that you have specified the files correctly (including any wildcards in file names).

Also check that the account the SQL Backup Agent service logs on as (the startup account) has permission to read the transaction log files.

Files missing from backup history.

One or more of the backup files required for the restore process is missing. Check the error message for details of the missing files.

Files missing from search folder.

One or more of the backup files required for the restore process is missing. Check the error message for details of the missing files.

Backup failed. Retry attempt: <value>

This is an informational message. SQL Backup could not back up the database at the first attempt, but succeeded after further attempts.

Check the error message for information about why each attempt failed.

Your license does not allow email notification to be performed.

The MAILTO, MAILTO_ONERROR, or MAILTO_ONERRORONLY keyword was specified, but has been ignored due to licensing restrictions.

SQL Backup failed to send an email notification because you are using SQL Backup Lite edition, or a read-only licensed edition of SQL Backup. To send email notifications, you must use the Pro edition of SQL Backup.

Note that from version 6.5, SQL Backup is only available in the Pro edition. SQL Backup Lite has been retired.

If you are currently using SQL Backup Lite and have not yet been contacted by Redgate about a free upgrade, please go to the SQL Backup product page and download it from there. You can use your existing serial key to license the Pro version.

Failed to initialize local data store: <value>

SQL Backup could not initialize the SQL Server Compact database it uses to store details of backup and restore processes. The SQL Server Compact database is created when the SQL Backup server components are installed and is used to improve the performance of the GUI.

Check the error message for the cause of the failure.

If the error message reports that access to the database file is not allowed, you need to ensure that the account the SQL Backup Agent service logs on as (the startup account) has permission to access it. For more information, see Permissions.

Failed to open local data store: <value>

SQL Backup could not connect to the SQL Server Compact database it uses to store details of backup and restore processes.

The SQL Server Compact database is created when the SQL Backup server components are installed. The account the SQL Backup Agent service logs on as (the startup account) must have permission to access the folder containing the SQL Server Compact database files (data.sdf). By default, this is:

• %PROGRAMDATA%\Red Gate\SQL Backup\Data\<instance name> (Windows Vista, Windows 2008 and later), or 
• %ALLUSERSPROFILE%\ Application Data\Red Gate\SQL Backup\Data\<instance name> (Windows XP and Windows 2003).

For more information, see Permissions.

Folder does not exist: <folder name>.

Check that all the log file locations you have specified for your log shipping restore job are available.

If necessary, create the missing directories, or alter your log shipping restore job so that it refers to the correct directories.

Also, check that the account the SQL Backup Agent service logs on as (the startup account) has permission to read the directories.

Get exclusive local data store access failed - timeout.

SQL Backup could not acquire a lock on the SQL Server Compact database it uses to store details of backup and restore processes. Another process was accessing the database for more than 15 seconds.

The SQL Server Compact database may be too large. Review your backup history deletion settings:

1. Open the SQL Backup GUI and select the SQL Server you were trying to back up or restore to. 
2. From the Tools menu select Server Options.
3. On the File Management tab, review the settings under SQL Server backup and restore history. Consider reducing the amount of backup history you retain. For more information, see File Management Options.

Get exclusive local data store access failed - abandoned.

SQL Backup could not acquire a lock on the SQL Server Compact database it uses to store details of backup and restore processes. This was due to a termination request.

This usually happens because the SQL Backup Agent service is in the process of shutting down. You can restart the SQL Backup Agent service from the Windows Services panel.

Get exclusive local data store access failed - invalid lock handle.

SQL Backup could not acquire a lock on the SQL Server Compact database it uses to store details of backup and restore processes. This was probably caused by an internal error.

Try restarting the SQL Backup Agent service. To do this, open the Windows Services panel, select the SQL Backup Agent service for the instance, right-click and select Restart.

Invalid DB handle.

SQL Backup could not write data to the SQL Server Compact database it uses to store details of backup and restore processes. The database was not available.

Try restarting the SQL Backup Agent service. To do this, open the Windows Services panel, select the SQL Backup Agent service for the instance, right-click and select Restart.

Get exclusive local data store access failed - invalid lock handle.

SQL Backup could not release a lock on the SQL Server Compact database it uses to store details of backup and restore processes. This was probably caused by an internal error.

Try restarting the SQL Backup Agent service. To do this, open the Windows Services panel, select the SQL Backup Agent service for the instance, right-click and select Restart.

Local data store error: <value>

SQL Backup could not write data to the SQL Server Compact database it uses to store details of backup and restore processes.

Check the error message for the cause of the failure.

Local data store SQL error: <value>

SQL Backup could not write data to the SQL Server Compact database it uses to store details of backup and restore processes. There was an error preparing the SQL command used to write the data.

Check the error message for the cause of the failure.

Encryption key size is specified, but password is empty.

The KEYSIZE keyword has been specified, but the PASSWORD keyword has not been specified, or it is specified with a zero-length password.

Short passwords may not be secure.

The KEYSIZE keyword has been specified, but the supplied PASSWORD is seven characters or fewer.

Transaction log has already been restored.

This is an informational message. One or more transaction log backup files has already been restored, and will not be restored again.

This may indicate that the MOVETO option is not moving restored transaction log files to the specified directory.

Alternatively, another process may be copying old transaction log backup files to the directory SQL Backup is using for newly created transaction log backup files.

Failed to run sp_change_users_login report while checking for orphaned users.

The ORPHAN_CHECK option was included in a RESTORE command, but SQL Backup could not run the sp_change_users_login stored procedure.

Check the error message for the cause of the failure.

The file name (<file name>) contains an invalid character (<invalid character>).

This warning arises if the <DATABASE> tag is used, either directly or via the <AUTO> tag, to generate a backup file name from the database name, and the database name includes an invalid character. If no backups are created, error code 505 is also returned.

For information on using tags to generate file names, see File location tags. For information on the <AUTO> tag see File management options.

File does not exist: <Filename .sqb>

This warning may arise during a restore operation. The restore process will perform a check on the file to ensure it is accessible before the restore begins. If there is a temporary network interruption or a delay in the initial response being received, this warning will occur, but the second attempt to check the file will succeed. The warning can be ignored in these circumstances.