![]() ![]() ![]() In July 2015, the company announced updates to the Adaptive Flash platform, including Nimble SmartSecure (software-based encryption), all-flash service levels, REST APIs, InfoSight-VMVision per-VM monitoring, and integrated data protection. ![]() In November 2014, Nimble Storage released arrays supporting the Fibre Channel protocol. In June 2014, the company announced the CS700 Series Arrays and an All-Flash Shelf, along with its Adaptive Flash technology. Throughout its history, Nimble Storage introduced various product updates and expansions. In October 2013, the company filed for its initial public offering on the New York Stock Exchange and subsequently went public on December 13, 2013, under the ticker symbol NMBL. Suresh Vasudevan assumed the role of CEO, and Umesh Maheshwari became the chief technology officer. Varun Mehta served as the chief executive until March 2011 when he became the vice president of engineering. In September 2012, Nimble Storage secured $40.7 million in funding from both original and new investors, including Artis Capital Management and GGV Capital. In July 2010, the company announced its first product, the CS200 series hybrid arrays, at Tech Field Day. Nimble Storage was established in January 2008 by Varun Mehta and Umesh Maheshwari. It specializes in producing hardware and software products for data storage, particularly data storage arrays that utilize the iSCSI and Fibre Channel protocols, and includes data backup and data protection features.ĭawn at Nimble Storage's campus in San Jose, California History Hope this helps you in implementing better security measures when using Storage Integration in your Veeam environment.Nimble Storage, founded in 2008, is a subsidiary of Hewlett Packard Enterprise. Notice no ‘disconnected’ Volumes in NCM below (which would be shown with a red ‘x’ icon on the Volume instead of a green check mark) but rather only my Repo Volumes: mitigating the potential of data removal. For your Volumes used as (production) Datastore storage, they will not be shown in NCM and thus not presented to the Windows OS. For Volumes used as Repositories (if you use your Proxies like I do as a ‘combo’ Proxy/Repo box), you select to ‘connect’ those Volumes. ![]() When you configure access to your Volumes on your array, your Volumes are not shown as being ‘presented’ to the Backup Proxy. I won’t go into the full Windows Backup Proxy configuration process, but setting up your Proxies for DirectSAN/BfSS, you add the Microsoft File & iSCSI Services as a feature/role, and also install Nimble Connection Manager (NCM) and Discovery address to present your Nimble Volumes to the server. All you need to do is configure access for these Volume(s) on your Nimble array with the Proxy(ies) IQN and, configure the access on the array to apply to just “Snapshots Only”. For Nimble Volumes you use as Datastores, you do ***not*** need to present these Datastore Volumes to your Windows Proxy OS. According to Veeam’s VMware User Guide here, when configuring your Proxy for Direct SAN mode (needed for BfSS), they state “ SAN storage volumes presented as VMware datastores must be exposed to the OS of the backup proxy which works in the Direct SAN access transport mode.” I cannot speak for other storage systems/vendors, but I would hope it’s the same for them. He and I were curious if Volumes used for Datastores really needed to be presented to the Windows Proxy OS. Several mos ago, we were trying to determine how best to present production storage to a Proxy, exposing as minimal amount of Nimble Volumes to a Windows OS as possible to prevent a catastrophic event, beit admin error or mal-intent. You can view the post here. For this post, I want to continue discussing Nimble Storage Integration, but provide you a security measure you can implement when configuring your Windows Proxies for Storage Integration or Direct SAN, as Veeam requires a Proxy to be configured with Direct SAN (or ‘Automatic Selection’) when using Backup from Storage Snapshots (BfSS).Ī fellow Vanguard and I have occasional on-going discussions on how to best secure Windows Backup Proxies using Nimble (now called whatever.Alletra? □ ) for Storage Integration. I created a previous post on Nimble Storage Integration with Veeam, discussing how you can potentially recover data even if a backup job’s Deleted VMs retention setting has passed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |