akirty
Contributor
Contributor

Switching from SRM 8.2 to SRM 8.4

Jump to solution

Hi,

We have windows based SRM 8.2 in the environment and we are planning to move to SRM 8.4.

So, what I did is, I deployed fresh SRM 8.4 and configured the same vCenter that the SRM 8.2 was connected to. Now when I login to the vCenter and go to SRM, I see both SRM 8.2 & SRM 8.4 listed. I then exported the configuration xml from 8.2 and imported it in 8.4.

Now, I want to completely remove the SRM 8.2 and move all the VMs to SRM 8.4. The Protection Group from 8.2 are visible in 8.4 along with the VMs (since I imported the config), however the protection is not enabled for VMs in 8.4.

I want to know if the below steps are sufficient to achieve the SRM switch :

1. Remove protection for each VM from SRM 8.2

2. Configure protection for each VM in SRM 8.4

3. Power off SRM 8.2 for a week and then decommission.

It looks so simple, am i missing any step ?

 

Regards

AK

Labels (1)
Tags (1)
0 Kudos
1 Solution

Accepted Solutions
ashilkrishnan
VMware Employee
VMware Employee

Hi @akirty ,

Once the protection group and plans are cleared SRM 8.2, you can un-install SRM installations from Windows servers to un-register.

If the 8.2 plug-in is still listed in vCenter, you need to remove the plug-in registrations from vCenter. Following commands will list SRM service and SRM html5 service registrations. Identify the service registrations using server FQDN/IP address and un-register them.

2 List commands: (If vCenter PSC is external, please run these commands on 

/usr/lib/vmidentity/tools/scripts/lstool.py list --url http://localhost:7080/lookupservice/sdk --type vrUi

/usr/lib/vmidentity/tools/scripts/lstool.py list --url http://localhost:7080/lookupservice/sdk --type vcDr

 

Once you have the service ID, you can run this command to un-register:

Note: Replace 'id' with service ID captured from the list commands, update vCenter SSO admin user and password

/usr/lib/vmidentity/tools/scripts/lstool.py unregister --url http://localhost:7080/lookupservice/sdk --id xxx-xxxx-xxx-xxxx  --user 'administrator@vsphere.local' --password 'VMware123!' --no-check-cert

 

Hope that helps.

 

 

 

View solution in original post

3 Replies
ashilkrishnan
VMware Employee
VMware Employee

Hi @akirty ,

Once the protection group and plans are cleared SRM 8.2, you can un-install SRM installations from Windows servers to un-register.

If the 8.2 plug-in is still listed in vCenter, you need to remove the plug-in registrations from vCenter. Following commands will list SRM service and SRM html5 service registrations. Identify the service registrations using server FQDN/IP address and un-register them.

2 List commands: (If vCenter PSC is external, please run these commands on 

/usr/lib/vmidentity/tools/scripts/lstool.py list --url http://localhost:7080/lookupservice/sdk --type vrUi

/usr/lib/vmidentity/tools/scripts/lstool.py list --url http://localhost:7080/lookupservice/sdk --type vcDr

 

Once you have the service ID, you can run this command to un-register:

Note: Replace 'id' with service ID captured from the list commands, update vCenter SSO admin user and password

/usr/lib/vmidentity/tools/scripts/lstool.py unregister --url http://localhost:7080/lookupservice/sdk --id xxx-xxxx-xxx-xxxx  --user 'administrator@vsphere.local' --password 'VMware123!' --no-check-cert

 

Hope that helps.

 

 

 

View solution in original post

akirty
Contributor
Contributor

Thank you so much for these steps. I had missed the extension removal step.

Will perform this within a few days and will update.

 

Regards,

Akshay Kirty

0 Kudos
akirty
Contributor
Contributor

This worked perfectly.

Thank you so much

 

Regards,

Akshay Kirty

0 Kudos