vCenter 6.7.0 Build: 15976728
Source SRM (On-Prem): 8.3.0, 16356494
Destination VR (VMC on AWS): 8.3.0, 16356494
vCenter 7.0.0 Build: 16345689
Source VR (On-Prem): 8.3.0.7861, 16284276
Destination VR (VMC on AWS): 8.3.0.7861, 16284276
After having expanded a drive (server_3.vmdk) on a VM on-prem, unable to add the server back to the Protection Group. This used to work on previous version of VR (On prem and VMC on AWS): 8.2.0, 14383137. Does anyone have any idea why?
Hi
If you are trying to re-configure VM replication with existing seed after increase disk capacity of a VM, then you need to increase the disk capacity of replica VMDK as well
Steps 5 to 8 --> VMware Knowledge Base
If you do not want to use replica seeds at target vsan storage, you can move the files to a different directory
Hope that helps
ashilkrishnan, don't you think the instructions in KB2052883 do not apply in my case, as we're talking about accessing the DR ESXi host in VMC on AWS via SSH? I doubt SSH is possible to hosts in VMC
Hi
I missed about the AWS part. Sorry about that
I do not handle replication to cloud environment. Let's wait for a reply from someone who handles such environments
I will reply if I find something to related to this issue