* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download Editstar Maintenance Schedule
Survey
Document related concepts
Serializability wikipedia , lookup
Microsoft Access wikipedia , lookup
Oracle Database wikipedia , lookup
Extensible Storage Engine wikipedia , lookup
Relational model wikipedia , lookup
Open Database Connectivity wikipedia , lookup
Ingres (database) wikipedia , lookup
Concurrency control wikipedia , lookup
Microsoft Jet Database Engine wikipedia , lookup
Team Foundation Server wikipedia , lookup
Database model wikipedia , lookup
Microsoft SQL Server wikipedia , lookup
Transcript
Chapter 2 EditStar Maintenance Schedule Chapter 1 EditStar Maintenance Schedule This chapter describes daily and weekly procedures that should be followed to maintain an EditStar system. An EditStar Weekly Maintenance Log worksheet is provided at the end of this chapter, that allows for easy recording of procedures performed on the system. When performing any daily or weekly procedures, initials of the person doing the procedures should be recorded. The log sheet provides a space for recording any changes made to the EditStar system (refer to “OTHER” section of log sheet). The following system changes should be noted on this sheet: EditStar software upgrades Profile software or hardware upgrades EditStar client hardware or software upgrades Network upgrades or changes Completing the EditStar Weekly Maintenance Log worksheet on a weekly basis in an accurate manner will assist EditStar Technical Support Department personnel in diagnosing a problem, and provides the station with a written log of system maintenance and upgrades. A detailed description of each entry in the Maintenance Log follows. Daily: 1. The following items should be checked throughout the day, especially a few minutes before a show. (a) Check the EditStar server applications on the Profiles and Database servers, to verify that each EditStar server application is running correctly. Refer to the “EditStar Server Applications Description” in Chapter 1, Introduction for more information on how to determine the correct running state of each application. To summarize: Video Server Port Server MCULink Configuration Server Dub Server MCU All eight channels appear The status message Waiting for new link accept appears Air channels are enabled and active Both Primary and Backup Database servers are responding; active server list is complete Dub operations are being processed Status indicators in upper-right-hand side of screen are blinking 1-1 Chapter 2 EditStar Maintenance Schedule (b) Check the EditStar Dub Monitor for queued dub operations. The Dub Monitor can be installed and invoked as a subapplication on either an EditStar or NewStar workstation, or from the View Dub Operations menu of the EditStar Video Management program. Verify that All Users and Active Operations Only options are checked in the Dub Monitor View menu. 2. Once per day, at a convenient time, the following operations should be completed: (a) Archive and delete any video on the Profile that is no longer needed, using the EditStar Video Management program (C:\EDITSTAR\CLEANUP.EXE). Keeping at least 20 percent free space on the Profiles is recommended. (b) When no one is using the EditStar system, restart the EditStar Server Monitor on Profile(s) and Database server. Restarting the Monitor program will restart all EditStar server programs running on that server. Verify that all applications start up properly. When the restart is complete, restart all EditStar workstations. (c) Reboot the Browse Capture Engine (if one exists). 1-2 Chapter 2 EditStar Maintenance Schedule Weekly: It is recommended that you perform the following procedures at least once per week, in the following order. Since EditStar servers must be stopped, these procedures should be performed when the EditStar system is not in use. Note: The EditStar database(s) may require compaction more than once per week, depending on system usage. It is suggested that you perform a compaction when the database (videodb.mdb) grows to 10 times its minimum compacted size. 1. Exit the EditStar Server Monitor on all EditStar servers. Note: Exiting the Monitor program will stop all EditStar programs running on the server. 2. Compact the EditStar databases. Note: You may notice the size of Primary and Backup databases differs. Despite the size difference, each database contains the same data. (a) Ensure that the EditStar Configuration server is not running on the Primary Database server. (b) Optional: Back up the existing EditStar database by copying C:\EDITSTAR\VIDEODB.MDB to another folder. (c) Remove the EditStar database share by starting Windows Explorer and right-clicking (NT 4.0 only) on the C:\EDITSTAR\DATABASE folder. Select the Sharing… item from the pop-up menu, and then select the Not Shared option button in the Properties dialog. Click Yes to disconnect any users from the shared resource. (d) Open the ODBC Data Source Administrator (via WinNT’s ODBC icon in the Control Panel). 1-3 Chapter 2 EditStar Maintenance Schedule (e) Select and open the VideoDB Data Source. (f) Click on the Compact button. (g) Use defaults for the source and destination videodb.mdb. (h) After compaction, copy the compacted Primary database over the Backup database on the Backup Configuration server (also in the C:\EDITSTAR\DATABASE folder). (i) The database share will be reestablished when the Configuration server is restarted. 3. Delete mismatched media between Profile and EditStar databases. The EditStar Profile Clip Database Editor (dbedit.exe) is used to view and delete mismatched video clip IDs between the Profile Video database and EditStar database. Run dbedit.exe from the C:\EDITSTAR directory on each Profile and remove all unreferenced items marked “No” in the Referenced column, except for the black clip (FFFFFFFF). 1-4 Chapter 2 EditStar Maintenance Schedule 4. Check and repair the Profile’s video file system. The Profile’s PDRCHECK utility deletes non-referenced media files, bad media references, and bad movie description files. This utility will not run unless all EditStar servers are stopped on the Profile. Run this program by typing C:\PROFILE\PDRCHECK –D from the DOS command prompt in Windows NT. 5. Verify that Database and Profile servers have adequate hard disk space. Occasionally, a logging mechanism may be inadvertently left on, causing the hard disk to fill. If EditStar logging is not required (sometimes requested by the Service department), delete all log files in the C:\MCULog and C:\DubLog directories. Prevent creation of new log files by disabling the logging mechanisms on MCULink and the Dub server. 1-5 Chapter 2 EditStar Maintenance Schedule 6. Shut down and power-cycle PAC audio chassis, Profile(s), and EditStar Database server. The EditStar Monitor program and all EditStar server programs should start automatically when the servers are restarted. Important: The PAC audio chassis must be turned on before the Profile is started. 7. Reboot and restart all EditStar clients. 1-6 Chapter 3 Troubleshooting EditStar EDITSTAR WEEKLY MAINTENANCE LOG WEEK OF: __________________________ DAILY M: 1a. 1b. 2a. 2b. INITIALS T: W: Th: F: S: Verify each application is responding appropriately. Server Application Notes Profile 1 Monitor Video Server Port Server MCULink Profile 2 Monitor Video Server Port Server MCULink Primary DB Monitor Config Server Dub Server Backup DB Monitor Config Server Check Dub Monitor. Delete / Archive. Restart Monitor on Profile(s) and Database. WEEKLY 1. 2. 3. 4. 5. 6. 7. S: INITIALS Stop all EditStar servers. Compact EditStar database. Delete EditStar unreferenced clips (DBEDIT.EXE). Check and repair Profile file system (PDRCHK –D). Verify hard disk space on Database server and Profile(s). Power-cycle PAC audio chassis, Profile(s), and Database server. Reboot and restart all EditStar clients. OTHER EditStar System Changes: Hardware Software Network Miscellaneous 1-7