- #Nimble san visio how to
- #Nimble san visio install
- #Nimble san visio full
- #Nimble san visio Pc
- #Nimble san visio professional
This discussion takes place from July 20th - August 1st August 7th. Most recently he was with Nimble storage where he served as an Escalation Engineer helping high profile accounts resolve performance problems that were introduced by poor VDI, Network and Virtualized designed environments. Previously, he was with a Reseller for 3 years supporting a multitude of storage and backup products including EMC, HP, Hitachi, Commvault and SE - EMCĭeny joined the EMC team with over 15 years of experience in Cloud Computing, Virtualization, Storage and Networking in wide variety of Pre-Sales and Engineering roles.
#Nimble san visio full
John prior to EMC was with NetApp for 6 years functioning as a Principal Solutions Architect focused on design and implementation of the the full NetApp solution stack supporting various applications such as Oracle, Vmware, and Microsoft. Strong background in UNIX system administration and NAS.
#Nimble san visio professional
Jim is an IT Professional for over 20 years, including 15 at EMC. To get started, check out the Top 10 Tips & Tricks for XtremIO document that we featured at EMC World.ĭirector, Global Systems Engineering - EMC Our panel of technical experts will share best practices of configuration, operation and management, and will be here to answer your specific questions.
#Nimble san visio how to
For two weeks, beginning July 20 th, our panel will show you how to make the most of your XtremIO system. Hope this helps you in implementing better security measures when using Storage Integration in your Veeam environment.Welcome to an all new YOU MAY ALSO BE INTERESTED ON THESE ATE EVENTS.Īsk the Experts: EMC Isilon technical content and documentationĪsk the Expert: Best Practices – 7.x Installation and UpgradeĮMC Community Network Ask the Expert conversation. 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.
#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. I just replaced our old Nimble CS260G SAN with a Nimble HF40, entirely new config and everything. I believe the default Nimble IP is 192.168.1.200.
#Nimble san visio Pc
Then set your PC to a static IP on the 192.168.1.0/24 subnet. You might want to factory reset it first. 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”. If I remember right there is a reset button on the controllers. 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)
