How To

What’s on your Drobo?

Updated 1/14/19: I have revised my opinion of Drobo devices. After experiencing multiple, serious data loss events on multiple Drobo models, even recent ones, I no longer consider them safe for my data.

The folks at Data Robotics put together a short video that showcases Drobo owners talking about what they store on their Drobos, and asked their Twitter followers what’s on their units.

That got me thinking about what I store on my Drobos. I have four Drobos in total: three 1st Gen Drobo units (USB 2.0 only) and one 2nd Gen Drobo (Firewire 800 + USB 2.0). Perhaps that makes me a bit unusual. Most people have one or two units, not four. But there’s reason to the seeming excess.

For one thing, I have a huge photo library. (You can find the photos I edited and published here.) For another, my wife and I have a huge video library. These are movies and cartoons we had on VHS tapes, which we digitized, or on DVDs, which we archived for easy viewing, or TV shows and movies that we recorded from TV. We’re big fans of classic movies and cartoons from the 1920s, 30s and 40s, and we collect all the ones we like. We also digitized most of our old paperwork. My medical records are all digital. So are my dental records. So are a bunch of our other documents. I scanned all the stuff I could scan, and now when I need to look something up, it’s right there at my fingertips. I’ve also started shooting video more intensively this past year, in SD and HD. (You can find my published videos here or here.) All that stuff takes a fair amount of space — terabytes to be more precise. And to top off this whole list, we live our life on two continents (North America and Europe).

Here’s what I do to make sure I don’t lose my data:

  1. I keep a Drobo with my parents, at their place. On it, I store a backup of my photo library and our video library, along with their files. I back up my live photo library to it using CrashPlan, a piece of software that will let you back up your data to a friend’s machine. I’ve actually just started using it, and while I’ve been able to back up just fine with both machines on the same network, being able to do it from thousands of miles away will be a litmus test of the software’s capabilities. I’ll be sure to write about it if it proves workable. The video library gets backed up every once in a while in a pretty simple manner: I carry movies and videos to them on a hard drive and copy them onto the Drobo. Updated 4/21/10: CrashPlan does indeed work as advertised!
  2. I keep two Drobo units at our home. On one of them, I keep our video library, and an extensive, historical file archive. On another, I keep a mirror copy of my live photo library, which is currently stored on a WD Studio drive, because it’s smaller and easier to transport than a Drobo, and I do a fair bit of traveling. I mirror my photo library with an app called Synkron, which works great. I switched to the WD Studio when I started traveling extensively and realized the Drobo couldn’t always fit safely into my luggage. (Where oh where is that Drobo carrying case I wrote about last year?)
  3. I gave the fourth Drobo to my brother, who needed a solid data storage device to begin to archive his ever-growing library of ethnological videos. He’s a documentary filmmaker who travels around Romania studying and recording religious and secular customs, which are being forgotten and buried along with the old folks. He wants to preserve these things for posterity. You can learn more about what he does at his website, called ORMA.

So that’s how I use my Drobos. However, I’ll have another logistical issue to deal with in the near future. I’m running out of space on the WD Studio drive, which has 2 x 1 TB drives in it. I run it in RAID 1, and in another month or two, it’ll be completely full. I’ll need to start using one of my Drobo units as my primary photo editing/storage device again. This means I’ll shuffle all my data around once more. A possible new arrangement will see me using the 2nd Gen Drobo for the storage and editing of my photos and videos, and the other for the storage and retrieval of our video library and historical file archive, while the WD Studio drive will see some backup duty or be relegated for travel-only purposes.

The current drive distribution among the three Drobos I use actively is as follows:

  • 2 x 2 TB drives + 2 x 1 TB drives in the Drobo that stays with my parents
  • 4 x 1 TB drives and 4 x 500 GB drives, respectively, in the two Drobos that are with us
  • I can’t speak for my brother, but I believe he’s using 4 x 1 TB drives in his Drobo

I’d love to hear how you are using your Drobo. Perhaps you have some ideas for me?

Image and video used courtesy of Data Robotics. The 2nd Gen Drobo is available for purchase from Amazon or B&H Photo. The 1st Gen Drobo has been discontinued as of 2009. Be sure to also check out my reviews of the Drobo S, DroboPro and DroboElite.

Standard
How To

The garden shed

