Nimble Storage have released their newest addition in the line up, the SFA, or to give its full name, the Secondary Flash Array. And in this post, we are going to look at how to set one up from scratch.
Taken from the following datasheet;
The Nimble Secondary Flash Array represents a new type of secondary data storage optimized for both capacity and performance. It adds high-performance flash storage to a capacity-optimized architecture for a unique backup platform that lets you put your backup data to work.
The Nimble Secondary Flash Array is optimized for backup, disaster recovery and secondary data storage. By using Flash, it lets you put your backup data to work for Dev/Test, QA and analytics. Instantly backup and recover data from any primary storage system. And our integration with Veeam backup software simplifies data lifecycle management and provides a path to cloud archiving.
Before you get started
As you can imagine it’s as easy as setting up one of the existing Nimble Arrays, as I blogged about previous (Setup via GUI, via CLI). Actually the configuration via CLI is the exact same!
First things to note; the SFA ships with the NimOS 4.x, which is now HTML5 based, and there is extra port requirement for access if you have a firewall or a web proxy in the situ, TCP 5392, which is used for RESTapi access. In my testing, I found that the Sophos web filter that was setup in transparent mode, caused issues with my login page on the Nimble, when I removed it from the equation, I noticed my Firefox gave me a pop-up window as per the below.
How to setup the array – initial configuration
- Launch the Nimble Setup Manager, this can be downloaded from https://infosight.nimblestorage.com
You’ll see below I actually used an older version, and it still worked fine discovering the array. When you click next, you’ll be presented a dialog box explaining that your default browser will be launched to continue the setup (as part of the new HTML5 interface).
- Accept the certificate error, as the Nimble uses a self signed cert on the web interface
Continue reading Setting up a Nimble Secondary Flash Array from scratch
So it’s just been a little over a year since Part 4 of my how to document series was posted. I hoped to keep adding to the series, but at the same time, only do it when I felt I had relevant content to share. So this post is to show how I have documented some recent backup configurations. Note: I mainly work with Veeam, but hopefully this will give you idea’s of how to present the setup of your other backup software
Below are the previous posts;
Note: The Visio file for these examples can be found at the end of the blog post.
Your backups evolve over time, as does your environment. Your backup schedules become more complex, and its hard to remember, what does what.
As past of my job, I setup backup solutions for customers, and then have the task of documenting how they are setup. I used to do this in a table format. It was quite simple
- Backup/replication job name
- Services backed up
- Job settings
When you have a number of backup jobs, you have a lot of jobs and information to dig through. Its not user friendly.
So I re-visualised the way to present the data, I still have the detailed tables, however I also have three Visio diagrams
- Backup Architecture setup
- Backup and Replication jobs – Servers/services included
- Backup and Replication job settings – high level
Continue reading How to produce good documentation – Part 5 – Diagraming your (Veeam) Backups
So the last time I used a Nimble Device, I had to configure it (quite easily) using the CLI first due to connectivity constraints at the customers site.
However here is how to configure a Nimble in 4 easy steps ready for production use.
So unbox, rack and cable up your Nimble device to the network, then;
1. Load the “Nimble Setup Manager” which can be downloaded from Nimbles website. Search for your Nimble on the Network (Obviously be in the same VLAN!).
– Click on your Array and then Next
2. Enter your basic network settings and click next.
4. Accept the EULA, and you are done, you can now connect to you Nimble and setup the Production side of things, which is basically the same as this article.
Nice and short