{"id":27006,"date":"2022-10-11T10:36:23","date_gmt":"2022-10-11T17:36:23","guid":{"rendered":"https:\/\/www.podfeet.com\/blog\/?p=27006"},"modified":"2022-10-11T10:36:23","modified_gmt":"2022-10-11T17:36:23","slug":"drobo-died-again","status":"publish","type":"post","link":"https:\/\/www.podfeet.com\/blog\/2022\/10\/drobo-died-again\/","title":{"rendered":"The Day the Drobo Died \u2026 Again"},"content":{"rendered":"

A Walk Down Memory Lane<\/h3>\n

Over the years I\u2019ve regaled you with tales of our various network-attached storage (NAS) devices. Steve and I use our NAS for storing sensitive financial data that we don\u2019t want to be stored in the cloud, along with hosting our PLEX video library Steve has ripped from our DVD\/Blu-Ray collection of over 300 films.<\/p>\n

I also keep backups of various podcast creation files. For the most part, I could live without those podcast files but every once in a while I found a reason to go back to the archives to recover something.<\/p>\n

Our first NAS Experience \u2013 Drobo<\/h3>\n

Our first NAS was a Drobo FS which is known in NAS lore as the slowest network-attached storage device ever known. It technically stored data, and it was technically on the network but it was nearly unusable.<\/p>\n

A few years later we upgraded to a Drobo 5N which was a huge improvement. We found we were using it more and more. Drobo let me test out AND keep a Drobo 5N2 which was a slight improvement over the 5N<\/a>.<\/p>\n

Using a NAS allows you the luxury of having mirrored drives, so you can lose an entire drive and all of your data is still safe. The NAS, in theory, will rebuild itself, creating yet another spare if there\u2019s room enough. If you pop in a replacement drive, the NAS will rebuild to use the new one.<\/p>\n

This data redundancy means you\u2019re protected from the single most likely failure – that of a single hard drive. The next most likely failure is of the entire NAS itself. While a good vendor may help you recover from a failure like that, it\u2019s a world of hurt.<\/p>\n

With the \u201cfree but you have to buy the disk drives for it\u201d Drobo 5N2, I was able to back up the 5N2 to the 5N.<\/p>\n

This didn\u2019t protect us from the third most likely failure – a fire\/flood\/earthquake\/theft from our home. I\u2019ll get back to that scenario a bit later.<\/p>\n

Synology Joins the Family<\/h3>\n

In June of 2020, I wrote an article entitled, \u201cThe Day the Drobo Died \u2026 and Synology Joined the Family<\/a>\u201d. I was kind of happy the Drobo 5N finally died because I\u2019d really been envious of those who had moved on to Synology’s NAS offerings.<\/p>\n

While Drobos do what they say on the tin, apps on the Drobo never really took off. It was a place to store files and nothing much more. Synology devices, in contrast, come with a bunch of fun apps built in, and they opened up to allow third parties to write apps and developers hopped on in droves.<\/p>\n

When the older Drobo died, I bought a Synology DS1019+. The 19 in the model number means the model came out in 2019, and the 10 means it can have up to 10 drive bays. It comes with 5 drive bays but you can double that with another piece of hardware. The plus seems to have some vague meaning like, \u201cyou are more than just a home user, maybe a small business user, but you\u2019re not a rack-mount kind of person.\u201d<\/p>\n

Synology has been a great deal of fun over the last two years. The apps are delightful and I\u2019ve learned to do so many nifty things like creating Docker containers, making my non-HomeKit devices become HomeKit-compatible, and more.<\/p>\n

The one thing I couldn\u2019t easily do was back up my Synology to my Drobo. No software apps I could find would allow one to talk to the other. My solution, in the end, was to use a Mac mini running Carbon Copy Cloner to back up from the Synology to the Drobo.<\/p>\n

It was a good solution because we never bothered to populate the older Drobo with as much disk space as the new Synology, and Carbon Copy Cloner allowed me to exclude things from the backup. For example, we store sparse disk bundle backups of our computers right before a nuke and pave on the Synology. These are just a belt and suspenders backup and don’t need to be backed up again to the Drobo.<\/p>\n

Bankruptcy!<\/h3>\n

This setup of using a Drobo as a backup to a Synology has been humming along relatively smoothly for the last two years. And then in June of this year, Drobo and its parent company filed for bankruptcy protection<\/a>. While this doesn\u2019t necessarily<\/em> mean the end of Drobo, it certainly isn\u2019t the sign of a healthy company. The probability of getting continued support is looking pretty grim.<\/p>\n

<\/p>\n

\"Drobo
Drobo Bankruptcy Petition<\/figcaption><\/figure>\n

<\/a><\/p>\n

In September I received an email from Drobo entitled \u201cDrobo macOS Ventura Compatibility\u201d. It said:<\/p>\n

\n Thank you for entrusting Drobo with your critical data. We have found that the upcoming macOS Ventura update is currently incompatible with Drobo. We cannot guarantee compatibility with future OS updates. Therefore, if you are planning on upgrading your macOS we highly recommend backing up data that resides on your Drobo to mitigate any unknown impacts of incompatibility.\n<\/p><\/blockquote>\n

The Drobo software has always been a janky weird thing, and more recent versions of macOS have been sending dire warnings about how the technology Drobo Dashboard uses is being deprecated and will stop working soon.<\/p>\n

This message from Drobo is a responsible thing for them to do, but it also sounds like they don\u2019t have the staff to find out whether this is the version of macOS that will kill it, and clearly are not working on a modernized version of Drobo Dashboard.<\/p>\n

If they don\u2019t have the staff to find out and fix it, then I don\u2019t have confidence that I should keep using the Drobo 5N2, even as a backup for another NAS. It would be irresponsible of Steve and me to move our Macs to macOS Ventura and just roll the dice and find out if it works.<\/p>\n

And that\u2019s why this article is entitled, \u201cThe Day the Drobo Died \u2026 Again\u201d. It was time to buy a second Synology.<\/p>\n

A New Synology DS1522+<\/h3>\n

Choosing a new Synology<\/h4>\n

When I\u2019m choosing a new Synology, I always turn to Steven Goetz. I don\u2019t know how he knows so much about the product. Even before he bought his own, he seemed to be very well-versed in the mire of different options Synology offers. He helped me pick out my DS1019+ two years ago, so I turned to him for my new purchase.<\/p>\n

\"Synology
Synology DS1522+<\/figcaption><\/figure>\n

This time it was easier to choose. We picked the DS1522+<\/a> which is the natural evolution of my current Synology. The 15 means it can have three sets of 5 drive bays, the 22 means it\u2019s the 2022 model, and again the \u201c+\u201d means it\u2019s for my kind of need.<\/p>\n

I should mention that I don\u2019t really need to be able to expand with more drive bays. When I needed to expand my storage last year<\/a>, the cost of adding a new bank of drive bays was far more than replacing the existing drives with higher-capacity drives. I think the ability to add more drive bays is for people who have already populated their existing bays with the highest-capacity drives and still need more space.<\/p>\n

The other thing that made it an easy decision was that the DS1522+ is the only Synology with 5 drive bays. You can get 4 drive bays in several models but 5 is unique. I like 5 because essentially one drive is always wasted in order to have the data replication with Synology Hybrid RAID (SHR), so you always have 4 drives worth of usable storage.<\/p>\n

Buying Drives<\/h4>\n

With the decision on which Synology to buy taken care of, it was time to make disk drive decisions. Here again, Steven Goetz is pretty knowledgeable and good at doing research. He has confessed that one of his favorite hobbies is helping other people spend their money.<\/p>\n

My current Synology has 3 4TB drives, and I replaced the other 2 with 2 8TB drives. Using Synology\u2019s RAID calculator<\/a>, that should give me an effective 20TB of space using SHR (Synology Hybrid RAID).<\/p>\n

\"Synology
Synology RAID Calculator Showing 28TB Turns into 20TB Usable<\/figcaption><\/figure>\n

When I needed to add storage last year, it really made me sad to throw drives away. This time, I decided that instead of populating every drive bay with the size that I needed now, I\u2019d instead buy 3 much larger drives, leaving 2 bays open. The cost works out more favorably now even if I never need to increase storage.<\/p>\n

Steven and I settled on Western Digital Red Pro drives (the Pros have a 5-year warranty). To achieve an effective 24TB of storage, I could buy 4 8TB drives for $880, or I could buy 3 12TB drives for $810. I actually save<\/em> $70, and I still have 2 drive bays open for future expansion. This again is an advantage of the 5-bay DS1522+.<\/p>\n

Where to Buy the Drives<\/h3>\n

You\u2019d think I was ready to fire up my Apple Card to make some purchases, but you\u2019d be wrong. Dave Hamilton on the Mac Geek Gab is crazy smart about Synology and NASes in general and offers some advice on buying drives.<\/p>\n

He points out that if you buy all of your drives at the same time from the same place, they\u2019re very likely to be from the same lot. If they\u2019re from the same lot, they have a higher probability of failing close in time to each other. All drives fail, but you sure don’t want them failing at the same time.<\/p>\n

While I really like to have all of my purchases in one pile at Amazon, I do like to spread the wealth from time to time, so I bought my previous and this new Synology at B&H Photo<\/a>. The DS1522+ is $700 everywhere so you can choose where to buy. I asked B&H chat if there was a way to buy the three drives from different lots, but they didn\u2019t have any way to do that. I bought one drive from B&H, one from Amazon, and one from Adorama. They were all the identical price with free shipping. I will be putting stickers on each one so that I know which vendor to contact if one of the drives fails!<\/p>\n

But Before I Migrate\u2026 I Must Diagram!<\/h3>\n
\"Diagram
Crude Start of a Diagram<\/figcaption><\/figure>\n

Before I start any kind of migration, I had to make a diagram. I know, you\u2019re shocked. I wanted to make sure I had documented what I currently have to be sure not to lose anything in translation. The Synology has more disk space on it than the Drobo, so not everything on the Synology gets backed up.<\/p>\n

I diagrammed how many of which kinds of disks I have in the two NAS devices, and how full the two devices were. I also documented my Carbon Copy Cloner settings so I was certain I understood which of the file shares was backed up and what exclusions there are in each of the shares.<\/p>\n

By documenting it in this way, I could see that some of the shares aren’t necessary to preserve, because they existed purely for experimental purposes. Might as well clean things up before migration. I still need to diagram what services I have running that I truly need to keep. I experiment a lot, so I’m expecting to do a fair bit of cleanup there as well.<\/p>\n

Another benefit of diagramming my current setup is that it will give me a reference to verify that the migration is successful. I want to make sure the data is there, of course, but also all of the tools I’ve installed and configured on the Synology.<\/p>\n

Migration Process<\/h3>\n

With purchasing and diagramming out of the way, there\u2019s still a lot more to figure out. I\u2019m not actually done yet with the planning.<\/p>\n

I could simply remove the Drobo from the network, drop in the new Synology and tell Carbon Copy Cloner to back up from the old to the new Synology. That would seem to be the easiest path but would realize the least benefit from spending $1600 on a new NAS with 24TB of effective storage.<\/p>\n

Another option would be to drop in the new Synology, tell Carbon Copy Cloner to clone from the old to the new, and then simply reverse the path of cloning so the new one is the one in charge. That would also be pretty easy with a slight gain in speed with the newer Synology.<\/p>\n

As I was rolling these ideas around with Steven, he pointed out that while Carbon Copy Cloner can easily keep the data synced over, it knows nothing about the users, the apps, and the settings I\u2019ve meticulously curated on the Synology.<\/p>\n

He explained that Synology has a tool called Migration Assistant. It provides the same functionality as the same-named macOS tool. The documentation for the Migration Assistant package installer says:<\/p>\n

\n Migration Assistant seamlessly migrates data and system settings from your old Synology NAS to a new one, while ensuring maximized service availability.\n<\/p><\/blockquote>\n

\"Synology
Synology Migration Assistant<\/figcaption><\/figure>\n

I found a video tutorial by Synology<\/a> that walks through the process of moving from one Synology disk station to another, and it\u2019s pretty straightforward. I am still really glad I watched the video first. There are quite a few little points made in the video that will make the process easier and less error-prone. I’m going to watch it again and take notes the second time through.<\/p>\n

Now that I understand how to make my new Synology look exactly like my old Synology using Migration Assistant, I still have many unanswered questions:<\/p>\n

    \n
  1. When Migration Assistant finishes, will I have two identically-named devices on my network? Will their only difference be their IP addresses?<\/li>\n
  2. After Migration Assistant runs, it disables all services on the old Synology so that should help things, but what\u2019s to keep us from accidentally storing new files on the old Synology?<\/li>\n
  3. My end goal will be to have the new Synology back up to the old Synology.\n
      \n
    1. Do I just want to back up my data?<\/li>\n
    2. Do I maybe want a full clone? Is that even possible?<\/li>\n
    3. Do I want an encrypted backup?<\/li>\n
    4. Do I want to move my old Synology to my buddy Ron\u2019s house a couple miles away so it\u2019s technically offsite even though the same earthquake\/flood\/fire might take out both of our houses?<\/li>\n
    5. Is it possible to do a backup over the Internet to his house?<\/li>\n
    6. If it is at his house, wouldn\u2019t I want it encrypted? Is that possible?<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n

      So many questions!<\/p>\n

      No Bottom Line Yet<\/h3>\n

      I like to end my articles with the bottom line, but with that many unanswered questions, I can\u2019t do that yet. The good news is that I clearly have hours and hours of entertainment awaiting me when that final disk drive arrives. It\u2019s going to be a blast figuring all of this out and learning new things. I\u2019ll be sure to let you know what I learn.<\/p>\n

      Also, if you\u2019ve done this kind of migration yourself, or if you have two Synologys in two different locations backing up to one another I\u2019d love to hear about it. Maybe you\u2019ve got lessons on what to do, or more importantly what not<\/em> to do. I can\u2019t wait to get started! This is going to be fun!<\/p>\n","protected":false},"excerpt":{"rendered":"

      A Walk Down Memory Lane Over the years I\u2019ve regaled you with tales of our various network-attached storage (NAS) devices. Steve and I use our NAS for storing sensitive financial data that we don\u2019t want to be stored in the cloud, along with hosting our PLEX video library Steve has ripped from our DVD\/Blu-Ray collection […]<\/p>\n","protected":false},"author":1,"featured_media":26999,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[147],"tags":[63,228,5521,5520,3623,1102,1249,1250,1248],"class_list":["post-27006","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog-posts","tag-backups","tag-drobo","tag-ds1019","tag-ds1522","tag-migration","tag-migration-assistant","tag-nas","tag-network-attached-storage","tag-synology"],"jetpack_featured_media_url":"https:\/\/www.podfeet.com\/blog\/wp-content\/uploads\/2022\/10\/Drobo-RIP.jpg","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/27006","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/comments?post=27006"}],"version-history":[{"count":3,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/27006\/revisions"}],"predecessor-version":[{"id":27014,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/posts\/27006\/revisions\/27014"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/media\/26999"}],"wp:attachment":[{"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/media?parent=27006"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/categories?post=27006"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.podfeet.com\/blog\/wp-json\/wp\/v2\/tags?post=27006"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}