Udostępnij za pośrednictwem

  • Artykuł

Moving a Back-End Database for an Enterprise Pool

Topic Last Modified: 2009-05-22

If you need to move the back-end database, such as might be required if the current location has insufficient space available for the database, you can move the back-end database to a different location on the same computer or to another computer.

Note

Before you move a database, ensure that the new location meets the system requirements for a back-end database. If you are moving the database of an Enterprise pool to a different computer, ensure that SQL Server 2005 or SQL Server 2008 is installed on the server. For details about system requirements and installation of SQL Server, see Internal Office Communications Server Component Requirements in the Supported Topologies and Infrastructure Requirements documentation and Install SQL Server in the Deploying Office Communications Server 2007 R2 documentation.

Moving a Back-End Database for an Enterprise Pool

In order to move a back-end database for an Enterprise pool, you do the following:

  • Detach the ACDDyn, RTC, RTCAb, RTCConfig, and RTCDyn databases from the Enterprise pool and move the database files to the new location.
  • Attach the ACDDyn, RTC, RTCAb, RTCConfig, and RTCDyn databases to the Enterprise pool.

To detach the databases and move the database files for an Enterprise pool

  1. Verify that the RTC database is backed up and that the backup files are accessible. For details about backing up the database, see Office Communications Server 2007 R2 Backup and Restoration Guide in the Operations documentation.

  2. Log on as a member of the RTCUniversalServerAdmins group. To stop Office Communications Server services remotely, you can log on to any computer in the same forest. To stop services locally, you must log on to each server in the pool.

  3. Stop all Office Communications Server services on all the computers in the pool.

  4. Log on as a member of the Administrators group to the Back-End Database Server for the pool.

  5. Open SQL Server Management Studio. Click Start, click All Programs, click Microsoft SQL Server 2005 or Microsoft SQL Server 2008, and then click SQL Server Management Studio.

  6. In the console tree, expand the server node. Expand Databases, and then for each of the databases (ACDDyn, RTC, RTCAb, RTCConfig, and RTCDyn), do the following:

    1. Right-click the database, point to Tasks, and then click Detach.
    2. In the Detach Database dialog box, in the details pane, select the check box in the Drop Connections column, and then click OK.

    After you have detached all the databases, move the .mdf and .ldf files for each database to the new location (server or path), and then use the following procedure to attach the databases.

To attach the databases for an Enterprise pool

  1. Log on as a member of the Administrators group to the Back-End Database Server where you are moving the databases.

  2. Open SQL Server Management Studio.

  3. In the console tree, expand the server node. Right-click Databases, and then click Attach.

  4. For each database, do the following:

    1. In the Attach Databases dialog box, in the details pane, under Databases to attach, click Add.
    2. In the Locate Database Files dialog box, click the .mdf file for the database to attach, and then click OK.
    3. In the Attach Databases dialog box, verify that both the .mdf file and the .ldf file of the database are listed under database details. If the .ldf file is not listed, add it now. Click the button in the Current File Path column, next to the .mdf file, click the .ldf file for the database, and then click OK.
    4. In the Attach Databases dialog box, click OK.

  5. After you have verified that all the databases are listed under the Databases folder, update the pool back-end settings. Click Start, and then click Run. In the Open box, type cmd, and then click OK. At the command prompt, type the following command with information about your deployment:

    lcscmd /forest /action:UpdatePoolBackend 
