WEBVTT

00:00:02.100 --> 00:00:05.110 position:50% align:center size:84%
Projects change. You
need the latest files,

00:00:05.110 --> 00:00:06.930 position:50% align:center size:84%
and you may need an earlier version

00:00:06.970 --> 00:00:09.140 position:50% align:center size:84%
later. Keeping that history can

00:00:09.140 --> 00:00:12.130 position:50% align:center size:84%
mean storing the same
information again and again.

00:00:12.170 --> 00:00:14.240 position:50% align:center size:84%
GLYX Archive looks for compatible

00:00:14.240 --> 00:00:17.790 position:50% align:center size:84%
information it can reuse
across an archive, while

00:00:17.830 --> 00:00:21.260 position:50% align:center size:84%
preserving what is needed to
recover the original files exactly.

00:00:21.300 --> 00:00:24.300 position:50% align:center size:84%
Different files can
contain familiar structure.

00:00:24.340 --> 00:00:26.700 position:50% align:center size:84%
New information still
needs to be stored.

00:00:26.740 --> 00:00:28.740 position:50% align:center size:84%
For you, the benefit is more room

00:00:28.740 --> 00:00:31.660 position:50% align:center size:84%
for useful files and
older versions within the

00:00:31.700 --> 00:00:33.480 position:50% align:center size:84%
storage you already have. Where

00:00:33.480 --> 00:00:36.020 position:50% align:center size:84%
you pay for the space
retained, reducing that

00:00:36.060 --> 00:00:39.000 position:50% align:center size:84%
billable amount reduces
the storage charge.

00:00:39.040 --> 00:00:40.660 position:50% align:center size:84%
In one recorded comparison,

00:00:40.660 --> 00:00:43.710 position:50% align:center size:84%
we used a selected library
of seven hundred and

00:00:43.750 --> 00:00:45.860 position:50% align:center size:84%
forty-two files.
Counting the archive

00:00:45.860 --> 00:00:49.070 position:50% align:center size:84%
and the recorded restore
software, GLYX used

00:00:49.110 --> 00:00:53.100 position:50% align:center size:84%
about forty-three percent less
space than the same files in ZIP.

00:00:53.140 --> 00:00:55.420 position:50% align:center size:84%
Every file came back exactly.

00:00:55.460 --> 00:00:59.090 position:50% align:center size:84%
We also tested adding
previously saved content again.

00:00:59.130 --> 00:01:01.460 position:50% align:center size:84%
In that separate exact-repeat test,

00:01:01.460 --> 00:01:03.820 position:50% align:center size:84%
adding almost two
gigabytes again needed less

00:01:03.860 --> 00:01:07.500 position:50% align:center size:84%
than one megabyte of extra
archive and recovery records.

00:01:07.540 --> 00:01:11.420 position:50% align:center size:84%
The earlier archive and required
software still had to be kept.

00:01:11.460 --> 00:01:15.230 position:50% align:center size:84%
The goal is useful storage
saving with exact recovery.

00:01:15.270 --> 00:01:16.820 position:50% align:center size:84%
We compare your real data with

00:01:16.820 --> 00:01:19.820 position:50% align:center size:84%
the best practical alternative,
count everything you

00:01:19.860 --> 00:01:21.500 position:50% align:center size:84%
need to keep and run, and check

00:01:21.500 --> 00:01:24.500 position:50% align:center size:84%
that the original files
come back exactly.

00:01:24.540 --> 00:01:27.120 position:50% align:center size:84%
Bring a backup history
or a project library.

00:01:27.160 --> 00:01:31.260 position:50% align:center size:84%
Compare what you keep, what you
can restore and what you pay for.

00:01:31.300 --> 00:01:34.970 position:50% align:center size:84%
GLYX Archive. Beyond Brute Force.

00:01:35.010 --> 00:01:37.634 position:50% align:center size:84%
Reuse structure. Create more.