Partilhar via

How to: Recover or Move a Single-Server Deployment of Notification Services

  • Artigo

A single-server deployment of Notification Services hosts an entire instance of Notification Services, including the following:

  • Engine components, including the hosted event providers, generators, and distributors.
  • The instance of the SQL Server Database Engine that hosts the instance and application databases.
  • Optionally, client components such as subscription management interfaces and non-hosted event providers.

This topic shows the general procedure for recovering or moving a single-server deployment of Notification Services.

Important

All deployments of Notification Services are unique. If you have a single-server deployment of Notification Services, use the following procedure as a guideline for developing and testing your own procedure.

Step 1: Restore the files, metadata, and registry information

  1. Install the SQL Server 2005 Database Engine and Notification Services. For more information, see Installing SQL Server 2005.

  2. Create any Microsoft Windows accounts and SQL Server login accounts required by the instance of Notification Services.

  3. Recover the instance and application databases.

    The exact procedures you use to recover a database depend on the recovery model. For more information about recovering databases, see Backing Up and Restoring How-to Topics (SQL Server Management Studio).

  4. Recover all operational files used by the instance of Notification Services. If you do not have a list of the files and their required locations, you can look in the instance configuration and application definitions. If you do not have this information, you can export an instance configuration file (ICF) and application definition files (ADFs) from the databases. For more information, see Exporting Notification Services Instance and Application Metadata.

  5. From the Start menu, point to All Programs\Microsoft SQL Server 2005\Configuration Tools, and then click Notification Services Command Prompt to open a command prompt window.

  6. Register the instance of Notification Services, creating the NS$instanceName Windows service.

    Note

    If you host the Notification Services engine in a custom application, do not create the Windows service. For more information, see Hosting the Notification Services Engine.

  7. Repair the metadata for the instance of Notification Services.

Step 2: If necessary, update the instance of Notification Services

  1. Disable the instance of Notification Services.

  2. Modify the SQL Server system value in the instance configuration so that it references the new instance of the Database Engine.

  3. Modify the system name values in each application definition so that they reference the new computer name.

  4. Update the instance to apply the changes to the instance and application databases.

Step 3: Bring the instance of Notification Services online

  1. Enable the instance of Notification Services.

  2. Start the instance of Notification Services. If using the NS$instanceName Windows service, start the Windows service. If hosting the engine in a custom application, use the custom application to start the instance.

  3. Verify the status of the instance of Notification Services.

    Note

    It may take 30 seconds for the status to be updated.

See Also

Tasks

How to: Recover or Move Notification Services Client Components
How to: Recover or Move Notification Services Databases
How to: Recover or Move Notification Services Engine Components

Concepts

Recovering Instances of Notification Services

Other Resources

Administering Notification Services
Managing Instances and Applications How-to Topics (Notification Services)

Help and Information

Getting SQL Server 2005 Assistance