/poolname:[name of pool to which databases have been attached] 
/poolbe:[name of SQL Server instance for the pool back-end]

  6. Log on as a member of the RTCUniversalServerAdmins group to the server on which the Enterprise pool was created (generally, the Front End Server of the Enterprise pool).

  7. Insert the Microsoft Office Communications Server 2007 R2 CD, or if you installed Office Communications Server from a network share, go to the \Setup\amd64 folder on the share, and then double-click setupEE.exe.

  8. In the deployment tool, click Prepare Environment.

  9. At Create Enterprise Pool, click Run.

  10. In the Create Enterprise Pool Wizard, on the Pool Name, Domain and Back-End page, do the following:

    • In Pool name, type the pool name.
    • Verify that Domain is the fully qualified domain name (FQDN) of the domain where you will install the Office Communications Server Enterprise Edition server roles is correct.
    • Confirm that Pool FQDN is the pool name followed by the domain that you specified.
    • In SQL Server instance, type the name of the SQL Server that is to host the back-end database and the name of the database instance. If you are using the default instance, specify only the name of the SQL Server. Otherwise, enter the SQL Server name and instance by using the following syntax: <servername>\<instance>.

    Note

    The SQL Server instance must already exist before you perform this step.

  11. On the Web Farm FQDNs page, in Internal Web farm FQDN and External Web farm FQDN, type the same FQDNs as before.

  12. On the Reuse Existing Database page, clear the Replace existing database check box.

    Warning

    If you select the Replace existing database check box, all of your existing data will be lost.

  13. On the Locations for User Database page, in Persistent user database and the Transient user database, type the appropriate path for each.

  14. On the Meeting Content and Archive Location page, do the following:

    • Under Meeting content location, type the address of the share that you created for storing Web conference presentations as described in the “Folders” section of Storage Requirements in the Planning and Architecture documentation. Use the format \\<computer name>\<Presentation>. You must specify a remote Universal Naming Convention (UNC) path.
    • Under Meeting metadata location, type the address of the share that you created to store metadata used by the pool’s Web Conferencing Server for the pool. For details, see Storage Requirements in the Planning and Architecture documentation. Use the format \\<computer name>\<Metadata>. You must specify a remote UNC path.
    • To enable archiving of Web conference data, select the Enable meeting archiving check box. Click Meeting archive location, and then type the address of the share that you created to store Web conference compliance information. For details, see Storage Requirements in the Planning and Architecture documentation. Use the format \\<computer name>\<MeetingCompliance>. You must specify a remote UNC path.

    Note

    The Create Pool Wizard accesses these shares and attempts to give read/write permission to the service accounts and groups used by Office Communications Server. For a complete list of these permissions, see Permissions Created by the Create Pool Wizard in the Deploying Office Communications Server 2007 R2 documentation. If for some reason, the wizard cannot access any of these shares or cannot grant the correct permissions, the wizard fails.
    If you encounter this issue, ensure that the account you are using has permissions to administer the shares. As a last resort, you can bypass this step by using LcsCmd.exe with the /force command-line option. If you do this, you must grant the appropriate permissions on these shares manually. For details, see the command-line reference in the Office Communications Server 2007 R2 Operations documentation.

  15. On the Specify Locations of Miscellaneous Server Stores page, type the UNC paths for the following three stores:

    • Click Address Book Server file store, and then type the UNC path of the share that you created for storing Address Book information.

    • Click Application Data store, and then type the UNC path of the share that you created for storing application data.

    • Click Client Update Data store, and then type the UNC path of the share that you created for storing client and device update files.

      Note

      For details about the share that stores device update files and its requirements, see Device Update Service in the Planning and Architecture documentation.

  16. Click Next.

  17. On the Archiving, Call Detail Recording, and QoE Monitoring page, select the Archive instant messages, the Enable call detail recording, or the Enable QoE monitoring check boxes, if appropriate.

  18. Click Next.

  19. On the Ready to Create Enterprise Pool page, review the settings that you specified. If you are satisfied with them, click Next to begin installation.

  20. When the files have been installed and the wizard is complete, select the View the log when you click Finish check box, and then click Finish.

  21. After looking at the log and verifying that all tasks completed successfully, use the Office Communications Server 2007 R2 snap-in to start all the stopped services for the Enterprise pool. If you choose instead to start the services manually, restart the ones that were running on the Enterprise pool before you moved the databases in the following sequence:

    • Office Communications Server Front End service
    • Office Communications Server IM Conferencing service
    • Office Communications Server Telephony Conferencing service
    • Office Communications Server QoE Monitoring Agent service
    • Office Communications Server Web Conferencing service
    • Office Communications Server A/V Conferencing service
    • Office Communications Server QoE Monitoring service
    • Office Communications Server Call Detail Recording service
    • Office Communications Server Application Sharing service
    • Office Communications Server Response Group Service
    • Office Communications Server Conferencing Attendant service
    • Office Communications Server Conferencing Announcement Service
    • Office Communications Server Outside Voice Control service