We’ve recently finished putting together a “severe weather” garden shed in our yard, made by a company called Arrow. We wanted a model that could withstand hurricane-force winds, since we live in South Florida, where hurricanes do occur from time to time. The particular model that we purchased was the Homestead 10′ x 8′ (HS108). We filmed our progress along the way (it took 1½ months from beginning to end), and you can see the video below.

The process of selecting and getting the garden shed approved and built highlighted several areas of concern when it comes to the manufacturing, retail and inspection aspects of this particular model. It all turned out to be more involved and more costly than we thought. It certainly was an adventure in do-it-yourself construction.

Watch video on YouTube (parts 1 and 2) | blip.tv

We looked for guidance from our city (Hollywood, FL) when we made the decision about what garden shed to get, but they were not helpful. All they told us was that many of the sheds sold at local building stores may not be approved for use and may not pass the inspections, and that we needed a product approval sheets for the shed.

We went to Home Depot looking for sheds, but we thought the pre-assembled ones they had on display were flimsy and might not withstand strong winds. Then we went to Lowe’s looking for a shed, found one made by a company called Arrow, only to be given the run-around when it came to the product approval sheets. The store clerk thought they were on the Lowe’s website. They weren’t. The management thought the Contractor Services department had them. Perhaps they did, though we couldn’t get them to help us. Then we tried the Arrow website, where they should have been listed alongside the shed specs. They weren’t.

Fortunately (or perhaps unfortunately), we did find a particular model on the Arrow website, called the Homestead, rated for “severe weather” and engineered for the Miami-Dade county building code, which is stricter than what we have in Broward county. That meant it was sure to be approved for use here, and would pass the inspections if assembled correctly. The price was much higher than we thought though (about $1,700) for a pre-fab, un-assembled shed that came in two flat boxes and was only 10 feet by 8 feet (80 sq ft). Still, I remembered seeing a Homestead model at Lowe’s, so we went back to check. To our surprise, it was on sale for a little under $500. We thought ourselves in luck, but the clearance price should have raised a red flag for us. We bought it, knowing we’d at least have no problems getting it approved with the city.

Sure enough, it was approved, and the time for the initial inspection came. The clerks at Lowe’s told us we’d need to pour a six-inch concrete slab. Fine, no problem. Wrong. According to the building inspector, the engineering plans for the shed (put together by Arrow to supposedly comply with the Miami-Dade building code) required a house-sized foundation, which meant digging a trench all around the edge of the foundation that was 1 foot wide by 1 foot deep, with a 45-60 degree slope on the inner lip, using re-bar around its perimeter, not just wire mesh, and naturally filling it all up with concrete. That more than quadrupled our original estimate of the amount of concrete that we needed to purchase. We thought 1 pallet would be enough for a 6-inch slab. We ended up buying over 4 pallets of concrete (almost 5) in the end.

Forget the clearance price! The ridiculous foundation requirements in effect raised the price of the shed to well over its original retail price once again!

I have to lay the blame for this squarely in Arrow’s lap. After all, they were the ones who hired an engineering firm to put together the plans for the shed, and to get them approved with Miami-Dade. I sincerely doubt there’s anything in the Miami-Dade building code that specifies one must have a house-sized foundation for a flimsy pre-fab shed. That makes no sense whatsoever. All other sheds on the market do just fine with a 4-6 inch concrete slab, yet this model, which is shorter and smaller than the rest, somehow needs a house-sized foundation? No way. Someone was careless or fearful when they drew up the plans, and the customers are now paying for it!

I might have been more lenient in my overall view of the shed, had it proven sturdier during the assembly and in the final review. But it’s just as flimsy and cheaply made as the rest of the pre-fab garden sheds on the market, many of which come pre-assembled and cost a third of this shed’s original retail price. There’s nothing to set it apart for me from the rest, other than the presence of extra wall beams at waist height, and the lack of a need to use hurricane anchors to strap it to the ground once it’s assembled. The sheet metal used for its walls and doors is just as cheap and easily bent or dented, the doors open and close just as badly as on other pre-fab sheds, and to top it all off, it’s so darn short I bang my head on the lintel every time I go in and out!

Oh, and lest I forget, let me mention that Arrow forgot to provide the sufficient number of bolts and nuts needed to assemble the shed properly. We were delayed by a day during the assembly process because we needed to make a trip to the store to get some more hardware, which should have been included with the shed to begin with. On the bright side, they did include the Hilti anchors needed to anchor the shed to the concrete foundation, though I expected to need to get those myself.

