Hi George,
I tested running the VCBMounter command and it works fine.
But I have to specify the -m nbd instead of -m san in the vcbmounter
command.
In the logs of NBU, I saw that it actually uses -m san.
So I suspect that it could be that reason that it failed.
Is there any where in NBU 6.5.1 to set that option?
It seems hardcoded.
Thank you.
-----Original Message-----
From: George Winter [mailto:george_winter AT symantec DOT com]
Sent: Friday, February 01, 2008 11:20 AM
To: Daniel Goh; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Netbackup 6.5.1 with VCB 1.1
Hi Daniel. A snapshot creation error (status 156) can be caused by a
number of issues. These include:
*** Backup Proxy has not been provided access (via iSCSI in your case)
to the VMware Datastore(s).
If this is the case the snapshot creation would fail pretty much as you
are describing. This can be easily tested outside of NetBackup. You
can use the vcbMounter.exe command for this. Manually running the
vcbMounter.exe command from the Backup Proxy tests the entire snapshot
creation process including copying the vmdk files to the Backup Proxy.
The vcbMounter.exe command can be found in the home directory of the VCB
Framework SW. This is typically:
\Program Files\VMware\VMware Consolidated Backup Framework
The command syntax is as follows:
vcbMounter.exe -h <FQDN of ESX Server> -u root -p <root password>
-a ipaddr:<FQDN of virtual machine> -r e:\vcb_mnt\<VM hostname> -t
fullvm
Instead of the "FQDN of ESX Server" you could also use the "FQDN of
Virtual Center Server". After the "-r" option, the "e:\vcb_mnt"
directory (staging area) must exist.
I've never personally tested this on iSCSI but I don't think you need
the "-m" switch.
If you can't get it to work initially make sure you don't have any typo
issues (I'm a bad typist!). If this works, NetBackup should work as
well. Once you get this command to work correctly, be sure and delete
the folder and files that were transferred to the Backup Proxy as a
result of this command.
Some other issues that might prevent the snapshot creation are:
*** VCB snapshot already exists.
>>From the VI Client, check the Snapshot Manger for the target Virtual
Machine and make sure the special VCB Snapshot (_VCB-BACKUP_) is not
currently created. If it is, either another backup job has been
initiated or it was not properly deleted after the last backup attempt.
Delete this snapshot and then try the vcbMounter.exe command again.
*** Not enough room on the staging area.
The staging area must be at least as large as the largest VM you are
going to backup. The staging area should be large enough to support
multiple VM's if you are going to run parallel backups.
*** The VCB Framework version is not correct.
The VCB Framework SW, ESX Server version and the VC Server version all
need to be the correct versions. Check the release notes for the
version of ESX server you are running to make sure that all of the
components mentioned are the correct version for your ESX server.
*** You are using the VMware NetBackup Integration Module
If you have installed this, remove it if you are using NetBackup 6.5.1.
NetBackup 6.5 and above does not use the VMware NetBackup Integration
Module. If it is installed, it can prevent backups from working
properly. If it is installed and you uninstall it, make sure you also
remove any bp_start_notify and bp_end_notify scripts that have been
created as a result of this module.
Daniel, I hope this helps.
-George
-----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 Daniel
Goh
Sent: Thursday, January 31, 2008 10:42 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Netbackup 6.5.1 with VCB 1.1
Hi all,
I am currently implementing NBU 6.5.1 with VCB 1.1.
Am using Netapps FAS2020 iSCSI LUNs.
However on running the backup in NBU 6.5.1 with VCB 1.1, I always get
snapshot error.
We always get error code 156.
Error Message:
FTL - snapshot creation failed, status 156
Although I can see the VM snapshot creation in VirtualCenter console,
the VMDK backup process never took place and respectively the newly
created VM snapshots were deleted automatically by VirtualCenter after
few seconds.
After inspecting some of the netbackup logs I believe I found the exact
cause however I don't have a workaround for it as yet.
Fragments from the "bpfis.log" file:
17:52:19.085 [5596.6096] <2> onlfi_vfms_logf: do_cmd: Command failed
""C:\Program Files\VMware\VMware Consolidated Backup
Framework\vcbMounter.exe" -h esxhost:443 -u "root" -p *********** -c
"C:\Program Files\VMware\VMware Consolidated Backup
Framework\vmName.cache"
-a ipaddr:vmguest.domain.local -t fullvm -L 6 -r
"e:\vcb_mnt\vmguest.domain.local" -M 1 -m san" <NUL
>C:\WINDOWS\TEMP\VfMS-05596201020733266096000000002-a06096
2>C:\WINDOWS\TEMP\VfMS-05596201020733266096000000003-a06096
As it can be seen, the command initiated by NetBackup to VCB contains
the parameter of using SAN transfer method which is not going to work
for me because I don't have SAN infrastructure at all. I would like to
use the "-m nbd" feature of VCB for making backups over LAN however I
can't find any place where to change this parameter in NetBackup.
Initiating the "vcbMounter" manually from CLI with the correct parameter
works just great so in my opinion this is definitely a problem with the
NetBackup / VCB cooperation. I didn't find any clues neither on the
internet nor in the official manuals regarding such situations so I
would appreciate very much the help of anyone who can give me some
workarounds or additional information on how to procede next.
_______________________________________________
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
|
