Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backup process with two rundown engines #84

Open
theusmpa opened this issue Jun 24, 2020 · 4 comments
Open

Backup process with two rundown engines #84

theusmpa opened this issue Jun 24, 2020 · 4 comments

Comments

@theusmpa
Copy link

Imagine a situation where a system with casparCG backup will be configured, running 2 lists (or 2 rundown engines .. as you prefer to call)
on casparCG PRI server: channel 1 engine 1, channel 1 engine2 and preview engine 1 channel
on casparCG SEG server: channel 2 engine 1, channel 2 engine2 and preview engine 2 channel

channel 2 is backup of channel 1 ...

It turns out that when synchronizing the media between the servers, engine1 and engine2 perform the same copying process, in the end I have the same file copied twice to the backup server.

I would have to solve this issue with a configuration leaving the sync of the media as an option when configuring the backup channel in the rundown engines. Is this possible to implement?

Would there be another solution that I don't see?

tks

--Matheus

@jaskie
Copy link
Owner

jaskie commented Jun 24, 2020

Did you observed that behavior? In which scenario? Startup synchronization, manual synchronization, or during file ingest?

@theusmpa
Copy link
Author

I noticed in the initial synchronization (when I have some material in the main that is not in the backup) and during the ingest.

@theusmpa
Copy link
Author

Hello,

Were you able to reproduce the above behavior?

Thank you.

--Matheus

@jaskie
Copy link
Owner

jaskie commented Jun 29, 2020

Not yet. Simply lack of time...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants