SQL Backup - 6.5
Adding SQL Server instances - SQL Backup
To back up or restore a database, you must first add the SQL Server instance to SQL Backup. SQL Backup displays the list of SQL Server instances that have been added in the Registered SQL Servers pane.
You can add the SQL Server instances by:
- specifying the instances by name
- importing registered SQL Servers from SQL Backup version 4, Microsoft SQL Server Management Studio, or Microsoft SQL Server Enterprise Manager.
Note that if you are upgrading from SQL Backup version 5, you do not need to import SQL Servers that you previously registered; these servers will be added automatically to the SQL Backup 6 Registered SQL Servers pane.
When you have added a SQL Server instance, you can:
- edit the registration to change the authentication or connection properties
- delete an individual SQL Server instance registration, or an entire group
Adding SQL Server instances by name
- Click the tab for the location in which you want to register the SQL Server instance.
- On the File menu, click Add SQL Server.
The Add SQL Server dialog box is displayed.
- Type or select the name of the SQL Server instance in the SQL Server box.
If you experience problems selecting a SQL Server instance that is not running on the LAN, for example if you are accessing the SQL Server instance via an internet connection, you may need to create a SQL Server alias using TCP/IP; refer to your SQL Server documentation for details. You can then type the SQL Server alias name in the SQL Server box to connect to the remote SQL Server. (Note that this SQL Server alias is not the same as the SQL Backup alias, in the Options tab.)
- Select the authentication method, and for SQL Server authentication enter the User name and Password.
For Windows authentication, the credentials of the current user are used.
For SQL Server authentication, you can select the Remember password check box. The password will be encrypted. If you do not select Remember password, when you next start SQL Backup will be displayed next to the SQL Server instance name to indicate that SQL Backup has not attempted to connect to the SQL Server instance; double-click the icon or click to enter the authentication details.
- By default, SQL Backup imports the last 1 month of history for native backup and restore operations into an internal cache.
You can change the amount of native activity history to import, but should be aware that it may take a long time to import and display all the activity history for the SQL Server. The time taken to import the data depends on the number of databases on the SQL Server, the length of time the SQL Server has been in service, and the amount of activity on the SQL Server. You can choose None, 1 week, 1 month, 3 months, 6 months, 1 year, or All.
Note that if the SQL Server instance has previously been used with SQL Backup (version 4 or above), all activities that were created by SQL Backup are imported, irrespective of the time period you select for importing native activity history.
- By default, when you add a SQL Server instance, the Install or Upgrade Server Components wizard is displayed so that you can install or upgrade the server components; SQL Backup requires server components to be installed on each SQL Server instance so that it can perform backup and restore operations.
If you do not want to install or upgrade the server components now, clear the Install or upgrade server components on connection check box.
- On the Options tab, under Location and group, select the location in which the SQL Server is situated.
- From the Group list, select the SQL Server group to which you want to add the SQL Server instance.
For more information about groups, see Managing SQL Server groups.
- To set up a SQL Backup alias for the SQL Server instance, in Alias type the alias that you want to use.
The alias will be displayed throughout the SQL Backup graphical user interface.
- To change the connection properties from their default values, under Connection Properties edit the values as required.
For details, see Connection properties.
- Click Connect.
SQL Backup adds the SQL Server instance. This may take a few minutes. The SQL Server instance is displayed in the Registered SQL Servers pane.
If there was a problem with the authentication, is displayed next to the SQL Server instance name. For example, this is displayed if you have entered the password incorrectly. Click the icon to correct the authentication details.
If there was a problem connecting to the SQL Server instance, is displayed next to the SQL Server instance name. Click the icon to see further details of the problem. You can also try the following to rectify the problem:
- Verify that the SQL Server is online and that the SQL Server name is listed in your LAN by pinging the address.
For example, open a command prompt and run the following command:
where ServerName is the name of your SQL Server.
- If the SQL Server is online, verify that you are connecting to the correct port.
If your SQL Server is not running on the default port (1433), type the following in the SQL Server box on the Add SQL Server dialog:
where ServerName\Instance is the name of your SQL Server and instance, and Port is the number of the port on which your SQL Server is running. For the default instance, use:
- If you are sure that you are connecting to the correct port, force SQL Backup to use the TCP/IP network protocol when it makes the connection by setting the Connection Properties for the SQL Server.
If you chose to install or upgrade the server components, the Install or Upgrade Server Components wizard is displayed to guide you through the process. For more information about this process, see Security model and Installing or upgrading on a SQL Server instance.
To change the connection properties:
- On the Add SQL Server dialog box, select the Options tab.
- Select the required network protocol from the Network protocol list.
The available client protocols are those configured in Microsoft SQL Server using the Client Network Configuration in Computer Management.
- In Network packet size, type or select the size of the network packets to be sent.
The default value is 4096 bytes.
- In Connection time-out type or select the number of seconds to wait for a connection to be established before timing out.
The default setting is 15 seconds.
- In Execution time-out, type or select the number of seconds to wait before execution of a task is stopped.
The default value is zero seconds (no time-out).
- To force the connection to be encrypted, select the Encrypt connection check box.
Importing SQL Server instances
To select SQL Server registrations that exist already on SQL Backup version 4, SQL Server Management Studio, or SQL Server Enterprise Manager:
- On the File menu, click Import SQL Servers.
The Import SQL Server Registrations dialog box is displayed showing any existing SQL Server registrations in a tree structure.
- Select the check boxes for the SQL Server registrations that you want to import.
- In the Location list, select the location into which you want to import the SQL Servers.
For more information about locations, see Time settings and locations.
- Click Import.
SQL Backup imports the SQL Server instances.
Editing a SQL Server instance registration
To change the SQL Server authentication or the connection properties:
- Right-click the name of the SQL Server instance in the Registered SQL Servers pane and click Edit.
- Edit the registration settings and connection properties as required.
- Click Connect.
Removing SQL Servers
To remove a SQL Server instance from the Registered SQL Servers pane, do one of the following:
- Right-click the name of SQL Server instance in the Registered SQL Servers pane, and click Delete.
- Click the name of SQL Server instance in the Registered SQL Servers pane, then on the Edit menu, click Delete.
To remove all SQL Server instances in a SQL Server group and delete the group, do one of the following:
- Right-click the name of the group in the Registered SQL Servers pane, click Delete, and then click Delete on the confirmation dialog box.
- Click the name of the group in the Registered SQL Servers pane, on the Edit menu, click Delete, and then click Delete on the confirmation dialog box.
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