ashilkrishnan's Accepted Solutions

Hi @Petersaints , If you cannot add 2nd interface on VR appliance at Site B, then you can deploy a add on server here and add 2nd interface on it for replications. Note: You cannot add more than one VR appliance(management/primary appliance), however you can add additional servers under it for load balancing/managing replications.  Pairing from Site B to C would use the existing appliances and when you configure VM replications, you can select the add-on servers. Deploy add-on VR server  Register add-on VR server to primary server  Isolate traffic on add-on server  Hope that helps  

Hi @AhhhOK , SRM has to be on 8.3 windows to support migration to 8.4 appliance. Please prerequisites here --> Migrate SRM on windows to appliance  Either you can upgrade SRM 8.2 windows to 8.2 appliance and then upgrade to 8.4 appliance Or Upgrade SRM 8.2 to 8.3 windows and migrate to 8.4 appliance Hope that helps.

Hi @whiteoneus , It's a patch update within the same update series(U3), so it's not a far away version and you are good to update it on 6.5 U3d. If there is any such limitation, it would be clearly mentioned in 6.5 U3q release notes --> vCenter 6.5 U3q release notes  Hope that helps

Hi @Petersaints , 1. This is based on the user requirements. If it's small bunch of VMs, you can let it run in auto-created network and manually assign a network for testing purpose followed by cleanup of that network. If you want to perform tests on multiple VMs, you can create a isolated network just for testing. 2. This network should be isolated only from the production network and not from everything. User needs to find a way to have this network accessible only at recovery site. If that's a challenge, yes VM console is the only option. 3. If IP customization is configured for recovery site, VMs will use the recovery site settings even during testing(but in isolated mode, depending the network port group assigned to test network). If you do not customize a NIC on the recovery site, the NIC continues to use the IP settings from the protected site. Please refer this section for more details --> Customizing IP Properties for Virtual Machines  Hope that helps.

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.      

Hi @JDMils_Interact , All these placeholder VMs(from previous and current installation) will have a 'com.vmware.vcDr' extension for them and if we try to list the VMs with that extension, it'll list the old and new placeholder VMs. Locating SRM Placeholder VMs using the vSphere API  Placeholder VMs are usually created in dedicated one or more placeholder datastore's. If the previous SRM installation was using a different placeholder datastore, it would be easier to locate and cleanup placeholder VMs from it. If the new installation does not contain a lot of VMs, you can cleanup all placeholder VMs and re-create them from SRM UI. Hope that helps  

Hi @PePierias , For graceful shutdown of VMs, you need to shut them down manually. vSphere does not perform a graceful shutdown of VMs when you shutdown ESXi directly. Please refer the 'Note' here --> Reboot or Shut Down an ESXi Host  More reboot-shutdown details here  Hope that helps.

Hi @jatdesi , SRM windows edition should be on 8.3 to migrate to SRM 8.4 appliance. Please upgrade SRM 8.2 windows to 8.3 windows before attempting migration to 8.4 appliance. This applies to SRM 8.3 appliance as well. We need to be on SRM 8.3 windows to attempt migration to 8.3 appliance. Hope that answers the question.  

Hi @rgmwanik , Seems like a nvme driver issue. If it's a Lenovo server, please refer this --> https://support.lenovo.com/in/en/solutions/ht508755-server-with-intel-p4500p4510p4600p4610-nvme-ssd-may-have-vmware-psod-during-heavy-io-lenovo-servers . If not Lenovo,  check current nvme driver version and update to latest version.

@9990374530 , Yes, you need license assigned to ESXi hosts at both sites. Please refer this FAQ --> Site Recovery Manager FAQ  Look for this question under 'Pricing and licensing' Are VMware vSphere license required for both protected and recovery sites ? Hope that answers the question.

If vCenter certificates were replaced, please confirm if the SSL trust anchors are good. For environments till 6.7 --> https://kb.vmware.com/s/article/2121701  For 7.0 environment --> https://kb.vmware.com/s/article/78709 

Hi @DavidWattoula , I would stick with the product life cycle matrix. I will share a feedback with the team to see if the KB/lifecycle matrix needs any modification. Will update the thread, if I get any additional information. 

Hi @BayerCGOps , Post upgrade to 8.4, additional steps are required and admin needs to be configured  Please perform steps mentioned under 'What to do next'   -->  VR 8.4 upgrade  Login to VR VM console using root user and configure admin user by running: passwd admin Register VR with vCenter --> Register VR 8.4 to vCenter using new VAMI interface  Hope that helps Please mark my comment as the Correct Answer/Kudos if this solution resolved your problem