Stopping the HyperBac Control Service - SQL Storage Compress

If you are working with Red Gate support to resolve a problem, you may be asked to stop the HyperBac Control Service.

Important: do not stop the HyperBac Control Service unless instructed to do so by Red Gate support. Stopping the service while a SQL Storage Compress or SQL Virtual Restore database is online can result in corruption of the entire database.

To stop the HyperBac Control Service:

1. If you are also using SQL HyperBac, ensure that no SQL HyperBac backups are in progress.
2. Take any SQL Storage Compress or SQL Virtual Restore databases offline:
   • Right-click each database in SQL Server Management Studio (SSMS), and select Tasks > Take Offline. You may need to run this task twice before SSMS reports the database as being offline.

   or

   • Ensure you are connected to the master database, then run the following T-SQL statement for each database:

     ALTER DATABASE <database name> SET OFFLINE

     You may need to run this statement twice before SQL Server reports the database as being offline.

   Alternatively, stop the SQL Server instance. To do this, right-click the instance in SQL Server Management Studio and click Pause followed by Stop, or stop the service in the Windows Services list.

3. From the system tray double-click the HyperBac Configuration Manager icon to open the HyperBac Configuration Manager.
4. On the General tab click the Stop button.

   

5. Click Exit to close the HyperBac Configuration Manager.

You can restart the HyperBac Control Service in two ways:

• From the SQL Storage Compress user interface - when the service is stopped, a warning appears at the bottom of the window. Click the hyperlink to restart the service.

  

• From the system tray - when the service is stopped, the HyperBac Configuration Manager icon is modified: Right-click the icon and select Start HyperBac Control Service to restart the service.

Once you have restarted the HyperBac Control Service, you can bring any SQL Storage Compress or SQL Virtual Restore databases back online. Use the Bring online task in SQL Server Management Studio or run the following T-SQL statement against the master database for each compressed database:

ALTER DATABASE <database name> SET ONLINE