Recovery Manager Central
1755443 Members
3404 Online
108833 Solutions
New Discussion

HPE RMC and Concurrent discovery limit of 16 reached for StoreOnce

 
SOLVED
Go to solution
TechEvangelist
Occasional Advisor

HPE RMC and Concurrent discovery limit of 16 reached for StoreOnce

Hi Community Members,

We have following setup in our organization to replicate 3PAR VVOL to  HPE StoreOnce 5660 via RMC 6.3.9-2149.2.

We have Copy Policies applied to 18 distinct VVOLs inside RMC . We have a 18 volume sets for each VVOL imported into RMC via 3PAR. Previously,  They would start every Wednesday at 19:00 for a snapshot and every Thursday at 19:00 for express protect. Then, we came across this error during Create Express Protect 

Concurrent discovery limit of 16 reached for StoreOnce. Waiting for a copy to finish.
Backup operation failed.
Error Code RMC - 4008
Message Failed to attach resource to the data mover.
Details Failed to attach snapshot(s)to StoreOnce data mover storeonce.domain.com with error: Volume 'rmc-0017879-ro-220609200008981' could not be found..

I then staggered the execution of express protect of 17th and 18th volume set an hour later i.e. 20:00 every Thursday instead of 19:00 same day.  Again , there is same error;

2022-06-09 20:00:17 - Initiating backup.
2022-06-09 20:00:21 - Starting NATIVE backup with source connectivity: FC
2022-06-09 20:00:21 - Submitting backup job to discovery queue.
2022-06-09 20:01:22 - Concurrent discovery limit of 16 reached for StoreOnce. Waiting for a copy to finish.
2022-06-09 21:00:23 - Concurrent discovery limit of 16 reached for StoreOnce. Waiting for a copy to finish.
2022-06-09 22:00:24 - Concurrent discovery limit of 16 reached for StoreOnce. Waiting for a copy to finish.
2022-06-09 23:00:25 - Concurrent discovery limit of 16 reached for StoreOnce. Waiting for a copy to finish.
2022-06-10 00:00:27 - Concurrent discovery limit of 16 reached for StoreOnce. Waiting for a copy to finish.
2022-06-10 01:00:28 - Concurrent discovery limit of 16 reached for StoreOnce. Waiting for a copy to finish.
2022-06-10 02:00:29 - Concurrent discovery limit of 16 reached for StoreOnce. Waiting for a copy to finish.
2022-06-10 03:00:30 - Concurrent discovery limit of 16 reached for StoreOnce. Waiting for a copy to finish.
2022-06-10 04:00:31 - Concurrent discovery limit of 16 reached for StoreOnce. Waiting for a copy to finish.
2022-06-10 05:00:32 - Concurrent discovery limit of 16 reached for StoreOnce. Waiting for a copy to finish.
2022-06-10 05:12:07 - Backup operation failed.

I have one catalyst store on Storeonce side for all volume sets in RMC.  

Does anyone come across this issue before? 

3 REPLIES 3
support_s
System Recommended

Query: HPE RMC and Concurrent discovery limit of 16 reached for StoreOnce

System recommended content:

1. HPE Recovery Manager Central (RMC) 6.3.9 Release Notes and Documentation Errata | Limitations in RMC 6.3.9

 

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

 

Thank you for being a HPE valuable community member.


Accept or Kudo

TechEvangelist
Occasional Advisor

Re: Query: HPE RMC and Concurrent discovery limit of 16 reached for StoreOnce

I could not obtain infomration relevant to address my issue from your hyperlink.

I assume that following information might be relevant. There is a hard limit of 16 volumes in paralell that can be backed up to StoreOnce.

Document - HPE Recovery Manager Central Software - Specifications | HPE Support

sbhat09
HPE Pro
Solution

Re: Query: HPE RMC and Concurrent discovery limit of 16 reached for StoreOnce

Hello @TechEvangelist,

That is the automated system recommendation. Please ignore if the hyperlinks are not relevant.

The link you posted is correct. I think you found the reason for that error. Please let me know if you need any more assistance.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of the company.


I am an HPE Employee

Accept or Kudo