Protection: What type of fault tolerance does each array have or can have, how fast are their rebuilds? Do they use spares or distributed sparing (there isn't a wrong answer here, just know what you are looking for).Īre the controllers active/active or active / passive? (front end and back end, not all controllers work the same). Snap Shots (but what kind, do they need to be writeable? Can you use a snap to refresh a test/dev database?) One word here, FC backend went the way of the dodo bird about 10 years ago it's all SAS or NVME today. Next Feature set: Figure out what features you need, vs desire. Don't work with guessers, they haven't earned your business. The detail they should have for each of these, at a min, is as follows:įailure to have this data, means whoever you are speaking to is just guessing. At a min each vendor you work with should investigate, find and size for:
Nimble san visio how to#
They all have their pros and cons, and you are bound to like one of them for "reasons" you can't explain, so instead of telling you why one vs the (besides the fact that would be totally biased) let me give a few suggestions on how to choose one:įirst: Make sure your vendors are sizing / solving for your workload. Between Dell, Pure, Nimble and even netapp it really is a buyers market. You are actually at a really good time to be looking at storage as their really are great options on the market. Hope this helps you in implementing better security measures when using Storage Integration in your Veeam environment.\disclaimer - Dell peon: Obv Bias is Obv* 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.
Nimble san visio windows#
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.
Nimble san visio install#
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 kommentar(er)
