UNSOLVED

davei0595

updated

12 years ago

D

davei0595

13 Posts

0

27005

June 27th, 2014 02:00

EQL Powershell - RPC failed

Hi

I'm trying to use EQL Powershell tools (ASM PS tools actually) to recover replicas of volumes at a DR site.

I have two EQL groups - one in primary, one in DR.  Vols are replicated - VMFS, NTFS for SQL and fileserver.

I am testing recovery of an SQL server.  We use SRM to bring the VM up and reconfigure it, no problem.  VM has two vNICs connected to the ISCSI network at DR site, so it can see the DR equallogic group.  IP connectivity is there.

I can use ASMCLI to recover a volume, that is tested and works fine.

I would like to use powershell though as I need to do lots of other things of course as part of recovery an powershell is my tool of choice!

So from powershell, I can connect to the DR group fine (connect-eqlgroup -address x.x.x.x).  I have my ps credentials listed in ASM/ME.

When I try to run a command against the group, I get the following error:

C:\> connect-eqlgroup -groupaddress x.x.x.x

Successfully connected to the group 'xxxx'

C:> mount-asmsmartcopy -objectname -document="Collection{SQL_Coll_DB1}\a9fd6e88-8204-449c-aca8-3908def8d961.bcd -location "R:"

mount-asmsmartcopy: The remote procedure call failed. (Exception from HREULT: 0x800706BE).
At Line:1, char:1.

I can wrap some powershell round the ASMCLI commands if needs be. But any ideas why i'm getting this RPC error with the 'native' cmdlets?

Thanks.

Dave

 

 

 

  • Joe S586

    9 Technologist

    •

    729 Posts

    432

    0

    Posted June 27th, 2014 07:00

    Can you confirm what FW version is running on the group or what version of ASM/ME you are using, but with the latest versions of ASM (4.x and above) try using this syntax instead:

    asmcli -mount -document="Collection{SQL_Coll_DB1}\a9fd6e88-8204-449c-aca8-3908def8d961.bcd -location "R:\"

    -joe

  • davei0595

    13 Posts

    432

    0

    Posted June 30th, 2014 02:00

    FW is 7.0.5.

    ASM is 4.7 on 2008 R2.

    ASMCLI works fine.  It is the equivalent powershell cmd-lets that produce the RPC error.

    I'm wrapping the asmcli commands in a powershell script as I have other things for the script to do too.  It would have been nice to use the ASM cmdlets such as mount-asmsmartcopy, for one-liners rather than having to call asmcli.exe and parse output etc.

    Any advice would be great.

    Cheers