3.3
Table Of Contents
- Avid iNEWS Administration Guide
- Contents
- Using This Guide
- 1 - Introduction
- 2 - Connect Services
- 3 - Database Security
- 4 - Database Management
- 5 - Backing Up the iNEWS System
- 6 - Disconnects
- 7 - Troubleshooting
- A - Command References
- Programs Invoked by iNEWS
- Commands Used by Avid Personnel Only
- Linux Commands Used in iNEWS
- Console Control Commands
- Console Server Commands
- broadcast
- configure
- connect
- ctraits
- dbclean
- dbclose
- dbdev
- dbdump
- dbfree
- dblines
- dboriginal
- dbpurge (Superuser conditional)
- dbrestore
- dbserver
- dbsort
- dbtraits
- dbvisit
- dictionary
- diskclear (Superuser only)
- diskcopy
- doc
- ed
- enter
- force (Superuser only)
- grpcheck
- gtraits (Superuser only)
- help
- hogs
- idiff
- list
- list B
- list C
- list c
- list d
- list g
- list p
- list q
- list s
- list sq
- list u
- logout
- makemontab
- makeshift (Super user only)
- maketab (Superuser only)
- msgclean
- offline
- online
- otod
- reconnect
- remove
- rename (Superuser only)
- reorder
- restart
- searchtape
- send
- shutdown
- sitedump (Superuser only)
- siterestore (Superuser only)
- startup
- status
- stop
- su
- unbusy
- utraits (Super user only)
- version
- wholockedit
- Job List Commands
- Dialog Commands
- B - System Files
- C - Standard Dictionaries
- Using Dictionaries to Define Messages and Commands
- Customizing Dictionaries
- Utility Messages Dictionary (/site/dict/messages)
- DBServer Program Messages
- Disconnect Program Messages
- Category and Keyword Check Program Messages
- Keyboard Check Program Messages
- Keyboard Check Program Messages for Macros
- Grpcheck Messages
- Wire Program Messages
- Mail Server Messages
- Validation (Action) Server
- Seek Server Messages
- Last Login Messages
- Print Server Messages
- dbtraits Messages
- Save Error (Workstation) Messages
- Queues Dictionary (/site/dict/queues)
- Words Dictionary (/site/dict/words)
- Keyboard Macros Dictionary (/site/dict/keymacros)
- Case-shifting Dictionary (/site/dict/shift)
- MCS Dictionary (/site/dict/mcs)
- Job List Command Dictionary (/site/dict/joblist)
- D Messages Dictionary (/site/dict/dmessages)
- S Messages Dictionary (/site/dict/smessages)
- D - Environment Variables
- E - Managing Traits at the Console
- F - The Line Editor, ed
- Index
6 Disconnects
92
At this point, all devices and sessions are running on the survivor—that is, master
computer—even the ones that normally run on the other, revived server. These devices,
utility programs, and sessions eventually need to run in their normal place on the revived
server.
Schedule a time to log the users off and stop the servers and devices. At that time, run
the following commands on the survivor:
NRCS-A# offline
NRCS-A# logout all
NRCS-A# stop all
8. Reconfigure the system (survivor).
The system is now running in a dual AB configuration. When you run the configure
command, the system will reconsult the /site/config file and divide responsibility for
which server will run the devices, half for server A and half for B:
NRCS-A# offline
NRCS-A# configure
NRCS-A# online
Wait for the system being configured messages to appear on both servers before moving
on to the next step.
9. Start up the revived server.
When you run startup on the revived server, the devices and utility programs (such as
action servers or txnet links) on that server are started and it is placed online:
NRCS-B# startup
10. Restart all of the survivor’s devices by typing
restart all
on the master computer.
The system is now running normally (dual) with all sessions and devices in their normal
places.
If server B was selected as the master database, it is now the master computer. Since
either server can run as master, nothing further needs to be done. If you want to make
server A the master computer again, perform a normal system shutdown, reboot and
startup, as described in iNEWS Newsroom Computer System Setup and Configuration
Manual.
c
Wait for the diskcopy to complete before rebooting the system to make server A the
master computer again. Database corruption may result if the system is taken down
before the diskcopy completes. If the system loses power or must be rebooted; the
master computer that contains the full database must be brought up in a single server
configuration, and the disconnect recovery procedure restarted again.