Microsoft KB Archive/929981

From BetaArchive Wiki

Article ID: 929981

Article Last Modified on 1/25/2007


APPLIES TO

  • Microsoft TV Foundation Edition 1.7 Service Pack 1


INTRODUCTION

In Microsoft TV Foundation Edition 1.7, the Targeted Broadcast Message Service (TBMS) may be migrated from one server farm to another. This article discusses how to migrate TBMS from one server farm to another.

MORE INFORMATION

TBMS is configured by using the following files:

  • Tbms.xml

This file is part of the standard Microsoft TV Foundation Edition configuration. This file specifies the Motorola OM-1000 out-of-band multiplexers/modulators to which messages may be sent.

  • Tbms.mdb

This file is a database of messages that have been sent to the set-top boxes. This database also contains message counters. The set-top box uses these counters to determine which messages are new and which messages have already been viewed. The TBMS database is managed by the TBMS application Graphical User Interface (GUI).

To prevent set-top boxes from viewing messages more than one time after you migrate TBMS, make sure that the following conditions are true:

  • Only one Microsoft TV Foundation Edition server farm is configured to communicate with the OM-1000s.
  • The most up-to-date TBMS database resides on the server farm that is active.
  • You have removed OM-1000 support from the "old" or source server farm.
  • You have added OM-1000 support to the "new" or destination server farm.

How to migrate TBMS from one server farm to another

Notes

  • “Source server farm” refers to the system from which you are moving TBMS.
  • “Destination server farm” refers to the system to which you are moving TBMS.
  • The TBMS extension document and .chm file state that the Tbmsdb.mdb file can be backed up and restored by using the Microsoft Access GUI. However, Microsoft Access is not installed on the Microsoft TV servers. Therefore, you must perform backup and restore operations by stopping services on the Microsoft TV stream engine computer and then copying the Tbmsdb.mdb file while the services are stopped.
  1. Back up the Microsoft TV configuration files and the TBMS databases on the source and destination Microsoft TV server farms. To do this, follow these steps:
    1. Start the Microsoft TV command prompt.
    2. Move to the Configuration directory by typing the following command:

      cd configuration

    3. Create a copy of the current configuration by using the tvs command in a directory whose name uses the YYYYMMDD_Rollback format. For example, run the following command in the 20061218_Rollback directory:

      tvs get-config 20061218_Rollback

    4. Create a backup directory that resembles the following:

      C:\Program Files\Microsoft TV\Foundation Server 1.7 NA\TBMSDB\20061218_Backup

    5. At the command prompt, type tvs stop.
    6. In Windows Explorer, locate the C:\Program Files\Microsoft TV\Foundation Server 1.7 NA\TBMSDB directory. This directory contains the TBMS database. If the Tbmsdb.ldb lock file is present in this directory, click Start, click Run, type Services.msc, right-click MSTV Targeted Broadcast Message Service, and then click Restart. After the service is restarted, the Tbmsdb.ldb lock file should no longer be present.
    7. Right-click MSTV Targeted Broadcast Message Service, and then click Stop.
    8. Copy the C:\Program Files\Microsoft TV\Foundation Server 1.7 NA\TBMSDB\Tbmsdb.mdb file to the directory that you created in step 1d.
    9. At the command prompt, type tvs start.
  2. Remove OM-1000 support from the source server farm. To do this, follow these steps:
    1. Start the Microsoft TV command prompt.
    2. To change to the Configuration directory, type cd configuration.
    3. Create a working copy of the current configuration by running the tvs command in a directory whose name uses the YYYYMMDD_Ver1 format. For example, type the following command in the 20061218_Ver1 directory:

      tvs get-config 20061218_Ver1

    4. Use Notepad to open the 20061218_Ver1\Tbms.xml file.
    5. Put a comment character on all lines for the XML node that are named destinations. Use Internet Explorer to open the file, and then confirm that all destination nodes are commented.
    6. At the command prompt, run the following commands to commit the changes and to restart services. Press ENTER after each command.

      tvs validate-config 20061218_ver1
      tvs commit-config 20061218_ver1
      tvs stop all
      tvs start all

    7. Start the TBMS application, and then click New to create a new message. Confirm that no OM-1000s are present.

      Note You cannot create a message if no OM-1000s are selected.
  3. Add OM-1000 support to the destination server farm. To do this, follow these steps:
    1. Start the Microsoft TV command prompt.
    2. To move to the Configuration directory, type cd configuration.
    3. Create a working copy of the current configuration by running the tvs command in a directory whose name uses the YYYYMMDD_Ver1 format. For example, type the following command in the 20061218_Ver1 directory:

      tvs get-config 20061218_Ver1

    4. Use Notepad to open the 20061218_ver1\Tbms.xml file.
    5. On all lines for the XML node that are named destinations, insert the OM-1000 destination sections that were commented out from the source Tbms.xml file.
    6. At the command prompt, run the following commands to commit the changes and to restart services. Press ENTER after each command.

      tvs validate-config 20061218_ver1
      tvs commit-config 20061218_ver1
      tvs stop all
      tvs start all

    7. Start the TBMS application, and then click New to create a new message. Confirm that OM-1000s are present and may be selected.
  4. Copy the TBMS database from the source server farm to the destination server farm. To do this, follow these steps:
    1. At a command prompt on the destination server farm, type the following command:

      tvs stop C:\Program Files\Microsoft TV\Foundation Server 1.7 NA\TBMSDB

    2. In Windows Explorer, locate the C:\Program Files\Microsoft TV\Foundation Server 1.7 NA\TBMSDB directory. This directory contains the TBMS database. If the Tbmsdb.ldb lock file is present in the directory, click Start, click Run, type Services.msc, right-click MSTV Targeted Broadcast Message Service, and then click Restart. After the service is restarted, the Tbmsdb.ldb lock file should no longer be present.
    3. Right-click MSTV Targeted Broadcast Message Service, and then click Stop.
    4. Right-click the Tbmsdb.mdb file, click Security, and then confirm that the following three accounts have FULL CONTROL permissions.
      • g_sitecode_tbms
      • administrators
      • system

      Note sitecode will be site specific. For example, for a domain that is named evt17, the account name is g_evt17_tbms.

    5. Copy the Tbmsdb.mdb file from the source stream engine computer to the destination stream engine computer. Copy the file to the C:\Program Files\Microsoft TV\Foundation Server 1.7 NA\TBMSDB directory.
    6. At the command prompt, type tvs start.
    7. On the destination server farm controller, run the TBMS application, and then confirm that messages are present.

