I'm trying to backup /vmfs on an ESX 3.0.2 server using legato networker 7.2.
I can backup succesfully the rest of the ESX machine, but trying to bakcup /vmfs I get:
* sequana:+<span class="moz-txt-tag">/vmfs save: Warning inode number changed for /vmfs/devices<span class="moz-txt-tag">/+ may not be recoverable * sequana:+<span class="moz-txt-tag">/vmfs save: Warning inode number changed for /vmfs/volumes<span class="moz-txt-tag">/+ may not be recoverable sequana: /vmfs level=full, 2 KB 00:00:02 4 files gig: index:sequana level=full, 6801 KB 00:00:12 15 files
what can I do ?
Any other useful ideas about backup ?
Generaly I back-up the v-machines with their own (networker) client, but a couple of days ago a vmachine-flat.vmdk "disappeared" from /vmfs (still investigating how/why), so I was wondering what could I do to avoid this ?
(except reinstall vmachine and download everything from vmachine backup)
You can use any of the supported clients at the service console level.
You can use consolidated backup.
Or you can export the disks to another location with scripts.
>You can use any of the supported clients at the service console level.
>You can use consolidated backup.
Management dows not want to pay for soething else (no blame on me...)
>Or you can export the disks to another location with scripts.
what dou you mean ?
You can do scripts at console level to add snapshots and then export disk with vmkfstools or vcbExport
If you are looking for a free solution for backing up Virtual Machines an option could be my company's free version of esXpress. It will give you Full VM backups. The backups run in a Virtual Backup Appliance (VBA).
petedr is right, best free solution around
You just have to set rhe parameter 'save command' to 'save -x' to specify the client to cross filesystem.
I'm using ESX 3.5 and trying to backup the VMs through the service console with Legato Networker 7.2. I already installed the backup enabler.
First the backup stopped after a few seconds with the message 'Warning inode number changed....'. After I set the save-command to 'save -x' the complete 60GB were saved but I still got the error message...Any idea?
Sorry for the duplicate. Got an error message 'Thread not available' and thought I have to repost.
Message was edited by: kennygno