Hey folks.
My goal is to run vcbMounter to export VMs on a regular basis, and then replicate those files to another site for DR. At the site I'm working with, there is no real storage except for the ESX server itself.
I tried running vcbMounter to export the files to a directory under /vmfs/volumes/<datastore_name> but then when I tried to rsync the files to the alternate site, I got an rsync error. Google says this is due to the file system not being ext2/3 or some other standard file system. So I thought then I would make a linux VM, export an NFS share, mount that on the ESX server, and then have vcbMounter write to that destination.
It turns out this is incredibly slow (2 hours wrote ~70MB). Is this expected? Could this be a bug that is fixed (the ESX server is quite out of date (3.5.0 build 82663)?
At this rate, I might as well write the data across the WAN, but I would rather write locally and then rsync across the WAN.
Any wise advice out there for me?
Many thanks!
Grant
-
If you plan to make a DR solution over WAN you can consider other solution (vRanger, esXpress, VMware Data Recovery if you migrate to vSphere, ...) that have differential and/or incremential transfert.
Andre
Veeam Backup with its replication function fits better than VCB, but of course it's not free.
---
VMware vExpert '2009