Saturday (10-November-2012) — New Jersey

Technology Update: Drobo Good Bad and Ugly

I’ve had a love/hate relationship with my Drobo disk arrays ever since I got them. I have two Drobo’s, an eight disk Dobro B800i (configured with eight 2 TB drives) as my primary working array and a 5 disk Drobo S (configured with five 3 TB drives) as an offline backup. Although some glitches when setting them up, when working they are fast and have been happy. Well, mostly happy other than the >10 days it took to add more drives: see my 13-November-2011 post.

When I got back from the SAS 2012 Fall Semester voyage, I realized that my storage space was getting tight, and after the Gone to See America 2012 Road Trip/Nikonians ANPAT 12 Trip I was running out of space. The B800i drive had a message that I was >85% full, and the one of the hard drives had a yellow light indicating that it should be replaced with a higher capacity hard drive.

One of the reasons that I bought the Drobo disk arrays was that I was supposed to be able to a hot swap upgrade if I a drive went bad, or I needed to increase drive space on the disk-array. Well, the first bit of bad news I found out that if you are using a fully populated Drobo array and all of the drives are the same size, you need to upgrade with two higher capacity drives before you get access to more space. The second bit of bad news was that I got back to New Jersey just in time for Hurricane Sandy.

Since I had configured my Drobo in the default (single drive failure mode) this meant that I could only add the higher capacity drives one at a time. And each time it takes 24+ hours for the data protection to complete before adding the next drive. This gets to be a long, long process especially during Hurricane Sandy when the power kept going down. In my case the power was on and off four times over 10 days. A UPS works for a couple of hours, but not for days. As such, I ended up having to restart the data protection process several times. This was all on the Drobo B800i that was initially set up with eight 2 TB hard drives, that I wanted to upgrade to eight 3 TB hard drives.

The upgrade process on the Drobo S system populated with five 3 TB drives was more complex. In this case the system was also configured in the default mode (single drive failure). I was at the point that there was less than 10% free space, and the top drive was red – indicating that it needed to be upgraded. The availability of 4 TB hard drives is limited, but I was finally able to find some. Again, not well documented by Drobo, but you need to replace two or more drives to get more space and get back to a normal green operating space. When I replaced the “red” 3 TB drive with a 4 TB drive you have to be very patient. First it takes several minutes to indicate that the new 4 TB drive was installed, and then it takes almost half an hour to go from red to flashing green/yellow and indicate that data protection is in progress. Really bad news – 56 hours to complete data protection.

When the data completion was finally complete (less than 56 hours, but more than 36 hours), the system flashed red on the same 4 TB drive that I just replaced – indicating that the drive that I needed to replace was the drive that I just replaced. OUCH – that was the drive that I installed and waited 36+ hours for the data protection process to complete. Was the new drive bad – or was there a software/hardware problem with the Drobo S unit. Well, I took a chance (since I have 2 other on & off site copies of the data) and the unit did indicate that the data protection process was complete. I did a hot swap of the #2 hard drive with a new 4 TB drive. It took several minutes to 1) get an indication that the drive was removed; 2) many more minutes to indicate that a new 4 TB drive was installed; and after waiting for 20 minutes that the data protection process was underway (all drives flashing green and yellow). This time it indicated 69 hours to complete (dropped to 36 hours in a couple of hours). We will see in another day or two if this works.

I have been concerned about the Drobo arrays since the posts by Scott Kelby in June. As a noted Photographer, he had four Drobo disk array fail and ultimately decided on another solution for storage of his images. Right after his posts, I started getting e-mail messages from Drobo that I needed to purchase an extended warranty. Do I stay with Drobo or find a less proprietary solution? With the amount of time it has been taking me to upgrade my storage over the last couple of weeks I wonder if it is time to evaluate a Synology NAS disk array.

Sunday (04-November-2012) — New Jersey

Hurricane Sandy Aftermath: Day 6 — Power Restored

I am happy! Power to the house was restored yesterday. When I woke up this morning, power was still on and the house was warm. With the time change, the sun was just coming up through my bedroom window rather than getting up in the dark. I’m thinking of having a Sunday roast chicken dinner with lots of garlic.

