[00:00] In this lesson, we will learn how licenses are affected by redundancy. Since redundancy is a platform level feature, it's not owned by one module. Rather, other modules utilize it. In a production environment, you're going to want a license on both the master as well as the backup gateway. So you will need two licenses. The main reason is that when a failover occurs, the backup gateway is responsible for continuing operations. If the backup doesn't have a license and the trial is expired, then none of the modules will run, which more or less invalidates the point of having redundancy in the first place. When you purchase a license from us, you do have the option to add on a backup only license, which is basically a copy of the license you're purchasing, but it's intended for the backup gateway. I'm looking at my backup gateway here, which does have this kind of license applied. If I look at the effective license, there's this backup true item. Now, in most cases, you don't really need to know what these details are, but the backup one is special as it marks this gateway as a backup only.

[01:09] So this gateway here can only ever be set to a backup mode in redundancy. For example, if we go over to the redundancy page and we try to change the mode to independent and save our changes, nothing will actually occur. Here we can see that a our role towards the top of the screen still remains as backup, and we'll eventually see that redundancy still persist because there is a peer connected. If you would like to change the mode of the backup gateway, the backup only license must first be inactivated. Once inactivated, a new license will need to be applied. Otherwise, the gateway will operate in the two hour trial mode.