User Volume cannot be accessed by RPA

Question

I am trying to replicate VMS from Site A to Site B. Each Site has its own VCenter. Site A has VirtCenter A registered to it and Site B has VirtCenter B registered to it.

I am getting multiple error messages like this ERROR: User volume [Test Group, Test Server, CG_RSET_TestWindows2008Server_0_0_scsi] cannot be accessed by: RPA 1

What does that mean and what do I need to do to correct it?

forshr · Accepted Answer

This message appears because it takes some time for us to provision the replica and journal volumes and establish the shadow VM. Until this is done the splitter can’t access the replica volumes and this message appears. What we need to do is tailor the message accordingly.

Regards,

Rich Forshaw

RecoverPoint Corporate Systems Engineering

k_williamson · Answer

Apparently, my error went away on its own.  When I start to replicate a VM, it goes to init appears to go 100%, then it errors and the cycle repeats itself for a long while.  then it goes active.  I am still confused on how to the process is supposed to look and if things are correct on my end.

echolaughmk · Answer

Hi,

I have seen the same thing and upon investigation and a case with EMC for another issue, this was confirmed a known process/working flaw. Pretty much any task that will operate on the underlying constructs in RP4VMs will generate these transient errors in the web client and refresh/go away on their own. I see this every time I create a CG, disable/enable protection, even failovers and cleanup. It seems that the web client isn't masking out these transient errors and as long as they don't go away in 5 minutes or so and don't linger, they can pretty much be ignored. If it is a real issue...it will persist

I mentioned this to product mangement as well, but not sure what any future fixes/filtering might be applied in future releases.

-K

k_williamson · Answer

The error messages I see do concern me.  When I added protection to another VM, it errored about the access to the Journal volume and then it went away in a few minutes.  I think when I added another CG, it made another Journal Volume and it wasn't created yet.  After a few minutes, the messages went away and it started initializing.  I might have to start treating the error messages like I do for the UCS.  If it is still there after a few minutes then, it is important.  I just think it needs a little more smarts in it so we wouldn't see as many errors.  Like don't try to use the Journal Volume till it has been created.

echolaughmk · Answer

Yeah - your thought process on letting them work it out for 5 or so minutes is what I have been adopting for my installs and if they persist past 5 or so minutes, then I start to get concerned

RecoverPoint

User Volume cannot be accessed by RPA

Was this post helpful?