Redundancy loop with cloud based disaster recovery -

October 12, 2016

By Harshad

The world is moving away from downloading. Streaming music, and videos have become the norm with a whopping 45% increase in streaming revenues. Our emails, contacts, schedule, our neighbor's dog, everything is on cloud. It's just convenient this way, with lesser chances of losing out on any of our content. Yet, when it comes to broadcast the most common approach is creating a redundant system which mirrors everything in the primary broadcast workflow. Assets, schedule, ad insertions, subtitles, everything'.

In short, a TV Network spends as much in creating a redundancy as running two separate channels at the same time! But what happens if the back-up system goes down in a major disaster? Well, there is a backup system for backup, and so on till there is an infinite loop of redundancy systems. To paraphrase matrix, Nobody knows how deep the redundancy rabbit hole goes.

Needless to say, each extra redundancy is piling on the bills, making it a high OPEX affair. Fortunately, there is an alternative.

By shifting to a cloud-based disaster recovery, broadcasters, TV Networks, and content owners stand to benefit in not just the reduction of cost but also improved efficiency. Here are three ways shifting to cloud can help:

No need of maintaining physical DR sites Typically, a TV station needs to have a disaster recovery site (hot, warm, or cold) at a geographical location non- contiguous to the primary site. This involves additional maintenance as the sites need to be broadcast ready' at moment's notice. With the cloud, it's possible to completely manage disaster recovery from a remote location. In fact, one could do it sitting on a beach, provided there is adequate internet connectivity.

Disaster recovery at all levels A disaster doesn't come with a calling card. It can strike any point in the entire broadcast workflow, including your data center, teleport, or even satellite. In short, even after painstakingly taking back-up of back-ups at your datacenter, there is still a possibility of broadcast going kaput. Also, even if content assets are protected in a non-contiguous location, playout and schedule may not be protected leading to a blank screen for the audience. By moving the entire workflow to cloud, TV networks can continue transmitting despite being hit by disaster as the content as well as the playout are both in cloud. In a public cloud like AWS a different instance of cloud goes up instantaneously when the primary one is down. This ensures that the channel operation is uninterrupted.

Pay only for use

Most cloud based broadcast services offer a higher level of flexibility to the TV network. For example, Amagi CLOUDPORT can be configured to automatically pull content and schedule from a channel's existing content and schedule, without the need to set up expensive satellite or fiber network. It can be priced appropriately for usage as a backup solution' so that the TV network does not have to bear the costs of a primary feed for their back up feed. Using a cloud-based playout as the primary broadcast playout system, completely eliminates even the need to set up a separate disaster recovery feed. The cloud-based nature of the playout ensures a built-in disaster recovery.

In a time when the world is fast moving to OTT playout, and multiscreen viewing, TV networks are facing the challenge of staying relevant. A heavy capex model of traditional delivery such as satellite or fiber for disaster recovery limits the ability of TV networks to invest in high value areas such as HD, or UHD playout, or even an OTT feed. A cloud-based model can help TV networks save money and resources, which could be redeployed in making the broadcast truly future-ready.