If the service is restarted during an ongoing recording, it will be unable to reconnect to the recording session already in progress. As a result, it will not be able to:
Monitor the recording status.
Apply any modifications requested after the recording has started.
Update the related asset information.
Properly associate the completed recording with the originating asset.
If the Broker Service becomes unavailable due to network issues, server failures, or workstation problems, there are only two ways to avoid losing the ongoing recording.
The safest approach is to allow the recording to continue until its scheduled end time.
In this scenario:
The physical media file will be created correctly from start to finish.
The recording service will automatically stop the recording at the scheduled time.
The file will be properly finalized and closed.
However, the file will not be linked to any asset because the Broker Service is no longer managing the recording.
The operator must then manually associate the generated file with the appropriate asset and manually start the After Ingest workflow.
A recording is scheduled on asset XXX starting at 10:00 AM with a duration of 2 hours.
At 10:30 AM, the server hosting the Broker Service unexpectedly shuts down due to an external issue.
When the Broker Service is restarted, it cannot regain control of the recording that is already in progress.
The operator must wait until the scheduled end time (12:00 PM). The recording service will automatically stop the recording and finalize the media file. Since the Broker Service is no longer tracking the recording, the generated file will not be linked to asset XXX.
The operator must manually associate the file from Media Library using the standard operational procedure.
If the recording must be stopped before its scheduled end time, the operator can use the MultiIngest Client.
Procedure:
Open the MultiIngest Client.
Connect to the Ingest Service instance used by the Broker Service.
Locate the active recording session.
The only available command will be STOP.
Execute the STOP command.
In this scenario:
The recording will be stopped immediately.
The media file will be correctly finalized and closed.
The file will not be linked to any asset because the Broker Service is no longer managing the recording.
The operator must manually import or associate the generated media file with the desired asset and manually trigger the appropriate workflow required for media processing and movement.
A recording is scheduled on asset XXX starting at 10:00 AM with a duration of 2 hours.
At 10:30 AM, the server hosting the Broker Service unexpectedly shuts down.
After the server is restored, the Broker Service cannot reconnect to the active recording.
The operator opens the MultiIngest Client, connects to the appropriate Ingest Service instance, and presses STOP.
The recording service stops the recording and properly closes the media file. Since the file is not associated with any asset, the operator must manually import or link the file to the desired asset and then manually execute the required workflow.
Note: This second option should only be used when the recording must be terminated before its originally scheduled duration.
If the MultiIngest Client closes unexpectedly (for example, due to an application crash or a workstation failure), it can reconnect to the corresponding running Ingest Service and regain control of the active recording.
In such cases, the operator will only be able to stop the recording; no other actions are available during this recovery procedure.
The recorded media will not be lost. However, it is recommended to verify that the generated file is correctly associated with the corresponding asset. If the association is missing, the operator must manually link the file to the appropriate asset.
For streaming recordings, this verification may not be necessary, as the asset association is typically created automatically a few seconds after the recording starts.