Thursday, 20 October 2011

“To The Cloud…”


For the last year or so, it seems marketing people have moved away from terms such as “... as a Service”, and replaced the words with Cloud.

We are seeing hosted applications, hosted infrastructure, hosted servers, hosted platforms, managed services, VPNs, MPLS networks, distributed networks, hosted virtual servers, remote VDI solutions, all termed with the phrase Cloud.

I understand the drivers that are used to move services out of your own server room, by lowering infrastructure costs, moving capital expenditure to operational expenditure, upgrading or downsizing by modifying your service plan, removing running costs (such as air conditioning, trained server administrators, etc.), having your systems monitored and changing applications on the fly.

I have a few issues with Cloud offerings, which include:

Authentication
  • How do users connect to the solution? 
  • Are they using a username and password?  

There are many issues around authentication, such as weak or insecure passwords, using common words, using easy to guess words (such as favourite bands, football teams, children’s names, car, etc.) and that’s before the fact the password can be told to someone else. 

People often talk about multi-factor authentication, but to surmise it, the factors are “something you know” such as passwords and PINs, “something you’re given” such as a one time passwords from a token, or “Something you are” where biometric devices are used to read fingerprints or iris scanners.

A combination of two of these will be known as two factor authentication, where passwords are coupled with a token generated one time password, offering much improved security.

Encryption
  • How is your data protected?
  • Who has access to your data?

With the Information Commissioner’s Office issuing fines of up to £500,000 for the loss of personal data, it is more critical than ever data is encrypted. 

I would expect the data to be encrypted with to a minimum level of 256-bit AES, although another consideration who has access to your data.  It may be encrypted, but if the key is held by the service provider, then they will have the ability to decrypt your data.

Backup and Archive
  • Is the data backed up?
  • Is the data archived?

Your data should be backed up regularly, giving a point in time that the data can be restored to.  The issue with back up is that it will back up current data, but the ability to roll back and restore can be more destructive and time consuming than working round the missing/lost/corrupted data.

If your data was archived, then it would offer the ability to manage and archive all versions of the data.  Archiving is driven by compliancy and traceability, rather than disaster recovery.

Access to the service
  • Where can you access the data from?

It would be great to be able to access your service from anywhere in the world, wouldn’t it?  A concern is that although this great for remote users, should everyone be able to have access?  Data security may dictate that the service or data should not be access from non-trusted IP addresses, or by specific users or during specific times.  If this level of control is required, ensure your provider is able to deliver this.

Disaster Recovery
  • Are there multiple servers hosting your service?
  • Are there multiple datacentres hosting your service?

One of the draws with a Cloud offering include having your applications and services available from anywhere, so there perfect disaster recovery solution.

The issue will be when the provider has a server failure.  Will they be able to move your service to a new server in a timely fashion?  Whether the services are being run on virtual or physical servers, ensuring your service up time is vital. 

Another concern will be if the provider only has one datacentre or one WAN connection, so if there service is delivered well I would expect multiple datacentres, with multiple links running an active/active configuration, along with an active/active or active/passive server configuration.

Conclusion
My concern with Cloud solutions is the number of providers who are “jumping on the bandwagon” offering cloud services as quickly as possible.  The issue is that some providers offer very favourable pricing, but the infrastructure may not be in place until there is some uptake.  This can only be a bad thing for the early adopter, especially if it is not making money and they stop the service or become bankrupt.

My advice is to proceed with caution, check the provider thoroughly and try not to be price driven.

Thursday, 23 June 2011

Drobo Dashboard v2.0.2 is now available

The new Drobo dashboard is available, which has a much slicker look and feel compared to the previous version.  The image below is taken from the Drobo.com website:

AllDevicesPage.jpg

The new dashboard allows you to manage multiple Drobo devices, rather than just one device with the previous version.  The only shortcoming is that from my netbook, the whole interface can't be displayed on my 1024 x 600 screen, as the bottom is cropped.  This has been reported to Drobo and I expect this to be resolved in a future release of the dashboard.

The downloads are available here: http://www.drobo.com/support/updates.php

Sunday, 22 May 2011

DroboApps and Firefly iTunes server

