16.01.2013 Views

1EQQ8ZzGD

1EQQ8ZzGD

1EQQ8ZzGD

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

up errors properly (a full disk situation was masking them,<br />

if my memory serves), our validation software also wasn't<br />

dishing up errors properly (that was written very hastily, and<br />

without a clean state to start from, was missing several important<br />

error conditions), and several other factors were compounding<br />

our lack of concrete, verifiable information.<br />

The only prospect then was to roll back about two months<br />

to the last full backup that we thought might work. In that<br />

meeting, Galyn mentioned she might have a copy at her<br />

house. So we went home to get that machine, and you can<br />

watch the video for how that went . . .<br />

With Galyn's machine now back in the building, we duped<br />

that data immediately, then set about the task of trying to<br />

verify and validate this tree, which we thought might be about<br />

two weeks old. We compared Galyn's restoral with a much<br />

older one (from two months prior) and couldn't determine<br />

a clear winner, there were too many inconsistencies. So, instead,<br />

we set about the task of assembling what effectively<br />

amounted to a new source tree, by hand, one file at a time.<br />

The total number of files involved was well into the six figures,<br />

but we'll round down to 100,000 for the sake of the rest<br />

of this discussion to make the math easier.<br />

We identified the files that hadn't changed between the<br />

two, and took those straight away. Then there were the files<br />

that were on Galyn's but not on the older one; we took Galyn's<br />

and assumed they were new. Then there were files that were<br />

on the older one but not on Galyn's; we put those in the "hand<br />

check" pile, since it is unusual for files to be deleted within a<br />

production source tree, and we were suspicious of those deletions.<br />

Then there were the files that were different across the<br />

two backups, those also went into the "hand check" pile along<br />

with any files that were touched more recently than Galyn's<br />

version.<br />

Given that, we had something like 70,000 files that we felt<br />

good about, and we poured those into a new source tree. For<br />

the remaining 30,000 files, it was all hands on deck.<br />

We checked things across three partially complete, partially<br />

correct trees . . . the two month old full backup (A), Galyn's<br />

(B, which we thought was the best one), and another<br />

cobbled together tree (C) from the stray files left around from<br />

249

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!