No – I think he is
saying he has no issues backing up the virtual machines on top of
vmware. What he wants to do is backup the underlying “real” machine
so he can restore vmware itself. (i.e. Backup what would be there if there were
no virtual machines setup yet.)
In that case there is
no “C” drive because vmware is Linux rather than Windows. You’d have
to have a client installed there. NetBackup comes with RedHat Linux
clients but I don’t know if there is a vmware client.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Martin, Jonathan
Sent: Thursday, August 16, 2007 11:44
AM
To: Kevin Whittaker;
veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] VMWARE Backup
question
Ok...
so
Host_1 -->
Virtual Machine 1
Host_1 --> Virtual
Machine 2
Host_1 --> Virtual Machine 3
Verify that Host_1 (in
my example above) is in DNS and make sure you specify host_1 in your policy with
the C:. I'd also make sure you exclude the directories with your virtual
machines in them. Forget about Virtual Machines, this is just a standard
file level backup of that server.
From: Kevin
Whittaker [mailto:Kevin.Whittaker AT syniverse DOT com]
Sent: Thursday, August 16, 2007 11:32
AM
To: Martin, Jonathan;
veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] VMWARE Backup
question
No.... That is not
it.
I am backing up the
virtual clients just fine, using standard NetBackup
procedures.
I want to backup the
actual servers C drive, not one of the VMWARE client's.
I believe I am just
using the wrong terminology.
It is not even getting
connected, because it keeps getting the 58 and 29 status codes on the
backup.
Kevin
From: Martin,
Jonathan [mailto:JMARTI05 AT intersil DOT com]
Sent: Thursday, August 16, 2007 11:30
AM
To: Kevin Whittaker;
veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] VMWARE Backup
question
I'm not sure what the
"core" is, but if you are backing up the disk files or data that resides on the
master / host then you have to specify that host name in the policy. If
you want data on the virtual disks (not the virtual disks themselves) then you
have to install the NBU client on the virtual machine and use that host
name.
Think of backing up
virtual machines like backing up cluster resources. If you want a resource
the cluster (virtual machine) has use the cluster (virtual machine) name.
If you want the node (host / master) info then use that hostname. As
usual, make sure all these names and IPs are in DNS, both forward and
reverse.
-Jonathan
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Kevin Whittaker
Sent: Thursday, August 16, 2007 11:17
AM
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] VMWARE Backup
question
All,
Netbackup 5.1MP6
Ok,
I am going to try and not sound too stupid about this. I am new to backing
up VMWARE and a little confused.
We
have a Windows 2003 , running VMWARE Workstation 5. Well, we loaded
NetBackup client on the 2 VMWARE clients, also running Windows 2003, and they
both backed up successfully.
We
loaded the NetBackup client on the core area of the server and keep getting a
status code 58, for the first try and then a status code 24 for the second
try. I was told, as long as I am not backing up the dsk files, I should be
able to do a normal backup of the core area.
I
have done all the normal troubleshooting for 58 & 24 status codes but
nothing seems to work.
I
can ping the master server from the core area and I can also do a
traceroute.
Anybody have any idea what I am
missing?
Kevin Whittaker
Syniverse Technologies
Systems Engineer - UNIX
Admin