After following the instructions on the DroboApps website: (http://www.drobo.com/droboapps), I installed Apache and the DroboApps Admin Utility.

Using the DroboApps Admin Utility, I installed the Firefly application. I then changed the server name and the default password, and I was up and running.  Browsing to the DroboApps share, I dropped my music into the media folder within the Firefly folder.

The only issue was that my iTunes could not see the shared library!  A bit of searching found this Apple support article: http://support.apple.com/kb/TS2972

It seems that my software firewall was not allowing TCP port 3689 and UDP port 5353. Once opened up, iTunes instantly found the shared library.

All my music is currently being moved off my netbook, into the secure and resilient environment of the Drobo.

- Posted using BlogPress from my iPhone

Saturday, 21 May 2011

Introduction to DroboApps

There is a strong community of developers, creating applications for the Drobo devices.  The applications are called DroboApps, and the download files can be found here: http://www.drobo.com/droboapps/

Being new to DroboApps, I went against my technical gut instinct, and read the manual!  There is a very useful document highlighting how to install DroboApps, along with some installation examples: http://support.datarobotics.com/app/answers/detail/a_id/468

Having enable the DroboApps functionality on the appliance, I had a look through to see what I need to download, along with what I wanted to download.

Going through the DroboApps, I downloaded the following:
  • DroboApps Admin Utility
  • Apache (required for the admin utility)
  • Firefly (iTunes library)
  • Fuppes (Media server with DLNA support)
  • Lighttpd (HTTP server)
  • Pure-ftpd (FTP server)
As mentioned previously, the reason Drobo caught my attention previously, was the fact I could have more just two hard drives in an appliance, and that it could be my iTunes library.

DroboApps Admin Utility, Apache and Firefly will be installed soon.  I will document and review the features then.

Thursday, 19 May 2011

Introduction to the Drobo Dashboard and Configuration

The hardware was very easy to put together, and the software was just as simple to set up.  There are a lot of screenshots here, but you can see it was pretty much a case of "next, next, next" to get the dashboard installed.  Once installed, you will have the dashboard up and running.

1. Once the Drobo Dashboard software is installed and running, it is looking for Drobo devices.


2. The Drobo device is detected, but at this point my device was still starting up.


3. Clicking on the "Advanced controls" and looking at the "Data" tab, I can see what is in the device and it has correctly identified my four 1TB 3.5" SATA hard drives.


4. The "Tools" tab, offers a number of commands, alert settings, device settings and updates.


5. The dashboard shows how much free space I have and the shares available.


6. Expanding the "How is my storage being used?" shows more drive information.


7. As I selected the option to check for updates, this box somes up.


8. Clicking on the highlighted option to change the Admin password, shown in images 6 & 7 above, brings up the "Admin" under the settings.  There is also an option to enable DroboApps (which I plan to investigate more in the future)


9. By default, the Drobo device will protect your data in the event of one hard drive failing.  There is a option to enable dual disk redundancy, which will protect the data in the event of two drives failing.  It does use more hard disk space, but I guess it depends how important you data is.  As my device will be holding family photos and my MP3s, I will be enabling the dual drive redundancy.


10. On the "Network" tab, the network settings can be configured.  I will be setting this to match my internal network.


11. On the "Shares" tab, shares and users can be created.  By default, you have one share called "Public" and the administrative user called "Admin" by default.


13. On the "Email Alerts" tab, the email server information can be configured.


As you can see, the software interface is clear and concise.  Lots of features are available and seems much easier to configure that my existing NAS device.  Now the device is on my network, I will be investigating more about DroboApps.

Introduction to the Drobo FS

I had a surprise at work today, as a box was left on my desk.  Drobo kindly shipped a Drobo FS to me to test and use.

At e92plus, we have just started distributing the Drobo range of products and like any technical person, the technology interested me, but hands on experience with a product is much more fun!

A number of things drew my attention to the Data Robotics (Drobo) range of drive enclosures, even before we signed them up to distribute their products.  I was aware that different makes and sizes of hard drives could be used within one enclosure.  This goes against the things that I have learnt about RAID technology and have been using for over 17 years, but then again RAID is over 25 years old!!

I was also aware that some of the Drobo range would allow applications (Drobo Apps) to be run on the device, so it could be a web server, FTP server, iTunes server, etc.

There was a boast that it was easy to set up without the complex configuration normally associated with RAID systems.  I think I had a head start as I have worked with RAID for a number of years, as well as already owning a Netgear NAS appliance at home.  I've been looking to replace this with a device that support the storage of an iTunes library, which my current device does not do.

After plenty of research, I came to the conclusion that I need a Drobo FS at home, and all of this was decided before I was even aware of it at work.  It was good to see that something I had researched a while ago was not only good enough for home, but have a number of devices suitable for business uses.

Here's the box that arrived today:




The box contained a number of items:
  • Drobo FS Device
  • Drobo FS User Guide
  • Drobo Resource CD
  • Straight Ethernet Cable
  • AC Adapter
  • Power Cords (UK & European)
The device is very attractive, metal chassis and a plastic front bezel, held on with magnets.  It has a very good blend of aesthetics with a quality/sturdy build quality.  It felt very solid compared to the my existing NAS appliance.




The instructions on the box were very straight forward:


  1. Install Drobo Dashboard from the Drobo Resource CD
  2. Insert at least two 3.5" SATA hard drives, metal side up (Note: Any data on the drives would be wiped)
  3. Connect an Ethernet cable and the AC adapter, then follow the dashboard instructions






I had four 1TB SATA hard drives spare, so this is what I'm using as part of this test.

Software installation to follow in the next post: