SQL Backup - 6.5
Activating SQL Backup
When you download and install SQL Backup, you have a 14 day trial period in which you can evaluate the product. When your trial period expires, you are invited to purchase the product. If you need more time to evaluate the product, contact firstname.lastname@example.org
When you purchase SQL Backup, you are sent an invoice that contains your serial number. You use the serial number to activate the product. If you cannot find your invoice, you can review your serial numbers at http://www.red-gate.com/myserialnumbers
SQL Backup is licensed per physical server. If you have a number of SQL Server instances registered with SQL Backup that are all on the same physical server, you need to activate only one of the instances. The status of SQL Backup on the server for a registered SQL Server instance is displayed in the Registered SQL Servers pane in the graphical user interface. You can activate SQL Backup on a server if one of the following icons is displayed to the right of the name of the SQL Server instance:
SQL Backup is activated for a trial period on this server.
The SQL Backup trial period has expired. To use SQL Backup with this SQL Server instance, you must activate SQL Backup for the server.
When you activate SQL Backup, the licensing and activation program sends an activation request to the Red Gate activation server, using checksums of attributes from your computer. The checksums that are sent to the activation server do not contain any details that might pose a security risk. The activation server returns an activation response and an encrypted key to unlock the software. The licensing and activation program should activate SQL Backup within a few seconds.
If you experience problems, you can try manual activation. You can use manual activation if:
- your computer is not connected to the Internet
- your network uses a proxy server that interrupts contact between the product and the Red Gate activation server
- activation is unsuccessful (see Troubleshooting licensing and activation errors)
Note that you cannot automate activation using the command line. However, if you are not able to activate a server using the graphical user interface, you can use the program ProductActivation.exe which is provided with SQL Backup. For example, you may wish to use this program to activate cluster nodes. ProductActivation.exe is located in the folder in which you installed SQL Backup: for example, C:\Program Files\Red Gate\SQL Backup 6. You can also start the program from the SQL Backup GUI by selecting Tools > Utilities > Cluster Activation Wizard from the menu.
For general questions about licensing, see Licensing and activation FAQs.
To activate SQL Backup on a server
- To activate SQL Backup on a server:
- click the or icon next to the server you want to activate
- or, right-click the name of the SQL Server instance and click Activate License
The activation dialog box is displayed:
- Enter your serial number and click Activate.
Your activation request is sent to the Red Gate activation server.
When your activation has been confirmed, the Activation successful page is displayed:
If there is a problem with your activation request, an error dialog box is displayed. For information about activation errors and what you can do to resolve them, see Troubleshooting licensing and activation errors. Depending on the error, you may want to try manual activation.
- Click Close.
You can now continue to use your product.
Activating multiple servers
If you have purchased a SQL Backup license for multiple servers, you can activate these servers at the same time using the Multi-Server Activation utility (select Multi-Server Activation from the Tools > Utilities menu).
Deactivating SQL Backup
You may wish to deactivate SQL Backup on a server so that you can reuse the serial number on another server. You can do this using the SQL Backup GUI, or the Red Gate deactivation tool.
To deactivate a serial number, the server on which the SQL Backup server components are installed must have a connection to the internet.
Deactivating SQL Backup using the GUI
In the Registered SQL Servers pane, right-click the SQL Server instance and click Deactivate License. If you have more than one SQL Server instance on the same computer, all the instances on that computer will be deactivated.
Note that you can deactivate a SQL Server using the GUI only if the latest server components are installed.
Deactivating SQL Backup using the deactivation tool
If you are unable to deactivate SQL Backup using the GUI (perhaps because the SQL Server is using old SQL Backup server components), you can use the Red Gate deactivation tool on the server instead.
You will need to download and run the deactivation tool on the computer where the SQL Server instance is installed. See Deactivating your products for more information.
Re-activating SQL Servers
If you need to re-install SQL Backup server components on the same computer, for example following installation of a new operating system, you can re-activate using the same serial number. If you need to change the computer on which the server components are installed and your current serial number does not work, contact email@example.com
Manual activation enables you to activate products when your computer does not have an Internet connection or your Internet connection does not allow SOAP requests. You will need access to another computer that has an Internet connection.
You can use manual activation whenever the Activation Error dialog box is displayed and the Activate Manually button is available, for example:
To activate manually:
- On the error dialog box, click Activate Manually.
The Activate using the Red Gate Web site dialog box is displayed:
- Copy all of the activation request.
Alternatively you can save the activation request, for example to a location on your network or to a USB device.
- Leaving the activation dialog box open, on a computer that has an Internet connection, go to the Manual Activation page of the Red Gate Web site at http://www.red-gate.com/activate and paste the activation request into the box under Step 1.
- Click Get Activation Response.
- When the activation response is displayed under Step 2, copy all of it.
Alternatively you can save the activation response.
- On the computer where the licensing and activation program is running, paste the activation response or if you saved it, load it from the file.
- Click Finish.
The Activation successful page is displayed.
- Click Close.
You can now continue to use SQL Backup on this computer.
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