Between two huge server parks Alpha and Bravo there has been built three different physical communication lines - Kilo,
Posted: Tue May 10, 2022 7:17 am
Between two huge server parks Alpha and Bravo there has been built three different physical communication lines - Kilo, Lima and Sierra - with different bandwidths. These three communication lines are used only to synchronize the data stored in Alpha and Bravo server parks in order to tend towards the situation where the same data is simultaneously stored in both server parks for security (availability) reasons. For other purposes these lines are not used. Because both Alpha and Bravo store extremely huge data volumes, all three lines have been operating at full capacity for the past two years (if they are not temporarily out of order).
In March, however, all three communication lines were being repaired at the same time. Sierra was starting to operate on April 1st at midnight (during first seconds). Somewhen later, also Lima was starting to operate. Kilo was starting to operate exactly three days and three hours later since Lima's start. Then all three lines worked together for a while, until somewhen Lima broke down again and only the other two lines remained to operate. This situation lasted until June 1st (till midnight) - i.e. Kilo and Sierra are working properly, Lima is broken again.
It is known that during the whole consideration period (two months, between April 1st and June 1st), the average throughput of a three-channel set was 4.9159 Gb/s - i.e. a total of 2530.17 terabits (Tb) of data was transmitted between Alpha and Bravo during this time. We know that during the period when all three communication lines were working properly and full time simultaneously, the total bandwidth of the set would have been somewhat higher, 5,490 GB /s. In addition, it is known that Lima transmitted a total of 581,927 terabits (Tb) of data between the starting (after the repair) and the re-failure. By the way, Lima was started (after the repair) exactly at midnight, but unfortunately it is not known on which actual day in April it took place. We also know that Sierra had already transmitted a total of 62,300 terabits (Tb) for the moment when Kilo was started.
Task: Find out when Lima broke down again as accurately as possible - in days, hours and minutes.
Between two huge server parks Alpha and Bravo there has been built three different physical communication lines - Kilo, Lima and Sierra - with different bandwidths. These three communication lines are used only to synchronize the data stored in Alpha and Bravo server parks in order to tend towards the situation where the same data is simultaneously stored in both server parks for security (availability) reasons. For other purposes these lines are not used. Because both Alpha and Bravo store extremely huge data volumes, all three lines have been operating at full capacity for the past two years (if they are not temporarily out of order). In March, however, all three communication lines were being repaired at the same time. Sierra was starting to operate on April 1st at midnight (during first seconds). Somewhen later, also Lima was starting to operate. Kilo was starting to operate exactly three days and three hours later since Lima's start. Then all three lines worked together for a while, until somewhen Lima broke down again and only the other two lines remained to operate. This situation lasted until June 1st (till midnight) - i.e. Kilo and Sierra are working properly, Lima is broken again. It is known that during the whole consideration period (two months, between April 1st and June 1st), the average throughput of a three-channel set was 4.9159 Gb/s - i.e. a total of 2530.17 terabits (Tb) of data was transmitted between Alpha and Bravo during this time. We know that during the period when all three communication lines were working properly and full time simultaneously, the total bandwidth of the set would have been somewhat higher, 5,490 GB/s. In addition, it is known that Lima transmitted a total of 581,927 terabits (Tb) of data between the starting (after the repair) and the re-failure. By the way, Lima was started (after the repair) exactly at midnight, but unfortunately it is not known on which actual day in April it took place. We also know that Sierra had already transmitted a total of 62,300 terabits (Tb) for the moment when Kilo was started. Task: Find out when Lima broke down again as accurately as possible - in days, hours and minutes.
In March, however, all three communication lines were being repaired at the same time. Sierra was starting to operate on April 1st at midnight (during first seconds). Somewhen later, also Lima was starting to operate. Kilo was starting to operate exactly three days and three hours later since Lima's start. Then all three lines worked together for a while, until somewhen Lima broke down again and only the other two lines remained to operate. This situation lasted until June 1st (till midnight) - i.e. Kilo and Sierra are working properly, Lima is broken again.
It is known that during the whole consideration period (two months, between April 1st and June 1st), the average throughput of a three-channel set was 4.9159 Gb/s - i.e. a total of 2530.17 terabits (Tb) of data was transmitted between Alpha and Bravo during this time. We know that during the period when all three communication lines were working properly and full time simultaneously, the total bandwidth of the set would have been somewhat higher, 5,490 GB /s. In addition, it is known that Lima transmitted a total of 581,927 terabits (Tb) of data between the starting (after the repair) and the re-failure. By the way, Lima was started (after the repair) exactly at midnight, but unfortunately it is not known on which actual day in April it took place. We also know that Sierra had already transmitted a total of 62,300 terabits (Tb) for the moment when Kilo was started.
Task: Find out when Lima broke down again as accurately as possible - in days, hours and minutes.
Between two huge server parks Alpha and Bravo there has been built three different physical communication lines - Kilo, Lima and Sierra - with different bandwidths. These three communication lines are used only to synchronize the data stored in Alpha and Bravo server parks in order to tend towards the situation where the same data is simultaneously stored in both server parks for security (availability) reasons. For other purposes these lines are not used. Because both Alpha and Bravo store extremely huge data volumes, all three lines have been operating at full capacity for the past two years (if they are not temporarily out of order). In March, however, all three communication lines were being repaired at the same time. Sierra was starting to operate on April 1st at midnight (during first seconds). Somewhen later, also Lima was starting to operate. Kilo was starting to operate exactly three days and three hours later since Lima's start. Then all three lines worked together for a while, until somewhen Lima broke down again and only the other two lines remained to operate. This situation lasted until June 1st (till midnight) - i.e. Kilo and Sierra are working properly, Lima is broken again. It is known that during the whole consideration period (two months, between April 1st and June 1st), the average throughput of a three-channel set was 4.9159 Gb/s - i.e. a total of 2530.17 terabits (Tb) of data was transmitted between Alpha and Bravo during this time. We know that during the period when all three communication lines were working properly and full time simultaneously, the total bandwidth of the set would have been somewhat higher, 5,490 GB/s. In addition, it is known that Lima transmitted a total of 581,927 terabits (Tb) of data between the starting (after the repair) and the re-failure. By the way, Lima was started (after the repair) exactly at midnight, but unfortunately it is not known on which actual day in April it took place. We also know that Sierra had already transmitted a total of 62,300 terabits (Tb) for the moment when Kilo was started. Task: Find out when Lima broke down again as accurately as possible - in days, hours and minutes.