SQL Backup - 7.2
The Registered SQL Servers pane - SQL Backup
The Registered SQL Servers pane displays a list of the SQL Server instances you have registered with SQL Backup, and their databases.
You use this list to select the SQL Server instance or database that you want to back up or restore, or for which you want to view details such as the activity history.
Navigating the Registered SQL Servers pane
The SQL Server instances are organized into groups. You choose the group to which you want an instance to belong when you register it. To change the group to which an instance belongs, in the Registered SQL Servers pane, drag the SQL Server instance to the group. For information about creating and managing groups, see Managing SQL Server groups.
The SQL Server groups, instances, and databases are displayed in a tree structure. To expand an item, click 
. The time line also expands to show activities for the databases. To collapse an item, click 
.
You can scroll through the list of SQL Server instances and databases by using the scroll bar to the right of the time line, or by moving the mouse pointer over the Registered SQL Servers pane and rotating your mouse wheel button.
Display
The connection status of each SQL Server instance is displayed to the left of the instance:
|
Connected. |
|
SQL Backup has not attempted to connect to the SQL Server because you are using SQL Server authentication and you chose not to save the password when you entered the authentication details. Double-click the icon or click |
|
SQL Backup could not connect to the SQL Server because of an authentication error, such as an incorrect password. Click the icon to enter the correct details. |
|
SQL Backup could not connect to the SQL Server. Click the icon to see the associated error messages. Note that you can specify the time period for which SQL Backup will attempt to connect to each SQL Server in the connection properties for that server (right-click the server and click Edit, then select the Options tab). For more information see Adding SQL Server instances. |
|
SQL Backup is connecting to the SQL Server instance, or refreshing the connection. You can continue to interact with the time line while a connection is being refreshed. The corresponding row in the time line is shaded |
indicating that there is no connection to the server.
while connecting.You may also see the following icons displayed to the right of the SQL Server instance name:
|
SQL Backup is installed and activated on this SQL Server, but the version of server components is not up-to-date compared with your version of the graphical user interface. Click the icon to upgrade the server components. Note that this icon does not show you when new versions of SQL Backup become available for download; you can use Check for updates for this. |
|
SQL Backup is activated for a trial period on this SQL Server. Click the icon if you have purchased a license and you would like to activate it. For more information, see Activating SQL Backup. |
|
The SQL Backup trial period has expired. To use SQL Backup with this SQL Server instance, you must activate SQL Backup for the SQL Server. Click the icon if you have purchased a license and you would like to activate it. For more information, see Activating SQL Backup. |
|
SQL Backup version 4 or earlier is installed on the SQL Server. You must upgrade the server components to use SQL Backup 6 with this SQL Server instance. Click the icon to upgrade the version of SQL Backup on the SQL Server. For more information, see Installing or upgrading on a SQL Server instance. |
|
You have not installed the SQL Backup server components on the SQL Server. Click the icon to install the server components. For more information, see Installing or upgrading on a SQL Server instance. |
For each connected SQL Server instance, you can click to see the databases on the instance. The status of each database is displayed:
|
Operational. The database is fully usable. Transaction log backups and differential backups cannot be restored to this database. |
|
The database is being restored, or it has been left in a non-operational state (using WITH NORECOVERY) so that differential backups and transaction log backups can be restored to it. |
|
The database is read-only. If the database is read-only because it has been left in a standby state (using WITH STANDBY), transaction log backups and differential backups can be restored to this database. |
|
The database is unavailable because it has been set to a SUSPECT or EMERGENCY state. Refer to your SQL Server documentation for more information. |
|
The database is offline or in an unknown state. |
Refreshing the data
For the selected SQL Server, and for all databases that are visible in the time line, SQL Backup refreshes the display every minute.
To refresh the display for a SQL Server, click the SQL Server in the Registered SQL Servers pane, and press F5. 
is displayed next to the SQL Server instance while SQL Backup refreshes the connection. Note that if the SQL Server is busy, there may be a short delay before the display refreshes. You can continue to interact with the time line while a connection is being refreshed.
Interaction
Whenever applicable, the SQL Backup features and displays act on the item you select in the Registered SQL Servers pane. For example, if you have a database selected and you click 
Backup, the Backup wizard pre-selects the database for you (you can change the selection in the wizard).
Similarly, the Activity History, In Progress, Log Copy Queue or Jobs tab is updated with information related to the selected item. For example, if the Activity History tab is displayed and you click a SQL Server instance name, all activities that have occurred on that instance are shown in the tab; if you then click a database, only those activities that occurred on the selected database are shown in the tab. The Reminders tab is updated with information according to the server selected.
SQL Server and database properties
You can display properties for a SQL Server instance or a database.
To do this, right-click the SQL Server instance or database in the Registered SQL Server pane and click Properties.
SQL Backup must be connected to the SQL Server for the properties to be displayed.
SQL Backup displays details of the selected SQL Server instance, and database, as applicable. For example:
To see the properties of another SQL Server or database, click on it; you do not need to close the Properties window first.
You can display the properties of backup and restore activities from the Activity History. For details, see "Activity properties" in Activity History.
See also |
Was this article helpful?
Installing or upgrading SQL BackupSecurity model
Activating SQL Backup
Registering SQL Servers with SQL BackupExploring the graphical user interfaceBacking up and restoringTools and utilitiesSettings and optionsScripting SQL BackupWorking with SQL BackupError code reference
Acknowledgements
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
