SQL Backup - 7.0
Scheduling backups: file settings
Scheduling backups > Specify SQL Server > Select backup type and database > Create backup schedules > File settings > Processing and encryption settings > Verification options > Review summary
This topic describes the wizard page for specifying the locations and file names for your backups, and for managing existing backup files.

Choose:
- Single backup file to create each backup as a single file.
- Single backup file, mirrored to second location to create the backup as a single file and simultaneously make a duplicate of the backup during the backup process.
This option is only available when you have selected a single database to back up. During the backup process, a warning is raised if any of the files cannot be written. However, the backup process continues as long as at least one specified backup file can be written. If none of the files can be written, an error is raised and the backup process is stopped.
- Split backup into multiple files to store each backup across a number of files.
Splitting the backup can speed up the backup process if backing up to a single file does not fully use the Input/Output capacity of your disks. For a single database backup, you can split (or 'stripe') your backup files across a number of disks. For multiple database backups, you can specify the number of files to split each database backup into (on the same disk). All backup files must be available when you restore the backup.
Backup location
For a Single backup file, if you have selected only one database to back up, a default folder and file name is displayed.

To change the file name, clear the Name file automatically check box, and type the new file name. To change the folder, type the new path or click
and specify the path using the folder browser. You can use tags in the folder and file name, if required.
For information about how to specify file names on remote servers, see Specifying file paths. Note that if you specify a network share as the backup file location, the SQL Backup Agent Service 'log on' user must have Full permissions to access the location. Backing up directly to a network share can be slower than backing up locally and occasionally problematic. You are recommended to back up locally and use the Copy backup to network option instead. For more information, see Backing up and restoring on a network share.
If you have selected multiple databases, multiple backup types, or both, the backup for each database and backup type is created in a separate file. The file names will be generated automatically using the <AUTO> tag. SQL Backup uses the default file name format specified in your Server Options; if you have not set up a default file name format, SQL Backup uses the SQL Server instance's default format for file names. A default folder for these files is displayed; to change the folder, type the new path or click
and specify the folder using the folder browser. If you want the backup file to be created in a different folder for each database, in the folder browser click Create subfolder for each database.
For a Single backup file, mirrored to second location, specify the backup file as described above, and additionally specify the folder and file name for the mirrored backups.

For Split backup into multiple files, if you have selected a single database and a single backup type, you must specify at least two destination files. Type or select each folder and file name as described above, and click Add to add it to the list.

If you have selected multiple databases, multiple backup types, or both, you can specify only one folder for the split backup files; the files will be named automatically.

In Files per backup, type or select the number of files into which you want each backup to be split (maximum 32).
Network copy location
If you want a copy of the backup files to be created on a network share when the backup has completed, select the Copy backup to network check box, and then type the network share details in the box or click
to use the folder browser. For information about how to specify file names on remote servers, see Specifying file paths.

If you typed the network share details, click Test to check that the 'log on' user for the SQL Backup Agent on the source SQL Server has permission to create files on the network share. If it does not have the appropriate permissions, an error message is displayed next to the button; if you choose to keep the network share details, a warning
is displayed in the Activity History when the backup has completed. If you browsed to the network share, this check is performed automatically.
For more information about using network shares with SQL Backup, see Backing up and restoring on a network share. For details about setting up permissions to use a network share, see Security model.
You may experience problems when you back up to network shares if your SQL Server is unable to write large data blocks (over 2 MB) to the network share. You can use the MAXDATABLOCK keyword with the BACKUP command to limit the data block size.
Managing backup files
SQL Backup provides a number of settings to automate the management of your existing backup files. You can specify these settings separately for the initial backup location, and the network copy location.
Note that if you specify a network path in the backup location folder, any network copy location options you specify will be applied to files at this path. Similarly, if you specify a local path in the network copy location folder, any backup location folder options will be applied to the copied files in the (local) network copy location.

Select the Overwrite existing backup files of the same name check box if you want to overwrite any existing files with the share/path name. Note that if a file of the same name exists already and you have not chosen to overwrite it, the backup or network copy will fail.
Select the Delete existing backup files in this folder for the selected databases check box if you want SQL Backup to delete backups of the same type for the selected databases from the initial backup or network copy destination folders. You can restrict deletion of existing backup files by age (All files older than) or number (All files except the latest).
By default, files are deleted when the backup process or network copy has completed. If the backup fails, the files are not deleted. To delete the files before the backup is created, select the Delete files prior to start of backup check box. For example, you may want to do this to create space for the new backup files. However, note that if the backup fails, the old files will have been deleted; you are therefore recommended to select this check box only if you have a copy of the existing backups. This option is available for the initial backup location only; existing network copies of files are always deleted after the copying process has completed.
Next: processing and encryption settings
See Also |
Was this article helpful?
SQL Backup
- 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
all products
- 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
SQL Backup
- 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
all 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

Installing or upgrading SQL Backup