Veritas-bu

Re: [Veritas-bu] Problem of VMWare ESX Backup via SAN

2011-08-12 04:22:38
Subject: Re: [Veritas-bu] Problem of VMWare ESX Backup via SAN
From: "Adrian Soetanto" <adrian.soetanto AT bentoel.co DOT id>
To: "George Winter" <george_winter AT symantec DOT com>, "Luke Walker" <lwalker AT td.com DOT au>, "WEAVER, Simon (external)" <simon.weaver AT astrium.eads DOT net>, <veritas-bu AT mailman.eng.auburn DOT edu>
Date: Fri, 12 Aug 2011 15:21:51 +0700
Dear all,

If we use NetBackup 7.1 and VMWare ESX 4.1, do we need to install VCB in
order to backup ESX over SAN?
We did not install VCB yet.

Currently, we have automount disabled in backup host and the VMFS
datastore LUNs have already been presented in Device Manager of backup
host.
But, why the VMFS datastore LUNs are not presented in Disk Management
view of backup host? (only local disk is presented)

Is that the cause of our VMWare backup over SAN failure?
If the datastore LUNs do not need to be presented in Disk Management,
then what is missing from our NetBackup setting/configuration?
 
But, if the datastore LUNs need to be presented in Disk Management, then
what is missing from our datastore LUNs setting/configuration?
 
Thank you for helping.

--
Best Regards,
 Adrian




-----Original Message-----
From: George Winter [mailto:george_winter AT symantec DOT com] 
Sent: 12 Agustus 2011 6:25
To: Luke Walker; Adrian Soetanto; WEAVER, Simon (external);
veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Problem of VMWare ESX Backup via SAN

Sorry, I misread that.  You are correct.  Disabling Windows automount is
highly recommended.

-George

-----Original Message-----
From: Luke Walker [mailto:lwalker AT td.com DOT au] 
Sent: Thursday, August 11, 2011 4:18 PM
To: George Winter; Adrian Soetanto; WEAVER, Simon (external);
veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Problem of VMWare ESX Backup via SAN

This seems contrary to best practice .. if you don't instruct Windows to
not automatically mount new volumes, and zone in the ESX
datastores/VMware LUNs .. Windows will try to mount those LUNs upon
presentation, and therefore damage live production VMs

Yes - don't try to mount/format/repartition VMware LUNs from your
Windows Media Server - but you should be running "automount disable"
before presenting said LUNs!

Kind Regards,
Luke Walker


-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of George
Winter
Sent: Friday, 12 August 2011 8:05 AM
To: Adrian Soetanto; WEAVER, Simon (external);
veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Problem of VMWare ESX Backup via SAN

Hi Adrian.  Answers inline:

>>  - Do we have to run the diskpart command (automount disabled &
automount scrub) before mapping the VMWare storage to Windows Backup
Host?

NO!  Do not do this.  You need to do nothing to the LUN's from the
Windows side.  If you partition or otherwise modify the VMware LUN from
the Windows backup system you will destroy all of the VM's on that LUN.

>>  - What entry should be defined in NetBackup Administration
credentials?

You just need to define the credentials of the vCenter server.  You do
not need to add the credentials for each ESX server.

>>   The question is, to run VMWare backup over SAN, do we have to
define the ESX server in Credentials?

No. I suspect that the problem that you have is that the SAN based LUN's
are not properly shared with the Windows backup host or they are the
wrong LUN's.  When the LUN's are correctly shared, they will show up in
the Windows disk manager as a "Healthy, unknown partition".  The exact
wording for this might change depending on the version of Windows you
are running.  If you see the LUN's in the Windows disk manager and
backups still fail it could be a permissions issue (permissions are
defined on the vCenter server) or the wrong LUN's are shared.  Because
network (NBD) backups are successful, the VADP process is working but
most likely the SAN based LUN's are not shared correctly.

The required vCenter permissions are defined here:

http://www.symantec.com/business/support/index?page=content&id=TECH13049
3

-George Winter
Symantec Corporation


