Recovery planning, Encoder failure considerations, Server failure considerations – Grass Valley NewsBrowse Desktop Browsing System Installation v.2.0 User Manual

Page 117: Database maintenance and administration, Chapter 4

Advertising
background image

25 May 2004

NewsBrowse Installation and Configuration Guide

117

Chapter

4

Recovery Planning

Establish a recovery plan for the customer in the event a NewsBrowse machine fails,
so that NewsBrowse services can be re-configured rapidly to minimize impact.

Encoder failure considerations

Encoders provide redundancy through numbers. A plan should identify the critical
encoders in the system and alternate encoders that can be reconfigured to substitute in
the case of failure. There are no automated fail-over capabilities with NewsBrowse
components. It is important to identify which machine(s) host Managed Device
Interface services (for either Proxy MDI or Profile MDI). These services can be
pre-installed on secondary devices, although the server should not be configured to
monitor them unless a failure of the primary service occurs. Managed Device
Interface services can exist on any encoder and the server need only to be
reconfigured to point to the new machine in case of failure.

Server failure considerations

The SQL database should be backed up on a regular basis and stored in a safe location.
In the case of server failure the database can then be restored to minimize data loss. If
an off-line backup server is purchased it should be pre-configured to operate in the
system so in case of primary server failure, minimal time will be spent bringing up the
backup system. The backed up database could be restored to this backup server on a
regular basis.

Newer NewsBrowse systems have redundant power supplies and mirrored disks to
further protect the integrity of the system.

Database maintenance and administration

The AMDBSan.exe is a utility that will compare the GeneralMetaDataTBL and
URN2URITBL of the ThomsonAM database to locate orphan records. It will
compare all the URN_UID's from the URN2URITBL to the URN's in the
GeneralMetaDataTBL to see if a metadata record exists. If the metadata record does
not exist then it is considered an orphan record.

AMDBScan is located in the C:\Program Files\Thomson\NewsBrowse\ directory. To
activate the AMDBScan utility it can be simply double clicked or run from a
command prompt. As it runs, it will create a log file as well as display results in the
DOS window. If any orphan records are detected the user will be prompted and asked
if they would like to remove the orphan records. The interface will require a (y/n)
response from the user. If the response is y then the orphan records are removed. If
the answer is n, the orphan records are not removed. The log file created will also
reside in the C:\Program Files\Thomson\NewsBrowse\ directory with the file name
AMDBScan_Log_MMDDYYYYHHMMSS.txt.

Advertising