In answer to your questions
1) a backup of the vmdk and vmx files is probably all that is required, but
the nvram and log files are pretty small so just back them up too. The
backup will only be consitant if the vmware instance is either off or
suspended. If it is running the backup will fail and networker can't get a
lock on the file. Also you will need to specifically include the vmfs
directories that the vmdk files are in. Putting All in the savesets files in
the networker client config will NOT work. You will have to put in /home and
/home the /vmfs/vmhbaw:x:y:z directories as a minimum.
2) The vmware instances must either be shut down or suspended for networker
to be able to back them up. Otherwise networker just reports that the file
is open and won't back it up. The instances can be up if you are taking a
snapshot as you will only backup the snapshot. We use vmware virtual center
for suspending and resuming instances.
3) Don't know. Some neat stuff in vmware 3 but I won't use it for at least 6
months. I'll let others work out the bugs ;-)

Ken





On 6/16/06, Shyam Hegde <hegde.shyam AT gmail DOT com> wrote:

Hello Thanks for the responses!

Can anybody try to answer few of my basic questions, (I am new in the
subject VMWARE!)

1. If I install the NetWorker Client package on the VMWARE host, take the
backup of .vmdk and .vmx files (disk and configuration files) is it
sufficient for recovering my virtual server? Will the backup be
consistant? My objective is not to backup the virtual server making it as
a
NetWorker Client. No granular backup is required at this moment. Want to
have a way of restoring my virtual server, in case of corrupt vmware
config
or disk files.

2. Is it mandatory to have the virtual server shut down before backup. or
have the snapshot and then take the backup of that snapshot?
If above is the case I may to opt for 'savepnpc' or so probably.

3. Is there any NetWorker module available or anounced for such backups.

Regards
Shyam

On 6/16/06, Brian Narkinsky <BNarkinsky AT cclaflorida DOT org> wrote:
>
> IN ESX 3.0 there is a new feature called consolidated backup.  Not sure
> exactly how it will work yet but, it promises to allow you back up the
> VM files but, still restore individual objects from with in these VM
> files.
>
> SO you could back up a whole VM and then later restore somebody's Excel
> Spreadsheet from this backup.
>
> A lot of this will need to be fleshed out as ESX 3.0 becomes mainstream
> but, it looks promising.
>
>
> -----Original Message-----
> From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT 
EDU]
> On Behalf Of Ken Gehring
> Sent: Friday, June 16, 2006 9:02 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] How to backup servers running on VMWARE....
>
> There are a number of ways to do it.
> 1) Best practice (and most expensive) is to install the Netwroker client
> on each vmware instance.
> 2) Suspend each instance and then backup the entire instance (which is
> what we do)
> 3) Take a snapshot of each instance, and backup the snapshot.
>
> If you are backing up the ESX servers over GB ethernet, then you can
> doany of the above. If they are backed up over 10/100 then use #1.
>
> We backup our ESX server twice a day. Each time suspending different
> instances (separates our production and non-production stuff).
>
> Ken
>
> On 6/16/06, Shyam Hegde <hegde.shyam AT gmail DOT com> wrote:
> >
> > Hello Everybody,
> >
> > Greetings!
> > I have to configure a cluster of servers which are running on a host
> > with VMware ESX Server 2.5.0 build.
> > I want to know what are the best practices to backup servers running
> > on VMWARE hosts.
> >
> > I use NetWorker 7.2 and my backup server is on Solaris 9. All backups
> > are taken over the 10/100 (and some on Gig) LAN.
> >
> > Thanks in advance!
> >
> > Best Regards
> >
> > Shyam
> >
> >
> > ****** WISHING YOU ALL GREAT WEEK END! ********
> >
> > To sign off this list, send email to listserv AT listserv.temple DOT edu and
> > type "signoff networker" in the body of the email. Please write to
> > [email protected] you have any problems wit this
>
> > list. You can access the archives at
> > http://listserv.temple.edu/archives/networker.html or via RSS at
> > http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> >
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu and
> type "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems wit this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or via RSS at
> http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu and
type
> "signoff networker" in the
> body of the email. Please write to
[email protected] you have any problems
> wit this list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type
"signoff networker" in the
body of the email. Please write to [email protected] you 
have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER