If I read you right, you are running into the issue I describe. This is not allowed. If this is a VMware environment or the like you probably have to do a staged migration. Remove one host in the cluster from the IG and put it in the new one and move the devices and VMs on them to the new one and then repeat with the rest.
Are you trying to add a device that is already in a view to another view that uses the same initiator group as the first view? You can mask the same device to another host, but you cannot have two overlapping masking views that use the same device and initiator group.
Device is already in two storage groups. I have 3 masking views, For example 1mv 2mv 3mv. Initiators in 1mv and 2mv are in 3mv. I want add all the device which are in 1sg 2sg into 3sg and delte 1sg and 2sg.
Great--so you might just want to leverage Storage vMotion to evacuate a datastore of its VMs temporarily remove it from the original SG and then add it to the new one, then move the VMs back. Repeat this until all of the devices are moved to the new view.
The process you would follow for production removal and re-adding of a device would be as follows. There would be no downtime or deleterious effects to the host(s). All that is required that you have enough space to temporarily move all of the VMs off of a device.
Storage vMotion all VMs from the device you want to move to the new view
Unmount the VMFS and detach the device in the vSphere Client
Remove the device from masking view 1 and add it to the new masking view
Anonymous User
242 Posts
0
September 12th, 2013 11:00
H:\>symsg -sid 1234 -sg SG add dev -rp
The operation cannot proceed because one or more device(s) is already masked within a view
codyhosterman
286 Posts
0
September 12th, 2013 11:00
If I read you right, you are running into the issue I describe. This is not allowed. If this is a VMware environment or the like you probably have to do a staged migration. Remove one host in the cluster from the IG and put it in the new one and move the devices and VMs on them to the new one and then repeat with the rest.
dynamox
9 Legend
•
20.4K Posts
0
September 12th, 2013 11:00
try symsg -sid 123 -sg add dev ###
codyhosterman
286 Posts
0
September 12th, 2013 11:00
Are you trying to add a device that is already in a view to another view that uses the same initiator group as the first view? You can mask the same device to another host, but you cannot have two overlapping masking views that use the same device and initiator group.
Anonymous User
242 Posts
0
September 12th, 2013 11:00
Device is already in two storage groups. I have 3 masking views, For example 1mv 2mv 3mv. Initiators in 1mv and 2mv are in 3mv. I want add all the device which are in 1sg 2sg into 3sg and delte 1sg and 2sg.
Anonymous User
242 Posts
0
September 12th, 2013 12:00
All devices are in Production.
Anonymous User
242 Posts
0
September 12th, 2013 12:00
These are all for ESX hosts(UCS Chasis).
codyhosterman
286 Posts
0
September 12th, 2013 12:00
Yeah thats why you would want to use Storage vMotion to move them off the device first so there is no downtime.
codyhosterman
286 Posts
0
September 12th, 2013 12:00
Unfortunately I am not familiar enough with RP to give you anything but a guess. Hopefully someone else can chime in on that.
Anonymous User
242 Posts
0
September 12th, 2013 12:00
These are all in Production. If i remove a device from storage group host will be having issues.
codyhosterman
286 Posts
0
September 12th, 2013 12:00
Great--so you might just want to leverage Storage vMotion to evacuate a datastore of its VMs temporarily remove it from the original SG and then add it to the new one, then move the VMs back. Repeat this until all of the devices are moved to the new view.
codyhosterman
286 Posts
1
September 12th, 2013 12:00
The process you would follow for production removal and re-adding of a device would be as follows. There would be no downtime or deleterious effects to the host(s). All that is required that you have enough space to temporarily move all of the VMs off of a device.
Anonymous User
242 Posts
0
September 12th, 2013 12:00
I have guess
Devices in storage group has tagged with recover point and its in replication. This may cause anything
Anonymous User
242 Posts
0
September 12th, 2013 13:00
I am getting error when i add ports to a port group
H:\>symaccess -sid 1234 -name PG -type port add -dirport 3g:1
A specified device is involved in a Remote Copy session and cannot be modified
Anonymous User
242 Posts
0
September 12th, 2013 14:00
i have listed those devices they are in replication and esx storage group