Problems using RSM

[Paul Hall_1]

We just got our EVA 5000 operational. I've been trying to setup a script inside RSM to make a snapshot of a LUN and present it to a different box. I keep getting an error saying it can't locate the volume. (see attached screenshot) I also tried pointing it to the volume on the target host and when I ran the script that time I got a commandview error. Any ideas?

[Metadata]

Hi Paul,

Can you please state which type of Operating System you are trying to mount the snapshot to? Also can you please specify what type of HBA's you are using in the server?

Tom

[Ivan Ferreira · Accepted solution]

It seems that there is something wrong with your vdisk name. In the log you get:

"\\EVACSUMB\FIRSTCLASS\FIRSTCLASS email"

Is this vdisk name correct, the space between firstclass and email? If you have sssu, can you post the ouput of show vdisk full?

[Paul Hall_1]

I changed the name on the volume in question to troubleshoot the space issue to just FC.

[Paul Hall_1]

both hosts are running 2k3 SP1. Both are using qlogic HBA's. The target host is a HP BL25p. The destination I'm trying to mount it to is a DL 380 G2

[Ivan Ferreira]

Sorry, I think that what is wrong is the command syntax.

ValidateHostVolume receives as argument the operating system disk device, not the eva disk device, like this:

AIX
ValidateHostVolume ("\\HostA2\/home/cats")

HP-UX
ValidateHostVolume ("\\HostA2\/users/cats")

Linux
ValidateHostVolume ("\\HostA2\/var/cats")

Solaris
ValidateHostVolume ("\\HostA2\/usr/cats")

Windows
ValidateHostVolume ("\\HostA2\E:\pets\cats")

See the RSM online help for more information.
So, you must change your definition of $source_hostvol_unc1

[CSUMB Network Operation]

interesting I was using the pre-populated template which apperantly generated the wrong syntax I'll play with the output now that I know what it should look like.