increase disk during replication

[baber]

Dear all

Hi

if i want change disk size during replication vm Are below steps correct ?

1 - stop replication

2 - power off source machine

3 - change size of disk on source VM

4 - power on source machine

5 - start replication

will be automatically destination vm disk increase ?

BR

[a_p_]

I'd suggest that you follow the steps in https://kb.vmware.com/kb/2052883

André

[baber]

Dear friemd

HI

i used all of that step but when i want enable replication attached error appear and can not enable that

what is my problem?

[baber]

please help me i am so confused

BR

[baber]

please help me for solve problem

[vbrowncoat]

I would suggest opening a support ticket

[baber]

where can i open support ticket VR is a free appliance will they support me ?

[vbrowncoat]

If you have support for vCenter then you have support for VR. Just open a support case as usual.

[baber]

where can open a support case?

[vbrowncoat]

LMGTFY

[baber]

thanks

but i am using trial version of esxi and in support have to insert serial number

[baber]

please help me my problem has not been solved yet

[maximiliens]

You can stop (delete) your replication and Re configure your replication. For me it's work when I have sometime this error...

[baber]

but if i stop replication or delete it my seeds will be delete and have to start new replication with biig data size this is problem

[admin]

Follow the steps in the KB provided already. It looks like you attempted to reconfigure replication. You didn't fully stop it and start it again.

If you look at the KB again you can see that there is a step to prevent the VMDK getting deleted when you stop the replication. i.e. rename the folder on the target site.

Then start a new replication job and point it at the existing disk on the target site.

[baber]

so thanks i have did this and work but when i reconfigure for replica machine after change disk size in wizard i accept use seeds but when replication start the time take for do replication was same a full sync is that correct ?

BR

[baber]

what is my problem ???

why this take same duration for synchronization data such as full synchronization ?

BR

[admin]

Full sync would be normal after re-configuring replication. It has to do full checksum and then copy the changed blocks. More information here:

vSphere Replication Synchronization Types - VMware vSphere Blog

[baber]

ok but now i am so confused thus what is the benefit of increase disk space via these steps ????

why do i have to disable replication?

why do i have to rename folder on replication site ?

what is difference between stop replication and create a new job or disable configuration and rename folder on replicaton site and finally create another job ?

in both mode it will be do start  full synchronization first and in both mode will be use same bandwidth ?

what is the benefit of this method?

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=20528...

[admin]

If you use seed disks anyway, it doesn't matter. The additional steps are not required.

If you did not use seed disks when first configuring replication, and then you stop replication, then the target VMDKs get deleted automatically. Renaming the VM folder prevents this from happening. So it takes less time when re-configuring replication. You just need to checksum and transfer the changed blocks rather than transfer the entire disk. It still can take a long time but not so much.

Note that the resize procedure is different in official documentation depending on whether or not seeds were used:

vSphere Replication 6.0 Documentation Center

vSphere Replication 6.0 Documentation Center