Patching and Reboot Procedures
CAMIO
Reboot
As a best practice, it is suggested that CAMIO restarts at least once a week. Scheduled restarts should be considered within established maintenance windows and procedures to minimize disruption to critical operations.
Patching (Windows updates)
Please feel free to run all required Windows updates during the appropriate maintenance window. Before installing any SQL updates, please ensure to consult with the Chyron Customer Success team regarding the qualification status of targeted patches. This will help ensure compatibility and smooth integration with your system.
PRIME
Reboot
As a best practice, it is suggested that Prime restarts the software once a day and the hardware at least once a week. Scheduled restarts should be considered within established maintenance windows and procedures to minimize disruption to critical operations.
Patching (Windows updates)
Please feel free to run all required Windows updates during the appropriate maintenance window.
ISQ
Reboot
As a best practice, it is suggested that ISQ restarts the software once a day and the hardware at least once a week. Scheduled restarts should be considered within established maintenance windows and procedures to minimize disruption to critical operations.
Patching (Windows updates)
Please feel free to run all required Windows updates during the appropriate maintenance window.
NEWSTICKER
Reboot
As a best practice, it is suggested that Newsticker restarts the hardware at least once a month. Scheduled restarts should be considered within established maintenance windows and procedures to minimize disruption to critical operations.
Patching (Linux updates)
Before installing any updates, please ensure to consult with the Chyron Customer Success team regarding the qualification status of targeted patches. This will help ensure compatibility and smooth integration with your system.
VSAR
Reboot
As a best practice, it is suggested that VSAR restarts the hardware at least once a week. Scheduled restarts should be considered within established maintenance windows and procedures to minimize disruption to critical operations.
Software restart recommendations would vary.
It is important to clarify that the main reason for VSAR software restart is GPU usage and memory allocation. Both GPU Fps and Memory allocation can be checked in the VSAR Editor interface and are not fixed values, as they depends on how each Project was conceived and its underlying processes. It is recommended to keep Fps running in the desired Frame Rate by optimizing rendering features, and keep the memory allocation below 15000Mb.
If the Project is open but not in Play mode, VSAR uses only the resources necessary to keep the Project open. In this case, there are no software restart requirements, and Chyron recommends checking the VSAR and Project status daily before switching to Play Mode, and turn on the Play Mode only during Production.
If the Project Level is left constantly in Play Mode, VSAR will be allocating resources to perform the rendering of the Level content.
For example, for a Project where GPU usage and memory allocation were tested before deployment with standard performance results (stable real-time Fps for GPU, and up to 3mb/minute for memory allocation), only if necessary, VSAR could be left running in Play Mode for up to week before requiring a software restart..
Patching (Windows updates)
Please feel free to run all required Windows updates during the appropriate maintenance window.