I've tried the VG/LVM method in the shell examples (lvmCreate.sh & lvmMount.sh) and I have a question as its
related to doing this using the VDDK API's flat file. e.g.
VixDiskLib_Open() & VIXDISKLIB_FLAG_OPEN_READ_ONLY flag.
Can the VG name be modified if the flat file was opened this way. I'm getting the following errors...
root@shuttle vmdiscover# vgrename YafuWk-3orv-WuXR-0Kf9-HuLk-1uRA-Ip6xNe vmwarelvm
/dev/loop0: write failed after 0 of 1536 at 4608: Input/output error
As of now, there is no read-only mounting support on Linux. So you could just use the default flags (0)
-Sudarsan
Sorry, I don't see how this can work with a read-only file.
-Sudarsan
So our VDDK API Linux proxy system should be clean of all VGs to insure we don't have a VG name collision problem mounting the VG for file level backup? If this is true then does it means we should only back on one Linux VM at a time because we can't change the VG names in the event the Linux VM are all created from the same Template and all have the exact same VG names?
Thanks,
-Ron
While I am not claiming to be an LVM expert - I think what you propose is right.
Thanks
Sudarsan
Is there someone who can confirm this? I really need a definitive answer... this could mean that we can only process 1 Linux client at a time.
I need to follow up with one additional question... seems I can use the
vmware-mount -f (flat file) option to mount a remote Linux disk and
then use the LVM commands to mount the VG on the local Linux proxy.
When I use the VDDK API on the same disk.... VixMntapi_OpenDisks()
&& VIXDISKLIB_FLAG_OPEN_READ_ONLY flag I can't. What flag does
the vmware-mount program use? VIXDISKLIB_FLAG_OPEN_UNBUFFERED?
VIXDISKLIB_FLAG_OPEN_SINGLE_LINK? Some other?
For doing file level backup... which flag is recommended?
Thanks,
-Ron
As of now, there is no read-only mounting support on Linux. So you could just use the default flags (0)
-Sudarsan