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
i had do test with 2 mode:
1 - my disk size was 85G and do first replication job it take 8min
2 - rename replication folder on replica site
then stop replication job
then increase disk size on protected site
then increase disk size on replica size with command vmkfstools -X 95G vm.vmdk
finally create replication job and use seeds and in this mode also it take 8min now i want to know why in second mode it take 8 min like first mode ? because in second mode i used seed
what is the problem now ?
BR
You are saying the initial replication did not use seed disks? That's surprising. I know the checksum can take quite a while but I would expect that replication using seed would be quicker. Otherwise what is the point of using seeds? Maybe the difference is more noticable in larger VMDK, or if there is greater number of active replications.
is that your means using from seeds will be sense in large vmdk files such as 500-600G ??????
I really don't know. Like I said, we would expect initial full sync time to be improved when seeds are used. I just suggested a couple of possible reasons why that was not observed in your case, but it's really just a guess.