Skip to main content

Migrating to a NAS (Part 2)

| Mark Matheson

With a new NAS and hard drives sitting on the floor of my office, it was time to start implementing it.  One of the key reasons for buying a NAS was to consolidate all my existing data from several machines and externals hard drives onto a single server, thereby increasing access speed and reducing duplication.  A review of my current hardware revealed that I was going to have to do a lot of data transfers.

Author Bio

Mark Matheson

Business Consultant
Mark has specialised in ACCPAC accounting software for over 30 years and more recently has been providing IT Managed Services to his clients. When he's not working, Mark can be found loitering on the side of a hockey field.

Key Points

  • Easy to administer once configured
  • Build RAID arrays takes time
  • Read the manual first!
8930
Hits

Along with numerous external hard disks, a hardware audit had identified the following drives in my network: -

  • 2 x 2TB Seagate drives, in use in my SBS Server
  • 2 x 1.5TB Samsung drives, in use in my Media Centre

Synology provides several options for data protection.  Not surprisingly, RAID1, RAID5 and RAID10 were on the list, but there are two other options that were attractive.  These are: -

  • SHR - Single disk protection, where the RAID is protected by a single disk equal in size to the biggest available disk.
  • SH2 - The same as SHR but utilising 2 disk for protection, thereby increasing the level of protection

The plan was to do the following: -

  • Install the NAS with the 2 x 3TB drives implemented in SHR
  • Transfer the data from the SBS Server
  • Install the 2 x 2TB drives from the server, and increase the size of the volume
  • Transfer the data from the Media Centre
  • Install the 2 x 1.5TB drives from the server, and increase the size of the volume

So, after reading the instructions (that alone was unusual for me), i powered up the NAS, installed the 3TB drives, and installed the Desktop System Manager (DSM) on the newly create 3TB volume.  After completing the wizard, the NAS was up and running with a Fixed IP address and accessible from the network.  Now to start the transfers ...

Two days later ...

I was still going with step one on the transfer process.  During the process, I had identified over 1TB of duplicated data.  This was mostly music and movies, but it reduced the clutter significantly, and also meant that my music, photos and videos were now all in one place.  But with the SBS Server now clear, it was time for me install the 2TB drives into the NAS and increase the size of the volume.  And it was here where things came unstuck!

It turns out, and this is NOT made obvious in the instructions or in the wizard, that you cannot increase the size of a volume with drives smaller than the smallest existing drive in the volume.  This meant, I could not use the 2TB drives in the existing volume.  And to complicate things further, if I wanted to use the 1.5TB drives, I really needed to have started with them.  So, a new plan was required.

My revised plan was now: -

  • Add the 2TB drives as a basic RAID (no data protection)
  • Transfer the data from the Media Centre onto the new volume
  • Install the 2 x 1.5TB drives from the server, and create a third volume
  • Transfer everything from volume2 onto volume 3
  • Increase the size of volume3, using the 2TB drives

So, I started the transfer from the Media Centre, and it is here where I encountered the second sticking point.  Despite having a Wireless N router and a Wireless N card in the Media Centre, the transfer of 2.8TB was estimated to take over 13 days.  No way I had that much patience.  Thankfully, I quick visit to my local component supplier and a 15M CAT6 cable dropped that estimate to 2 1/2 days.  The downside is, I now have an ugly blue cable taped to the walls and secured across the stairs.  A small price to pay I guess.

Three days later ...

The data from the Media Centre has now been transferred, and I thought I would do a backup before increasing the size of the volume.  And this is where I encountered a third issue with the NAS, one that still exists today, almost 4 weeks after completing the process.  The backup software provided with the NAS is very poor, does NOT compress the data, and even with several USB drives plugged in, does not seem to be able to complete two consecutive backups with one of he drives failing to be recognised.

So, holding my breath, I decided to increase the size of the volume without a backup.  Thankfully, the volume survived what turned out to be a 3 DAY process.

But, finally, I had a NAS with all my data on it, free space to burn, and two volumes, one for storage and one for TV recording.

Summary

If anyone is preparing to start a similar process to me, there are several things to be aware of: -

  • Make sure you start your volume with the SMALLEST drives you are likely to use, as you will not be able to increase the size of the volume with any drives smaller
  • Be prepared for problems with the backup software.  I am still investigating the use of CrashPlan (my online backup solution), and while I have the software, am yet to configure it
  • Do not try and do large data transfers across a WiFi connection
  • External USB drives will be frustratuing to use, even if they are on the compatability list.

The next blog will discuss the software I installed, and how the NAS changed my thinking on certain business solutions that I use.

No thoughts on “Migrating to a NAS (Part 2)”

Hi! My name is Mark Matheson and I look forward to helping you unlock the full potential of your business.

Why not subscribe to our newsletter.