Unsolved
This post is more than 5 years old
16 Posts
0
704
July 29th, 2008 11:00
Following errors occurred while starting SAN Copy Sessions:
Platform: CX3-40, Linux RHEL4, FLARE 24
I thought I had SAN Copy working properly.... I successfully set up an Incremental copy and completed the Initial Copy. I went back today to try an incremental and the following error was returned:
Following errors occurred while starting SAN Copy Sessions:
- Error occurred while Starting "Gold_SANCopy": This command was sent to the SP that does not own the lun (0x71008043)
The only powerlink hit I can find states the following:
This code means that a SnapView command was sent to a non-owning storage processor (SP).
But, it does not provide a solution. I cannot control which SP the SAN Copy is issued to, can I?
Thanks
Sarah
I thought I had SAN Copy working properly.... I successfully set up an Incremental copy and completed the Initial Copy. I went back today to try an incremental and the following error was returned:
Following errors occurred while starting SAN Copy Sessions:
- Error occurred while Starting "Gold_SANCopy": This command was sent to the SP that does not own the lun (0x71008043)
The only powerlink hit I can find states the following:
This code means that a SnapView command was sent to a non-owning storage processor (SP).
But, it does not provide a solution. I cannot control which SP the SAN Copy is issued to, can I?
Thanks
Sarah
No Events found!
gusgelpi
2 Posts
0
July 29th, 2008 11:00
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
July 29th, 2008 11:00
dynamox
11 Legend
•
20.4K Posts
•
87.4K Points
0
July 29th, 2008 11:00
change ip address to either SPA or SPB and wwn for source or target LUN WWN. Check logs to see if connectivity was verified.
SLRobb
16 Posts
0
July 29th, 2008 12:00
SLRobb
16 Posts
0
July 29th, 2008 12:00
60:00:00:blah blah -log"
change ip address to either SPA or SPB and wwn for
source or target LUN WWN. Check logs to see if
connectivity was verified.
It is reachable by both SPA and SPB.
The SP owner had been changed. It was changed back, and now it is working properly.
Thanks again for your help.
SLRobb
16 Posts
0
July 30th, 2008 07:00
3CsForumModerat
24 Posts
0
July 30th, 2008 08:00
This a known issue that is currently being worked on. See the announcement at:
http://forums.emc.com/forums/ann.jspa?annID=213