Database and recovery planning, Database planning and maintenance strategies, Encoder failure considerations – Grass Valley Aurora Browse v.7.0 Installation User Manual

Page 141

Advertising
background image

April 6, 2010

Aurora Browse Installation and Configuration Guide

141

Chapter

6

Database and Recovery Planning

You need to establish a recovery plan in the event an Aurora Browse MediaFrame
system fails, so that services can be re-configured rapidly to minimize impact.

This chapter describes strategies for planning and maintaining the database and
recovery images. It is divided into two sections:

“Database planning and maintenance strategies”

“Backup and recovery strategies”

Database planning and maintenance strategies

Procedures in this section are as follows:

“Encoder failure considerations” on page 141

“MediaFrame server failure considerations” on page 142

“Updating the database to the simple model” on page 142

“Creating a simple maintenance plan” on page 143

“Verifying the database maintenance plan status” on page 145

“Testing the backup” on page 146

“Modifying the database maintenance plan” on page 147

“Restoring the MediaFrame server database” on page 148

“Updating the maintenance plan after renaming the server” on page 148

“Reconfiguring MediaFrame after renaming the server” on page 146

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 Aurora Browse
MediaFrame components. It is important to identify which machine(s) host Managed
Device Interface services. 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.

Encoding jobs can be assigned to any available Aurora Proxy Encoder. N+1
redundancy is achieved by adding an extra Aurora Proxy Encoder.

Advertising