With the power restored, I restarted the backup of my server and image collection. I was finally able to start reviewing and process images from the New Mexico trip. One teaser image is of Noah’s Ark from the Albuquerque Balloon Fiesta.

The Drobo disk array where I store my images started beeping. The error message told me the storage space was nearly full and that I needed to add some bigger hard drives. We will see how long this takes, and hope that the power stays on for the upgrade to process. I followed the instructions and did a hot swap of the 2 TB drive with a yellow light with a 3 TB drive. After many, many minutes I finally got a message that the new hard drive was recognized — but that the Drobo disk array will require ~38 hours for the data protection process to complete. In the mean time I am making other backups. I am looking forward to the Seagate 4 TB hard drives becoming available at a reasonable cost. With these I could double the size of my image collection.

Noah's Ark. Albuquerque 2012 Balloon Fiesta Final Day. Nikonians ANPAT 12. Image taken with a Nikon D4 and 70-200 mm f/2.8 VRII lens (ISO 100, 155 mm, f/7.1, 1/200 sec). (David J Mathre)
Noah’s Ark. Albuquerque 2012 Balloon Fiesta Final Day. Nikonians ANPAT 12. Image taken with a Nikon D4 and 70-200 mm f/2.8 VRII lens (ISO 100, 155 mm, f/7.1, 1/200 sec). (David J Mathre)

Sunday (13-November-2011) — New Jersey

Technology Update: Drobo Storage Device Restored!

I’d previously posted that it was taking a long time for my Drobo B800i storage device to update after adding two additional 3 TB drives. The update never completed (after 12+ days), and appeared to need to restart after the multiple power failure after the early snow storm (and ultimately 42 hours of outage). I finally gave up, and decided to reset the device and restore my image database from backups. For the most part this went well, just took time. However, one of my primary backup devices, a Western Digital 2 TB MyBook devices failed. During the restore process, the process stalled. At first, I thought it was an overheating problem, so let the device cool before restarting. This was repeated several times. I even used the Western Digital “Data Lifeguard” program to check the device – and the device passed with no errors. Ultimately, I got a message that I needed to format the device before I could use it. OUCH!!!

OK — no problem, I have other backups. I went to the other backup that I keep in the house, the original RAW files stored on Western Digital Passport drives. These were my original external storage devices (160 GB, 240 GB, 500 GB, 750 GB, 1 TB) that I used since I started getting into digital photography. Unfortunately, one of the drives containing the data lost on the MyBook device was not recognized. STARTING TO PANIC!! — this included images from ANPAT 9 including image from a once in a lifetime trip to Alaska.

I guess that I am paranoid about data storage. I keep three, and sometimes four backups of key data, and some of the data is stored off-site (away from home). The third backup, I keep at work. I went and picked it up this weekend (3 hour round trip) and I was able to restore the data to my primary Drobo device. I am still running a full comparison (using Program Match — 32 bit CRC mode) since some of the earlier data restored from the failed drive may have been corrupted.

The thing that I did loose was any current metadata, or processing data for the images since I was going back to the original RAW files saved from the camera.

Bottom Line — One backup is not enough!! Primary media can fail, backup media can fail (hard drives fail). Primary media can be lost (fire, theft, other disasters etc). Technology moves forward, and old backup devices become obsolete. I am currently dealing with nearly 500 K (7 TB) images, and need to future proof my storage and back-up work-flow. Need to keep all of this in focus when devising a backup storage protocol.

I plan to get back to reviewing and processing images soon, so I can share images again!!

22-October-2011

Day 5 and Counting

My Drobo disk-array is rebuilding after adding a new drive. Don’t know how long it will take. New images (including a meteor caught last night with two cameras) to follow. The down side to large storage solutions such as Drobo is the time required for backup and restore. Not sure if this will be hours or days!!!!

I did post some images on Google+ for the following themes: #SongBirdSaturday  #RuralSaturday  #SunsetSaturday  #SepiaSaturday  #SaturdayNightLight  #Caturday

For a list of all of the Daily Google+ Photography Themes

Also, check out my post from 5 years ago today of a Turkey Vulture soaring over New Jersey: 22-October-2006