[BBLISA] NFS re-export or NFS proxy?

[Dewey Sasser]

Hello all,

I'm think I'm rather stuck here but I want to consult the wisdom of the
list before I do things "the hard way".

I'm running a VMWare system a mix of LabManager 2.5 and LabManager 4.0
with 350 odd VMs on 12 ESX hosts (mixture of 3.5 and 4.0).  All of the
virtual disks are served by a (currently single) Sun 7210 via NFS.

I want to move *one* (but not all) of the NFS exports from that 7210 to
a new 7210 to share the storage load.  From the 7210 perspective, doing
this is quite easy.

Unfortunately, VMWare is rather attached to the specific host name
(attached == uses a hash of the host name in paths in the virtual disk
files).  "The hard way" is to attach both storage systems to VMWare
machines and tell it to copy data from one to another.  This requires
service interruption while virtual disks are being copied and well as
being a fairly inefficient way of going about the bit moving compared to
what the 7210 gives me.

I can't just rename the host because I only want to move one of my
exports and leave the others.  Unfortunately, I failed to anticipate
this problem when setting up the system in the first place (note to
self:  use a bunch of DNS aliases with VMWare LabManager).

I could theoretically perform evil magic on VMWare but I'm leaning
strongly against it for risk reasons and clarity reasons.

My last thought on this is, if I had some kind of NFS multiplexer which
could take on the existing host name and then route NFS requests for a
specific export to the actual host, that would solve the problem.  Alas,
I know of no such system which I can put on top of what I already have
and my Google-fu is inadequate to find one.

My thought is that if I could either set up a system to mount the shares
I care about and re-export them, or if a straight-up NFS pass-through
proxy might exist, that would give me the appropriate indirection.

Does anyone know of such a system, or have any other ideas that might help?

Thanks,

--
Dewey