SQL Backup 6

Upgrading the server components

For information about upgrading the server components on a SQL Server cluster, see Installing the server components on a SQL Server cluster.

The SQL Backup graphical user interface (GUI) and server components are upgraded separately:

  • You can upgrade to the latest version of the GUI using Check for Updates on the Help menu. 
  • Once the GUI has been upgraded, the upgrade server components icon  is displayed next to each of the SQL Server instances listed in the Registered SQL Servers pane.

    Click the icon or right-click the SQL Server name and select Install or upgrade server components to open the Upgrade Server Components wizard. Click Finish to confirm that you want to upgrade.
    If your SQL Server security does not allow you to upgrade remotely, you can upgrade the server components manually by copying SQBServerSetup.exe to the server and running it. By default SQBServerSetup.exe is located in %ProgramFiles%\Red Gate\SQL Backup 6 on 32-bit servers and %ProgramFiles(x86)%\Red Gate\SQL Backup 6 on 64-bit servers. 

If you have upgraded to a new major version (for example, from version 6 to 7) and had previously activated SQL Backup on the SQL Server with a support and upgrades contract, SQL Backup will remain activated with the same serial number.

Otherwise, a 14 day trial of SQL Backup will begin, indicated by the trial license icon . When the trial expires, this is indicated by the trial expired icon ; you must purchase a license to continue using SQL Backup on that SQL Server. To purchase a license, email sales@red-gate.com. For information about activating SQL Backup on a SQL Server, see Activating

When upgrading to a later version, the server components are installed in the default location and it is not possible to specify an alternative location. To install the server components in a different location, first uninstall the current server components, then install the new server components manually to specify the location.

Upgrading from SQL Backup version 5

If you are upgrading from SQL Backup version 5, you do not need to import SQL Servers that you previously added to the SQL Backup GUI. Your servers will be added automatically to the SQL Backup GUI Registered SQL Servers pane. If you have not yet upgraded to the SQL Backup 6 server components, the upgrade server components icon  is displayed to the right of the SQL Server name in the Registered SQL Servers pane. Upgrade the server components as described above. Note that when you upgrade, the server components remain in the folder they were originally installed in. For example, %ProgramFiles%\Red Gate\SQL Backup 5\<instance name>To install the server components in a different location, first uninstall the current server components, then install the new server components, specifying the path.

The upgrade server components icon  may be shown in various locations within the GUI when you are working with a SQL Server instance that still has version 5 server components installed. This indicates that certain features are unavailable until you upgrade the server components to version 6.

The scripts and jobs you created using version 5 are supported in version 7, and will work in the same way.

SQL Backup 6 introduces changes to the SQL Backup file format. When you upgrade the SQL Backup server components to the latest version 6 components, SQL Backup creates new backup files in the version 6 format. The backup file extension is unchanged (.sqb).

  • SQL Backup 6 is fully compatible with files created by earlier SQL Backup versions. You can work with any backup file version using SQL Backup 6.
  • SQL Backup 5 (version 5.4 and earlier) cannot be used to restore a version 6 backup file. To restore a version 6 backup file to a server that has not been upgraded, you must use the SQL Backup File Converter to convert the files first.

Upgrading the activity cache

The activity cache speeds up the display of backup and restore history in the SQL Backup GUI by storing a copy of the backup and restore history for your registered SQL Servers.

By default, the cache data is located on the same computer as the SQL Backup GUI in:

  • %LOCALAPPDATA%\Red Gate\SQL Backup\Server Data (on Windows Vista, Windows 2008 and later) or 
  • %USERPROFILE%\Local Settings\Application Data\Red Gate\SQL Backup\Server Data (on Windows XP and Windows 2003)

When you start the GUI for the first time, you may be prompted to upgrade the activity cache. This will only happen if an activity cache from SQL Backup version 5 is found on your computer.

This may take several minutes, but happens only once.

Upgrading from SQL Backup version 4

If you are upgrading the SQL Backup GUI from version 4, you can import all your registered SQL Servers into SQL Backup 6; you do not have to register them all again. For details, see Importing SQL Server instances

When you add or import a SQL Server, if you have not yet installed the SQL Backup 6 server components on it, is displayed to the right of the SQL Server name in the Registered SQL Servers pane. Click the icon to upgrade the server components.

You must then activate the SQL Server. If you have purchased a support contract, you can use the same license key as you used in version 4 (SQL Backup will remember this for you). Otherwise, you can use a trial version of SQL Backup 6 for 14 days, but then you must purchase a license. For more information, see Licensing.

If you do not upgrade the server components, SQL Backup retrieves the details of activities and jobs on these SQL Servers when you first start SQL Backup. The information is displayed in the Time Line, the Activity History, and the Jobs tab. However, this information cannot be refreshed while SQL Backup is running.

Note the following changes from version 4:

  • Any options you set in version 4 are imported into version 6. However, note that backup alerts are no longer available; instead you can now use the Time Line or create a report of backup activity to see overdue backups. For more information about the options available, see File management options.
  • The scripts and jobs you created using version 4 are supported in version 6, and will work in the same way.
  • If you saved any backup settings in version 4, you can use them in version 6. However, in version 6 they are called templates.
  • Some features are restricted for activities and jobs from a previous version of SQL Backup. For example, you cannot display the properties of a backup performed by SQL Backup version 4.

Didn't find what you were looking for?