EasyManua.ls Logo

Appear TV SC2000 - Maintenance; Software Upgrades; Configuration Back-Up System; Configuration Backup Guidelines

Default Icon
134 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
SW Version 2.04 30-January-2009 Page 102 of 128
6 Maintenance
This chapter describes how to perform maintenance tasks such as software upgrades,
replacing faulty modules, etc.
6.1 Software Upgrades
Software can be uploaded to the unit remotely using the Maintenance Center (MC).
Please refer to the MC users manual for details.
Required software upgrades for units the will be provided together with instructions
by.
6.2 Configuration Back-up System
The ASIO-based software platform enables automatic backup of the service
configuration. It consists of a Linux cron job set to run every night at 04:00. A history
of 4 copies will be preserved before the system starts to override backup files. The
script looks for other ASIO cards, and exports the database to a text file and copies it
to the remote cards found. In case the backup is needed there is a script provided to
retrieve the backup. This script will erase the current configuration and create a new
database with the exported data.
Note:
A module reboot is necessary for the new configuration to be activated – this is
automatically done by the “restore” script.
Some useful commands
atvdbsnapshot dist dumps the live configuration to file on a
remote card within the unit
atvsdbsnapshot restore <database> restores the earlier files dumped to the
remote card. For ex:ample:
atvsdbsnapshot restore atvconfig.db
6.3 Configuration backup guidelines
Although the internal backup system will automatically back up the configuration
database it is good practice to keep a copy of the database somewhere externally to
the unit, the more importantly so the larger the configuration.
To make an external backup of the configuration please refer to section 6.6
If the external copy is to be used it is necessary to stop the application process on the
card before the configuration database may be copied. To do this log into the MMI
board using telnet or SSH. Then type
stop asio Check that the processes are stopped
ftp atvconfig.db to /etc/atv/atvconfig.db
(If this fails, stop the boa server, it may occupy the database.)

Table of Contents

Related product manuals