To change the database used by the Archiving Server, you deactivate the server and then activate it again, specifying the new database name during the activation process.

For details about SQL Server requirements, see Install SQL Server (for Archiving Server)in the Deploying Archiving Server documentation.

To change the database of the Archiving Server

  1. On the server where you installed the Archiving Server, log on as a member of the DomainAdmins and RTCUniversalServerAdmins groups.

  2. Open the Office Communications Server 2007 R2 snap-in.

  3. Expand Archiving Servers, right-click the fully qualified domain name (FQDN) of the Archiving Server, and then click Deactivateto start the Deactivate Archiving Server Wizard.

  4. Complete the wizard to deactivate the server.

  5. To start the activation process, insert the Microsoft Office Communications Server 2007 R2 CD. Setup starts and launches the deployment tool. If you installed the Archiving Server from a network share, go to the Setup\amd64 folder on the share, and then double-click either setupEE.exeor setupSE.exe.

  6. Click Deploy Other Server Roles, and then click Deploy Archiving Server.

  7. At Activate Archiving Server, click Run.

  8. On the Welcomepage, click Next.

  9. On the Select Service Accountpage, specify a new or existing service account to use for the Archiving Server, and then enter the password. The default account is RTCComponentService. For a new account, ensure that you use a strong password that meets your organization's Active Directory password requirements. When you are finished, click Nextto continue.

  10. On the Select SQL Server Instancepage, do one of the following:

    • To use the default instance, type the name of the server in the box.

    • To specify a different instance, type the name of the instance in the format <servername>\<instance>. For example, sqlserver\dbInstance.

  11. In Enter database name, type the name of the SQL Server database that the Archiving Server will use (by default, LcsLog), and then click Next.

  12. On the Reuse Existing Databasepage, do one of the following:

    • If you want to use a database that is already on the SQL Server instance, clear the Replace any existing databasecheck box. Do this only if the existing database has the same database schema.

    • If you want to use a new database, or overwrite an existing database, select the Replace any existing databasecheck box.

    Caution:
    If you select the Replace any existing databasecheck box, any existing database on the SQL Server instance will be deleted, and all its data will be lost.
  13. Click Next.

  14. On the Location for Database Filespage, specify where you want to install the archiving database and transaction log files:

    • Under Archiving database, in Database, accept the default directory, or click Browseto locate another directory.

    • In Transaction logs, accept the default directory, or click Browseto locate another directory.

  15. When you are finished, click Next.

  16. On the Start Service Optionpage, select the Start the service after activationcheck box.

    Note:
    SQL Server (the MSSQLServer service) must be started before you start the Archiving service (the RTCLog service).
  17. When you are finished, click Next.

  18. On the Ready to Activate Archiving Serverpage, review the settings that you specified, and then click Nextto activate the Archiving Server. To make any setting changes, click Back.

  19. When the wizard finishes, verify that the View the log when you click Finishcheck box is selected, and then click Finish.

    Note:
    Any change that you make to the pool-level archiving settings does not take effect until you restart the Office Communications Server Front End service. If you change any of the archiving settings for a pool, you should restart all Front End Servers in the pool to ensure that the settings take effect uniformly. If you mark archiving as critical on your Front End Servers and you then disable the Archiving Server, you must restart all Front End Servers; otherwise, one or more Front End Servers might stop running.