RPA went to Unknown State after upgrade

Adding to this , i see a new internal cluster was created on this from the base of original cluster

I would seriously consider reinstalling as there also looks to be RP/SE object corruption. RP/SE has to be installed using DM, therefore your manual CLI attempt to upgrade has broken several elements of this.

I didn't get the meaning for Re-installing does that mean do i need to upgrade the code again?

Thanks

Saran

No idea why the Cluster has another internal cluster created?

You definitely don't want to use a manual CLI upgrade procedure for RP/SE installations. It simply doesn't work. Even if you choose to use the manual method for a EX or CLI RP system it does not provide an NDU process. Therefore, DM is the correct tool to use for all upgrades.

This is how the Config looks like now

|------------------------------------------|

| Cluster Site2                          |

|------------------------------------------|

| Internal cluster name | 0xb83ef28        |

| Time zone             | America/New_York |

| Primary DNS server    | 10.227.171.x   |

| Secondary DNS server  | 10.227.171.x   |

| Primary NTP server    |                  |

| Secondary NTP servers |                  |

| Local domain          |                  |

|-----------------------|------------------|

In Cluster 0xb83ef28, SP cannot see RPA2. Verify that zoning is configured so that SP can see all RPAs at the relevant site. ; SunGard ;

dont know what would be the next step?

Thanks

Saran

Hi Saran,

The CLI method of upgrading is not supported because it is not capable of facilitating an NDU upgrade. The error messages would imply to me that the RP system no longer has correct visibility of the repository volume(s).

Regards,

Rich Forshaw

Consultant Corporate Systems Engineer - RecoverPoint & VPLEX (EMEA)

May i know the procedure for upgrading the RPA via CLi, may be i was missing something here.

just to my curiosity , why we have such a option then?

Thanks

Saran