Article Number: 540468

printer Print mail Email

RecoverPoint/SRM: SRM displays an extra and unknown array called "RecoverPoint-null"

Primary Product: RecoverPoint

Product: RecoverPoint more...

Last Published: 21 Apr 2020

Article Type: Break Fix

Published Status: Online

Version: 4

RecoverPoint/SRM: SRM displays an extra and unknown array called "RecoverPoint-null"

Article Content

Issue


 

SRM shows an extra and unknown remote array called "RecoverPoint-null" in the Array Pairs


The following can be seen in the cancun logs (extracted.*/files/home/kos/RPServers/RPServers_logs/cancun/cancun_server.log.gz) on the RecoverPoint Site Control RPA:
2020-01-16 21:40:11,387 [http-bio-7115-exec-3] (CancunKashyaAdapter.java:6215) DEBUG - validateLeaglArrays arrayIDs : [RecoverPoint-0xxxxxxxxxxxxxxxxx, RecoverPoint-0xxxxxxxxxxxxxxxxx] possibleArrays: [RecoverPoint-0xxxxxxxxxxxxxxxxx, RecoverPoint-0xxxxxxxxxxxxxxxxx, RecoverPoint-null]

2020-01-16 21:40:15,538 [http-bio-7115-exec-3] (CancunKashyaAdapter.java:568) DEBUG - Skipping group CG1 (CG UID: GroupUID [id=xxxxxxxx]): at least one of the copies (replica/source) doesn't belong to given arrays. SourceCopy siteUID=SiteUID [id=xxxxxxxxxxxxxxxxx], ReplicaSiteUID=SiteUID [id=294051554]
2020-01-16 21:40:18,861 [http-bio-7115-exec-3] (CancunKashyaAdapter.java:568) DEBUG - Skipping group CG2 (CG UID: GroupUID [id=xxxxxxx]): at least one of the copies (replica/source) doesn't belong to given arrays. SourceCopy siteUID=SiteUID [id=xxxxxxxxxxxxxxxxx], ReplicaSiteUID=SiteUID [id=294051554]

Cause

After RP site configuration change, an old setting is cached for SRM (cancun) and is shown incorrectly

Resolution

Workaround:

    A. Change RP consistency group from error in cancun logs (CG1, CG2 in the example above) to be non SRM-managed.
    B. Remove RecoverPoint Array Pairs in SRM 
    C. Add back Array Pairs

Resolution:


No fix is expected for this issue

Notes

Issue


 

SRM shows an extra and unknown remote array called "RecoverPoint-null" in the Array Pairs


The following can be seen in the cancun logs (extracted.*/files/home/kos/RPServers/RPServers_logs/cancun/cancun_server.log.gz) on the RecoverPoint Site Control RPA:
2020-01-16 21:40:11,387 [http-bio-7115-exec-3] (CancunKashyaAdapter.java:6215) DEBUG - validateLeaglArrays arrayIDs : [RecoverPoint-0xxxxxxxxxxxxxxxxx, RecoverPoint-0xxxxxxxxxxxxxxxxx] possibleArrays: [RecoverPoint-0xxxxxxxxxxxxxxxxx, RecoverPoint-0xxxxxxxxxxxxxxxxx, RecoverPoint-null]

2020-01-16 21:40:15,538 [http-bio-7115-exec-3] (CancunKashyaAdapter.java:568) DEBUG - Skipping group CG1 (CG UID: GroupUID [id=xxxxxxxx]): at least one of the copies (replica/source) doesn't belong to given arrays. SourceCopy siteUID=SiteUID [id=xxxxxxxxxxxxxxxxx], ReplicaSiteUID=SiteUID [id=294051554]
2020-01-16 21:40:18,861 [http-bio-7115-exec-3] (CancunKashyaAdapter.java:568) DEBUG - Skipping group CG2 (CG UID: GroupUID [id=xxxxxxx]): at least one of the copies (replica/source) doesn't belong to given arrays. SourceCopy siteUID=SiteUID [id=xxxxxxxxxxxxxxxxx], ReplicaSiteUID=SiteUID [id=294051554]

Cause

After RP site configuration change, an old setting is cached for SRM (cancun) and is shown incorrectly

Resolution

Workaround:

    A. Change RP consistency group from error in cancun logs (CG1, CG2 in the example above) to be non SRM-managed.
    B. Remove RecoverPoint Array Pairs in SRM 
    C. Add back Array Pairs

Resolution:


No fix is expected for this issue

Notes

Article Attachments

Attachments

Attachments

Article Properties

First Published

Tue Jan 21 2020 18:22:03 GMT

First Published

Tue Jan 21 2020 18:22:03 GMT

Rate this article

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters