AnsweredAssumed Answered

Connecting a Nimble Volume via Powershell

Question asked by Amanda Crisp on Dec 29, 2015
Latest reply on Jan 6, 2016 by Raj Chelur Siddalingaiah

I'm a bit of a newbie to both powershell and Nimble.

However.

I'm a DBA charged with getting backups, and we don't have room on the production SAN.  We're completely virtualized.

We *are* replicating to a DR site where we have room.

 

Our working theory is that I will write a script to create a clone from the latest snap and present it to the DR SQL server where...and then I have any number of options because once I get the .ldf and .mdf files I'm confident I can do whatever I want.

I'm relatively comfortable getting around in the Nimble GUI, and I've performed all of the above steps several times for quick restores.  I can script out the dispart stuff. 

 

I am using Justin Rich'sPowerShell Module , and I have the cloned volume showing up on the correct server but I can't figure out how to attach it.  The iscsi targets all have such long complicated names, and don't look like they are consistent.

Justin Rich

here's what I have now, and it gets it there but doesn't connect it:

 

Connect-NSArray -SystemName 10.20.30.40 -Password Beer

 

Get-NSSnapShot -volume 'serverdb' | select -First 1 | New-NSClone test

Add-NSInitiatorGroupToVolume -Volume test -InitiatorGroup 'DRServer'

 

Now I'm stuck.  It shows up with an x in the Nimble GUI, and I don't want to crash the whole VM by using the wrong commands.  Can anyone tell me what I'm missing?

 

Additionally, we're using commvault, so I'm wondering if there aren't Commvault commands which can interact directly with the snapshots?  That seems way easier.

Outcomes