WEBVTT

00:00:00.030 --> 00:00:06.029
it's 3:00 in the morning and you can't sleep so the natural response is of

00:00:03.449 --> 00:00:10.679
course to bust out your phone and waste some time on Reddit get to swiping on

00:00:08.220 --> 00:00:15.120
tinder or blow a few more dollars on that freemium game that's quickly

00:00:11.969 --> 00:00:17.730
becoming a real problem and luckily for

00:00:15.120 --> 00:00:22.410
you all of these services work without a hitch because they're all being provided

00:00:19.650 --> 00:00:27.269
to you from huge data centers that are expected to be reliable no matter how

00:00:24.869 --> 00:00:34.140
many people are connected or what time of day it is but how do they stay

00:00:30.449 --> 00:00:36.480
running with almost no downtime well our

00:00:34.140 --> 00:00:40.739
friends at IBM sponsored this video to tell you guys all about it and it starts

00:00:38.610 --> 00:00:46.800
of course with having facilities and computers that are purpose-built to

00:00:43.260 --> 00:00:48.809
handle lots of incoming connections now

00:00:46.800 --> 00:00:54.000
although some services have their own data centers many others who either

00:00:51.420 --> 00:00:59.070
don't need or can't afford a dedicated facility or need additional capacity

00:00:56.699 --> 00:01:04.580
actually rent server space and processing time from a larger companies

00:01:01.739 --> 00:01:10.439
a strategy called colocation data centers are typically made up of lots of

00:01:07.650 --> 00:01:15.299
servers sitting in racks to maximize how many machines can fit into one bit of

00:01:12.600 --> 00:01:19.380
floor space but of course setting up a data center is a lot more complicated

00:01:17.400 --> 00:01:24.000
than just throwing a bunch of servers into a warehouse and calling it a day

00:01:21.990 --> 00:01:28.140
larger data centers hold so much equipment that they are actually built

00:01:26.130 --> 00:01:33.140
to be sturdier than your average building to accommodate all the extra

00:01:30.810 --> 00:01:37.770
weight from these large racks of servers some of them are so large that the

00:01:35.909 --> 00:01:42.240
workers inside are even given small vehicles like scooters or bicycles so

00:01:40.650 --> 00:01:48.540
they can get around and troubleshoot issues more quickly also those servers

00:01:45.090 --> 00:01:50.939
generate a ton of heat so elaborate

00:01:48.540 --> 00:01:55.920
cooling systems including water chilling are often employed additionally data

00:01:53.640 --> 00:02:01.200
centers are often laid out to be more efficient for example servers will

00:01:58.170 --> 00:02:03.869
usually either face toward each other or

00:02:01.200 --> 00:02:10.679
directly away from each other to create what are called corridors of hot air

00:02:07.020 --> 00:02:12.390
that can be pushed out more easily but

00:02:10.679 --> 00:02:17.700
when there's an environmental hazard that isn't can huge problems can result

00:02:15.329 --> 00:02:22.980
for example a few years ago Facebook actually had weather in the form of

00:02:20.340 --> 00:02:28.230
clouds inside one of its data centers which caused some of the equipment to

00:02:25.200 --> 00:02:30.659
short out so humidity control can also

00:02:28.230 --> 00:02:35.609
be very important for larger operations some servers are even designed to

00:02:33.090 --> 00:02:40.590
withstand even more serious hazards like earthquakes using braces and extra floor

00:02:38.519 --> 00:02:44.879
mounting so of course data centers are protected with advanced physical and

00:02:42.540 --> 00:02:50.459
human security but what about the more technical challenges well aside from

00:02:47.719 --> 00:02:56.790
encrypting it data is often kept safe by spreading the processing and storage

00:02:53.639 --> 00:02:58.680
across multiple locations rather than

00:02:56.790 --> 00:03:03.599
having them just on one single machine in one place to make this simpler

00:03:01.139 --> 00:03:08.969
servers are very often virtualized meaning that one physical server can be

