Automated backup of Cablecast Pro?
Dear Tightrope,
I am designing a broadcast system around Cablecast Pro and two SX4 servers in a mirrored configuration. Is there a way to “mirror” the automation system so that if Cablecast Pro should go down a backup solution is already in place? Or is the only solution a manual transfer of cables/databases to one of the SX4 servers?
Also, what options do you have for a loss of signal detector? I see that Spyglass is one. Are there any others?
Thank you,
John
I am designing a broadcast system around Cablecast Pro and two SX4 servers in a mirrored configuration. Is there a way to “mirror” the automation system so that if Cablecast Pro should go down a backup solution is already in place? Or is the only solution a manual transfer of cables/databases to one of the SX4 servers?
Also, what options do you have for a loss of signal detector? I see that Spyglass is one. Are there any others?
Thank you,
John
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?John,
1.) The database
All the Cablecast data is stored in a SQL server database. Because everything is in the database, the database file is what needs to be copied from the Pro machine to an SX server. Because of the way SQL server works, this is usually a manual process, while you could script it to happen every night it's still not 'up to the second' redundancy.
SQL server does have a feature called replication. However, we use SQL 2005 Express, which can only be a subscriber of replication, not a publisher. If you have a DBA and a server that is running the full version of SQL server, you could configure Cablecast to use the other SQL server and set up a replication subscription on the Pro and SX.
Unfortunately, this is complex SQL server configuration and Tightrope can not help you configure or run SQL servers. If you have an experienced DBA that can set this configuration up then you may give it a try.
You might consider writing a script that runs on a schedule, it would be a lot less work and probably get you 90% there. Worst case is that you would loose the changes that happened between backups/restores. Might not be that much data loss.
2.) Playback shadowing
I think you already know this, but just it reiterate; If you have 2 SX server they can run their playback in 'shadow' mode. Which means that any commands sent to server 'A' will also play on server 'B'. So you can have 4 redundant channels. The key is to determine when to switch between the 2 servers.
A few of our customers have this configuration combined with 4 spyglass's for failure detection.
3.) Video failure detectors
I know that there are a few video failure detectors out there but I don't have personal experience with any of them. Maybe some customers on the forum here have opinions. Spyglass I know is one a lot of people use. -
Inappropriate?FYI there is more information on this topic on these threads:
Switching to a backup Cablecast server for automation
How Do I sync automation between Two Cablecast systems?
Loading Profile...




EMPLOYEE