Yes, the shed is now fully assembled, approved, and we’re using it. But it proved to be much more expensive in the end than it should have been, it took much more time and effort to get the project completed, and in my eyes at least, it wasn’t really worth all that. Imagine how those people who bought this shed at its original retail price felt! They must have felt they were ripped off royally. Thank goodness we at least got it at clearance price.

The City of Hollywood could also have been more helpful when I called them asking for guidance on garden sheds. Instead of dismissing me with some generic advice, they could have said, hey, here’s one of our building inspectors, talk to him and he can recommend sheds that he knows will get approved, cost less, and take less time to put together. While I understand that a government employee can’t recommend specific brands and models, at least I could have gotten helpful advice that could have saved us money, time and effort. Instead, the City of Hollywood was the only city in Broward County to raise property taxes this year, during a big recession, making me wonder exactly what we’re paying for, if they’re not helpful to us, its residents.

All I can say is this shed better hold up when the next hurricane comes, or Arrow will hear from me again.

Standard
How To

Are you really backing up your WP blog?

When those of us with self-hosted WordPress blogs back up our content using the built-in WXR functionality, do we ever check the downloaded XML file? Until recently, I didn’t worry about it. I’d click on the Export button, copy the WXR file to a backup folder and think my blog was safe, but I was wrong.

You see, what may be happening is the creation of the WXR file on the server side may be terminated before all the content gets written to it, and we’ll end up with a partial backup of our blogs. This is no fault of the WordPress platform, but will happen when the server settings don’t allow enough resources to the PHP script which writes out the XML file. When that’s the case, this is what the end of the WXR XML file looks like.

In the screenshot you see above, the script ran out of memory (I’d set PHP’s memory_limit at 64 MB, which was too little for my needs), but it can also run out of time, if PHP’s max_execution_time is set too low.

Depending on your scenario, you may or may not have access to the original php.ini file on your web server. If not, check with your host, you may be able to create a php.ini at the root of your hosting account to adjust these parameters (within limits). The thing to do is set the memory_limit and the max_execution_time high enough to allow PHP enough resources to generate the full WXR file. I can’t prescribe any specific limits here, because the amount of memory and time the script needs depends on how big your blog is. All I can suggest is that you experiment with the settings until they’re high enough for the WXR file to generate fully. You don’t want to set them too high, because your server will run out of memory, and that’s not fun either. This is what my setup looks like.

What happens if you use a cheap web host is that you’ll get crammed along with hundreds of other sites on a single virtual server where all the settings are tightly reined in, to make sure no one’s hogging any resources. Chances are that as your blog grows, your WXR file will get too big and will need more resources than are available to write itself, which means you’ll start getting truncated backup files. If you never check them by opening up the XML and scrolling to the end to rule out any error messages, you’re not really backing up your blog.

Keep this in mind if you want to play it safe. Always check the WXR file. A good backup should close all the tags at the end, particularly the tag, like this screenshot shows.

Standard
How To

The cat house – part 8

This is part eight of a personal carpentry project whose stages were recorded on video: building a cat house for our two kittens. Here are the other parts:

In this post, you’ll see the finished cat house, hear a bit more about the thinking behind the project, and find out my final opinion about what I’ve built. At this point, the cat house is pretty much complete, although a couple of small touches — like a frame around the window and a rubber door at the entrance — still need to be done. This means there will be a part 9 at some point in the near future, likely within the next 1-2 months.

As mentioned in the videos and in one of the first parts, the cat house was built using both leftover and reclaimed wood and thermal insulation. Pretty much everything I used in its construction I already had lying around my yard from ongoing renovations to our home. The only things I bought specifically for it were the two casters, the asphalt roof tiles, and the wood screws, which added up to a cost of 100 RON or about $33.

See this video on blip.tv, SmugMug or YouTube.

Standard
How To

The cat house – part 7

This is part seven of a personal carpentry project whose stages were recorded on video: building a cat house for our two kittens. Here are the other parts:

In this video, I’ve already completed all of the carpentry work and the cat house is assembled. It’s also been stained and it’s about to be treated with wood wax. Lots of details about what’s been done and what’s about to be done are offered in the video, such as what I’m going to do about the entrance and how the roof has been mounted and how it seals against heat loss.

See this video on blip.tv, SmugMug or YouTube.

Standard