00:03:06.180 --> 00:03:12.629
seen as several different systems this is incredibly useful because it allows a

00:03:10.769 --> 00:03:17.970
much greater number of tasks to be performed by one server and that's

00:03:15.090 --> 00:03:21.930
really important for colocation so as long as each virtual machine is

00:03:19.979 --> 00:03:26.370
separated well enough from the others this can even bolster security load

00:03:24.659 --> 00:03:30.389
balancing is another technique that ensures that servers are being used

00:03:28.349 --> 00:03:35.819
efficiently I mean you don't want a situation where some of the servers are

00:03:32.819 --> 00:03:38.459
getting slammed with requests and extra

00:03:35.819 --> 00:03:43.319
processing while others are sitting idle like that kid who contributed nothing to

00:03:40.919 --> 00:03:47.970
your group projects back in school so instead servers are often configured to

00:03:45.959 --> 00:03:53.069
have their workload and their data balanced more evenly between them this

00:03:51.030 --> 00:03:58.469
prevents overloading of certain machines and bottlenecks this is also often done

00:03:56.250 --> 00:04:01.590
automatically in cases where one server might need to be taken down for

00:03:59.879 --> 00:04:06.109
maintenance so that whatever it was working on can just be picked up by

00:04:03.569 --> 00:04:12.030
other servers in a similar vein redundancy is a critical feature of any

00:04:09.419 --> 00:04:18.030
modern data center copies of data are usually kept on multiple servers or even

00:04:15.150 --> 00:04:22.590
across multiple data centers and these facilities often have multiple pipelines

00:04:20.269 --> 00:04:27.220
leading out to the public Internet in case one Internet service provider has a

00:04:24.840 --> 00:04:31.680
problem so all this means that enterprise-grade data centers are

00:04:28.780 --> 00:04:38.800
designed for at least 99.999 percent uptime which works out to

00:04:35.620 --> 00:04:41.200
about five minutes of time offline per

00:04:38.800 --> 00:04:46.510
year some of them are actually even more reliable than that and while websites

00:04:43.570 --> 00:04:51.880
and online services do obviously go down sometimes it really is amazing how much

00:04:49.540 --> 00:04:57.460
has gone into making sure that we can access nearly anything nearly any time

00:04:55.300 --> 00:05:02.170
like if only everything in your life was that dependable right again this video

00:04:59.860 --> 00:05:05.890
is brought to you by IBM did you know that resiliency is the most important

00:05:04.090 --> 00:05:09.040
facet of your data center I mean you can have all the speed performance and

00:05:07.570 --> 00:05:15.940
features in the world but if your servers are down who cares IBM Z has the industry-leading

00:05:13.870 --> 00:05:21.160
resiliency needed to ensure that your bottom line doesn't suffer from planned

00:05:18.280 --> 00:05:25.150
maintenance or unplanned downtime your whole data center could go up in flames

00:05:22.720 --> 00:05:29.230
and your recovery could happen without a hitch when it comes to continuous

00:05:26.919 --> 00:05:34.510
availability IBM Z customers achieve five and six nines so that's ninety nine

00:05:32.320 --> 00:05:40.090
point nine nine nine and ninety nine point nine nine nine nine percent or

00:05:37.210 --> 00:05:44.979
greater uptime and they say the smaller IBM Z footprint can essentially replace

00:05:42.280 --> 00:05:49.510
as many as 100 servers so reduced downtime scaled to support large

00:05:46.900 --> 00:05:54.130
workloads and get peace of mind with IBM Z the leader in data center technology

00:05:51.720 --> 00:05:57.070
so thanks for watching guys like dislike check out our other videos leave a

00:05:55.720 --> 00:06:00.280
comment if you have this suggestion for a future fast as possible and don't

00:05:58.750 --> 00:06:03.760
forget to subscribe because even the most reliable data center can't give you

00:06:02.020 --> 00:06:06.210
a notification if you're not subscribed Kenneth