07-24-2015 10:32 AM
Hello guys,
I have installed a new platform for netbackup :
I would like to backup all my VMware machines using my SAN environement, I have configured my SAN using the Symantec Guide for VMware.
I'am using my media server as Host Backup for VMware, it says all my LUNs and datastores (When checking with diskmanager) from our EMC Array.
But all my VMware backup Job are failling whit this error :
"Error opening the snapshot disks using given transport mode: san Status 23"
for more details, see my attached file.
Thank you in advance for your help.
KAMOU
07-24-2015 10:54 AM
what is the netbackup and Vcenter versions?
are you saying that you zoned all luns that are presented to the Vmware enviornment to media server too? and able to see the Disks in device Manager?
how about the Multipathing.. does it being taken care?
if possible, test the backups with NBD transport and make sure they are successfull to confirm it is the only issue with the SAN transport.
please enable the vxms log and attach the log to this post along with the failed job details status
below is the T/N to enable the vxms log
https://support.symantec.com/en_US/article.HOWTO70905.html
07-24-2015 12:22 PM
Hi,
I will attach the vxms log later.
07-24-2015 01:55 PM
Hi,
You could find VxMS logs in the attached file.
Thanks for your support.
07-24-2015 03:53 PM
Hi Jakamou,
How many VMs are failing for backups?
Can you please confirm of those VMs are using passthrough disks ? I mean using RDMs . if yes then the snapshot process will fail.
Can you also check within vcenter if the snapshot creation is successful?
07-25-2015 04:11 AM
07-27-2015 01:22 AM
Hi SymGuy-IT,
The backup fails for all VMs within the vCenter.
And the snapshots are successfully created when the backups are launched.
07-27-2015 01:38 AM
Hi sdo,
All my disks are online and are listed with diskpart (list disk) from my media server (Backup host for VMware).
07-27-2015 01:40 AM
Hi SymGuy-IT,
The backup fails for all VMs within the vCenter.
And the snapshots are successfully created when the backups are launched.
07-27-2015 06:49 AM
can u send the details of the vmware policy
bppllist <policyname> -L
07-27-2015 07:53 AM
Hi,
You could find the detail in the attached file.
07-27-2015 09:06 AM
Share the detailed job status too. The policy looks OK. meanwhile did you try backup without file level recovery? Please create a fresh set of logs..
bpbkar vxms bpfis bpbrm bptm
07-27-2015 09:17 AM
Check this perhaps it helps!
https://support.symantec.com/en_US/article.TECH208807.html
best regards,
Cruisen
07-27-2015 09:38 AM
Hi SymGuy-IT,
You could find the logs in the atteched file.
I will test the backup without file level recovery and I will inform you.
07-27-2015 10:22 AM
please also send the detailed status of the job you ran
07-27-2015 10:33 AM
Hi,
You could find the detailed status for the job in attached file.
07-27-2015 10:34 AM
I get the same error without "file level recovery" option.
07-27-2015 10:37 AM
The issue is coming from ESXi side.
Following errors can be seen in VxMS log. All other logs I checked which have absolutely normal behaviour from Netbackup side. Here are the entried which you can share with Vmware
17:17:17.0775 : vdOpen:../VixInterface.cpp:495 <ERROR> : VixDiskLib_Open() error: 13
17:17:17.0775 : openLeafSnapshotDisks:../VixGuest.cpp:478 <DEBUG> : vdOpen() error = 13. Calling closeLeafSnapshotDisks()
17:17:17.0775 : log:../Error.cpp:249 <WARN> : Error: 0x00000017 occured in file ../VixGuest.cpp, at line 624
17:17:17.0775 : log:../Error.cpp:249 <WARN> : Error: 0x00000017 occured in file ../VixGuest.cpp, at line 624
17:17:17.0775 : vixMapObjCtl:../VixCoordinator.cpp:990 <ERROR> : Returning: 23
17:17:17.0775 : vix_map_objctl:../libvix.cpp:1275 <ERROR> : Returning: 23
07-27-2015 11:10 AM
Few suggestions -
1. Change the account used to access vCenter. Try the admin/root level access.
2. try with NBD
3. Turn off logging completely.
07-27-2015 01:27 PM
Hi SymGuy-IT,
I had tested all those options without success.
1- I had added the ESXs directly with root and password : ko
2- I created a new policy with NBD : ko
no changes !!