-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Adrian
Soetanto
Sent: Thursday, August 11, 2011 1:46 AM
To: WEAVER, Simon (external); veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Problem of VMWare ESX Backup via SAN

Dear Simon,

We use NetBackup 7.1, do we still need to get the latest NBU Update
Pack?
The re-scan disk results in nothing.

I'm not sure whether the configuration of our SAN and NetBackup is
complete or not.
That's why I want to ask a few questions regarding this VMWare backup
over SAN:

- Do we have to run the diskpart command (automount disabled & automount
scrub) before mapping the VMWare storage to Windows Backup Host?

- What entry should be defined in NetBackup Administration Console |
Media & Device Management | Credentials | Virtual Machine Servers?
  First, we just define only one VMWare VCenter and the VMWare backup
runs successfully over LAN only.
  When we have a failure running VMWare backup over SAN, then we tried
to define the two ESX server we have, but we have this error message:
"Host is invalid"
  Then, we try to enter the IP Address of the ESX and both of the IP
address of the ESX server can be defined here.
  The question is, to run VMWare backup over SAN, do we have to define
the ESX server in Credentials?

Thank you for helping.

--
Best Regards,
 Adrian




-----Original Message-----
From: WEAVER, Simon (external) [mailto:simon.weaver AT astrium.eads DOT net]
Sent: 11 Agustus 2011 2:29
To: Adrian Soetanto; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Problem of VMWare ESX Backup via SAN

Ok so you see it ... but does Disk Management show anything after you do
a re-scan disks?
And its definetely presented correctly (your VM Backup Host) on the SAN?

Also ... and I said this last time... did you get the latest NBU VMware
Update Pack, because this fixed many problems for me, especially doing
via the SAN as it was horrible speeds.

I was on 7.0.1
Take it you rebooted?

-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Adrian
Soetanto
Sent: 10 August 2011 17:38
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Problem of VMWare ESX Backup via SAN

Dear all,

I have another problem related to the previous problem which is a VMWare
ESXi Backup Problem.
The VMWare ESX backup has already been successful through LAN backup,
but it's still failed if I use SAN backup/transfer type.
Here is the description & facts of my problem...

DESCRIPTION OF PROBLEM

VMWare ESX backup is failed if it's set to use SAN, but is successful if
it's set to use LAN.


FACTS & FIGURES

- Master Server:
        OS: IBM AIX (oslevel 5300-12-04-1119)
        NetBackup 7.1

- Media Server & Veritas Backup Host:
        OS: Windows 2003 x64
        NetBackup 7.1

- Client/Machine to be backed up:
        VMWare ESXi 4.1

- The storage unit for the backup host has already been set up.
- I've already added the VMWare Virtual Center into the Credentials |
Virtual Machine Servers (from Java Administration Console).
- The windows Veritas Backup Host is a media server as well and I have
linked it to the VMWare storage and tape backup drive through the SAN
switch.
- I've already disabled the automount using diskpart command, so that
the storage will not be initilized and formatted by Windows.
- The VMWare storage can only be seen from Device Manager and not from
Disk Management.

Please help me solve this problem.
Thank you in advanced.


--
Best Regards,
 Adrian
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

This email (including any attachments) may contain confidential and/or
privileged information or information otherwise protected from
disclosure. If you are not the intended recipient, please notify the
sender immediately, do not copy this message or any attachments and do
not use it for any purpose or disclose its content to any person, but
delete this message and any attachments from your system. Astrium
disclaims any and all liability if this email transmission was virus
corrupted, altered or falsified.




-o-
Astrium Limited, Registered in England and Wales No. 2449259 Registered
Office:
Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

________________________________

This email is intended for the named recipient only. The information
contained in this message may be confidential, or commercially
sensitive. If you are not the intended recipient you must not reproduce
or distribute any part of the email, disclose its contents to any other
party, or take any action in reliance on it. If you have received this
email in error, please contact the sender immediately and please delete
this message completely from any systems. Confidentiality and legal
privilege are not waived or lost by reason of mistaken delivery to you.
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu