SQL Backup - 6.0
Learning SQL Backup - 6.0
The Time Line
The time line provides a graphical view of all the SQL Backup backup and restore activities. For a demonstration of the time line, see the SQL Backup walk-throughs and demonstration videos.
The time line shows all activities that have been set up using the SQL Backup graphical user interface, and, where possible, any other SQL Backup activities, such as those initiated using the command line. However, note that not all SQL Backup activities set up outside of the graphical interface can be recognized by SQL Backup.
For each registered SQL Server instance that is connected, the time line shows a summary of the activities on that SQL Server instance.
A gray block indicates a successful activity or a scheduled job; a red block indicates a failed activity or conflicting backup jobs.
To see the activities for the individual databases, click to expand the SQL Server instance in the Registered SQL Servers pane so that the databases are listed. The activities that correspond to the databases are shown.
Activities that have already occurred are shown as solid blocks, as illustrated above. Backup operations are green ; restore operations are blue . The type of backup is indicated by the height of the block. File or filegroup backups are the same height as differential backups.
An operation that failed is shown as a red block
Jobs that are in progress are shown as striped blocks, for example:
Jobs scheduled for the future are shown as hollow blocks, for example: . SQL Backup estimates the time duration of the job based on the last successful backup on the same database and of the same type. (Note that for multi-step jobs that include native SQL Server steps, the time estimate takes account of the SQL Backup backup step only.) Full and differential restore operations that are scheduled for the future show the icon for restoring a full backup, because SQL Backup cannot determine the backup type. Disabled jobs are not shown in the time line.
You can move your mouse pointer over a block to see more details.
If a database has two or more operations represented on the time line that are too close together to be visually distinguished, the operations are represented by a gray block . You can zoom in to the gray block to see the individual operations. For details of how to zoom in, see Navigating the time line.
If more than one backup or restore operation is scheduled at the same time on the same SQL Server instance, the time slot in which the conflict occurs is highlighted pink, and the conflicting operations are highlighted red. To see a list of all the visible jobs that conflict, right-click in the shaded area.
If a job comprises multiple schedules, the schedule that causes the conflict is also shown in the list. Note that SQL Backup lists only those jobs for the time period that you can currently see in the time line; for a full list of all conflicting jobs for the time slot, ensure that you can see the entire time slot. For details of how to change the time line view, see Navigating the time line. You can click the name of the job or schedule in the list to select it in the Jobs tab.
Navigating the Time Line
The current time is indicated with a yellow marker:
If the current time marker is not visible in the view, a small, yellow arrow is displayed in the top left (if you are looking at future jobs) or the top right (if you are looking at activity history).
You can navigate to the current time by clicking the arrow, or by clicking . For more information on the current time marker, see time settings and locations.
The date corresponding to the left edge of the time line view is displayed above the Registered SQL Servers pane. To change the date, click the arrow and select the date you require from the calendar:
There are a number of ways to scroll through the time line:
You can scroll to a different time or date by clicking the left and right arrow buttons to move in the direction indicated. To scroll more quickly, drag the central slider left or right; the further you drag the slider, the faster the time line moves.
To move the time line and SQL Server Registration pane up or down so that you can see details for databases that are not shown in the view, click the up and down arrow buttons, use the scroll bar, or press Ctrl and rotate your mouse wheel button.
Alternatively, you can move your mouse pointer to an area that does not show any activities and drag the time line to the required position (up, down, left, or right) using the grab hand
To zoom out, drag the Zoom slider to the left or click ; to zoom in, drag the Zoom slider to the right or click :
Alternatively, with the mouse pointer over the time line, rotate your mouse wheel button to zoom in or out.
When you perform a backup or restore operation, on completion, SQL Backup automatically scrolls to the activity in the time line. Similarly, when you schedule a job, on completion of the job creation SQL Backup scrolls to the first run of the new job.
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.
In the example above, the information for the LOCAL SQL Server instance is up-to-date, but the orange shading for SQL2000 and STANDBY shows that they have not been refreshed for approximately one minute.
You can move your mouse pointer over the shaded area to see the precise time at which the SQL Server was last updated. For more details about the different times that are provided, see Time settings and locations.
Red shading is used on the time line to show that the connection to a SQL Server instance has failed. Green shading is used to show that data is being collected for that particular section of the time line.
To refresh the display for a SQL Server instance, click the instance in the Registered SQL Servers pane, and press F5. While the connection to the instance is being refreshed, is displayed. You can continue to interact with the time line while a connection is being refreshed.
If you have registered a large number of instances and associated databases, you can reduce the time it takes to refresh the time line by creating groups and distributing your instances between them; data is not refreshed for collapsed groups.
Time settings and locations
SQL Backup uses locations so that you can manage SQL Servers that are situated in different time zones.
SQL Backup sets up an initial location for you to register your local SQL Server instances. This default location uses the time set on the client computer (the computer on which you are running the graphical user interface). The time zone is reflected in the tab at the top of the time line.
If there is a difference between the location time and the time set on the server (the server time), SQL Backup reflects this in the time line. For example, this may occur if the clocks on your servers have not been synchronized exactly. In the example below, the time on the server has been set to an hour earlier than the location time (in reality, the time difference may often be only a few minutes).
For the default location, the client time and location time are always the same.
Note that if your network is slow, or if your server is overloaded, you may see a difference between the server time and the client time even though their clocks are synchronized, due to the delay in SQL Backup receiving the data.
If you have servers situated in different world time zones, you can set up a separate time line for each time zone so that the current time marker shows the time local to the servers.
To create a new location:
- On the File menu, click New Location, or click the blank tab at the top of the time line:
- In the New Location dialog box, in the Time zone box, select the time zone in which the servers are located.
- If required, in Location name type a name for the location.
- Click Add Location.
The new location is displayed.
Note that SQL Backup uses the client time to calculate the location time by adding or subtracting the appropriate offset. Therefore, if your client time is incorrect, the location time will be incorrect by the same amount.
SQL Backup takes into account adjustments to time zone differences for daylight saving.
You can add SQL Servers to the new location in the usual way.
To edit or delete a location, click the tab, and on the Edit menu, click Edit or Delete as required. Alternatively you can right-click on the appropriate tab, and then click Edit or Delete. Note that if you delete a location that contains registered SQL Server instances, all instances registered to the location are removed.
Click an activity that has completed (to the left of the current server time) to select the corresponding entry in the Activity history.
Double-click a past activity in the time line to see its properties; for details, see "Activity properties" in Activity history.
Click an activity that is scheduled for the future (to the right of the current server time) to select it in the Jobs tab. Note that a number of activities on the time line can correspond to a single job in the Jobs tab.
Double-click a future activity to edit the job. The Edit Backup Job wizard is displayed. This is identical to the Schedule Backup Jobs wizard, but contains the settings for the selected job for you to edit. For details, see Scheduling backup jobs.
Note that not all jobs can be edited using SQL Backup's graphical user interface. For example, restore jobs and filegroup backup jobs must be edited using a SQL application such as SQL Server Management Studio or Enterprise Manager.
You can click an activity in the Activity History, or a job in the Jobs tab, to select it in the time line; selected activities are shown in the time line with shading, for example: for backup operations or for restore operations that have already occurred.
You can right-click an activity to see a context-menu of available features.
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