How to roll back the system if the migration is unsuccessful

  1. Remove OM-1000 support from the destination server farm. To do this, follow these steps:
    1. Start the Microsoft TV command prompt.
    2. To move to the Configuration directory, type cd configuration.
    3. Create a working copy of the current configuration by using the tvs command in a directory whose name uses the YYYYMMDD_Ver2 format. For example, type tvs get-config 20061218_Ver2 in the 20061218_Ver2 directory.
    4. Copy the Tbms.xml file from the rollback directory. For example, copy the Tbms.xml file from the 20061218_Rollback directory to the 20061218_Ver2 directory.
    5. At the command prompt, run the following commands to commit the changes and to restart services:

      tvs validate-config 20061218_ver2
      tvs commit-config 20061218_ver2
      tvs stop all
      tvs start all

    6. Start the TBMS application, and then click New to create a new message. Confirm that no OM-1000s are present.
  2. Add OM-1000 support to the source server farm. To do this, follow these steps:
    1. Start the Microsoft TV command prompt.
    2. To move to the Configuration directory, type cd configuration.
    3. Create a working copy of the current configuration by using the tvs command in a directory whose name uses the YYYYMMDD_Ver2 format. For example, in the 20061218_Ver2 directory, type tvs get-config 20061218_Ver2.
    4. Copy the Tbms.xml file from the rollback directory. For example, copy the 20061218_Rollback file to the 20061218_Ver2 directory.
    5. At a command prompt, run the following commands to commit the changes and to restart services. Press ENTER after each command.

      tvs validate-config 20061218_ver2
      tvs commit-config 20061218_ver2
      tvs stop all
      tvs start all

    6. Start the TBMS application, and then click New to create a new message. Confirm that OM-1000s are present.
  3. Restore the TBMS databases on the source and destination server farms. Follow these steps on the source and destination stream engine computers:
    1. Start the Microsoft TV command prompt, and then type tvs stop.
    2. In Windows Explorer, locate the C:\Program Files\Microsoft TV\Foundation Server 1.7 NA\TBMSDB directory. This folder contains the TBMS Database. If the Tbmsdb.ldb lock file is present, click Start, click Run, type Services.msc, right-click MSTV Targeted Broadcast Message Service, and then click Restart. After the service is restarted, the Tbmsdb.ldb lock file should no longer be present.
    3. Right-click MSTV Targeted Broadcast Message Service again, and then click Stop.
    4. Copy the Tbmsdb.mdb file from the C:\Program Files\Microsoft TV\Foundation Server 1.7 NA\TBMSDB\YYYYMMDD_Backup directory to the C:\Program Files\Microsoft TV\Foundation Server 1.7 NA\TBMSDB directory.
    5. At the command prompt, type tvs start.
    6. Start the TBMS application, and then confirm that the messages are present as expected.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.

Keywords: kbhowto kbinfo KB929981



Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.


Retrieved from ‘https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/929981&oldid=226483’
the Creative Commons 3.0 ShareAlike (except the Microsoft KB Archive).
Powered by MediaWiki