beautypg.com

Recovery planning, Encoder failure considerations, Mediaframe server failure considerations – Grass Valley Aurora Browse v.6.5 Installation User Manual

Page 103: Verifying the database maintenance plan status, Chapter 4, Chapter 4, recovery planning, To c

background image

November 1, 2008

Aurora Browse Installation and Configuration Guide

103

Chapter

4

Recovery Planning

Establish a recovery plan in the event an Aurora Browse MediaFrame system fails, so
that 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 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.

MediaFrame server failure considerations

The MediaFrame server must have a database maintenance plan in place. The
maintenance plan backs up the SQL database on a regular basis and stores it in a safe
location. In the case of server failure the database can then be restored to minimize
data loss.

MediaFrame servers shipped from the factory prior to June 2007 have Microsoft SQL
Server 2000 installed. For these servers you must configure a database maintenance
plan. Refer to previous version of this manual for procedures.

MediaFrame server shipping from the factory beginning in June 2007 have Microsoft
SQL Server 2005 installed. For these servers there is a pre-configured SQL Server
maintenance plan in place that provides the necessary backups.

If the SQLSERVERAGENT service is ever stopped, so is your maintenance plan.
Make sure that the service is set to start automatically.

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 systems have redundant power supplies and mirrored disks to further protect
the integrity of the system.

Verifying the database maintenance plan status

1. To determine the maintenance plan status, look in SQL Server Management Studio

under

<server name> + Management + Maintenance Plans

.