The WTC towers were constructed to withstand a 1970s jet (707, DC-8, etc) that was on approach to JFK/LGA, hence at low speed and not full of fuel. This was not the scenario on 9/11.
The fact that as a customer that is impacted by this, I only found out about it when my backups and automated test restore failed is worrying.
I get that things happen, but not realising that this was going to be a service impacting event does not inspire continued confidence. Sure, this situation probably won't happen again, but what else don't they understand about their infrastructure?
It looks to me that their US10 is not like an AZ but an actual server with bunch of HBA and disks. So very much pets and not only in a single location but possibly in a single rack or even box.
You are (maybe) protected against a few disk failures but that's about it.
(off topic) I promised to reply to you in another thread, but I can't because replies are locked. feel free to reach out to me if you want - my contact is in my profile
Not OP, but I would guess it's something like this:
1. Make a e.g. 30MB file of random data
2. Copy it to "_reference" file
3. Upload the file to backup service
4. Restore the file from backup service
5. Diff restored file against reference
Pick a couple random files that should be in the repo, restore them from a random archive, check the md5sums against the source. If the md5sums don't match (or the file can't be found), something is wrong. I am mainly backing up RAW image files, so they should never change.
I don't use borg, but I used duplicity, which offers something like that. The verify operation simulates a backup restore to compare whether the restored file's checksum matches that expected from the metadata and optionally against the local file. I use this routinely, interesting to see that a local S3 provider can sometimes mess up your files silently.
If I were a gazillionaire, this would be my yacht. Updated (sympathetically) to modern standards and efficiency, and open to the public as a museum ship when not in use.
Their biggest miss was not hitting the fuel dumps and repair facilities. Taking out a few ships, even carriers, would be easy to replace. Wiping out the logistics support capability would mean that ships would have to return to the US west coast to refuel/repair.
That would have been a major disaster. Pearl Harbor was just an irritant and catalyst.
First of all, take a look at the map [1] of Perl Harbor from wikipedia. The oil storage tanks are listed as A, and you'll notice that they formed two different groups. By my count each had 27 tanks. If you take a look at [2], you'll see that these tanks were well separated, with an earth wall between them. It is clear that when they were built precautions were taken to prevent the spread of (accidental of intentional) fire.
So, taking out the oil tanks was not as simple as dropping one bomb. You probably needed multiple passes. After the first successful pass, all others had to deal with the smoke, and more or less guess where their targets were. Of course, they would have to deal with the anti-air defenses. The second wave already took quite heavy losses, the third wave was guaranteed to incur much heavier ones.
Let's say in the best case scenario, the hypothetical third Japanese wave would have destroyed half of the 54 oil tanks. It would not have made a difference. Only a success rate of 90% would have, maybe.
In any case, that third wave was never planned. See [4] (written by one of hte co-authors of Shattered Sword) for convincing evidence that only 2 waves were planned, and Admiral Nagumo carried them as per the plan.
A small country can't fight an entire continent with abundant resources and free market economy, the rest is just details. Russia is about to find this out the hard way. If Russia had a market economy, maybe different, but then they would have less interest in trying to conquer people they can just trade with.
If someone has physical access to my encrypted Mac with a password, what am I worried about more than a stolen device? Sure it’s a headache. But I have insurance.
Washington state's Department of Natural Resources have published a batch of high-resolution LiDAR images.
These are stunning visuals of the topography, and they have very thoughtfully provided a series in 16:9 format, perfect for desktop wallpaper (Flickr link to albums in the main post).
