01-13-2014 04:40 AM
Follow the following logs backup host attached: detailed status, bpbkar, bpfis.
Can someone help me?
Solved! Go to Solution.
01-13-2014 09:25 AM
16:49:00.0912 : g_vixInterfaceLogger:bvix.cpp:1829 <INFO> : diskLibPlugin: 2014-01-13T14:49:00.912-02:00 [04736 error 'Default'] Cannot use advanced transport modes for vw-vcenter-01.central.iamspe.com.br:443/moref=vm-26190/snapshot-28300: Cannot create directory C:\Windows\TEMP\vmware-SYSTEM\422df1b7-b118-8c38-c8b9-1c1381d58d37-vm-26190.
one of possible reasons
File lock or corruption in temp path
Removed all files and directories in temp path
C:\DOCUME~1\OWENT~1.ADM\LOCALS~1\Temp\vmware-useraccount\
http://www.symantec.com/business/support/index?page=content&id=TECH170743
01-13-2014 05:13 AM
Lots to read there but at the end of the last log it says this:
[The host is not licensed for this feature]
And the first and second logs says this: ERR - Error opening the snapshot disks using given transport mode: Status 23
Plus invalid option: -block_incr
So there is something in how you have the job setup that is incorrect - tell us all of the options you have setup in your policy so that we can pin down where the error is - it could just be bad credentials to you vCenter server causing all of this
01-13-2014 05:29 AM
follows the policy settings in Appendix bppllist printscreen and the police
Regards
01-13-2014 05:32 AM
looks like you are using the SAN transport...
some more details please
1)what is the netbackup version and OS in backup host?
2) what is the Vcenter version and VM hardware version?
3) does this all Storage LUNs that are mapped to ESXi hosts are mapped to Backup host too?
4) what is the Storage you are using?
01-13-2014 05:35 AM
Based on two of the logs saying it cannot be backed up using the selected method - which on the policy is SAN - then either the media server (VMware Backup Host) cannot see the datastore that client is located on - or that client is on local storage - or it is a template - or similar issue that prevents it being backed up via the SAN
Try it using NBD first as a check that the vCenter rights are actually good enough to perform the backup - if that works you then need to identify why it cannot backup via the SAN
01-13-2014 05:56 AM
environment:
1. Backup host OS Windows 2008 R2 Enterprise
2. Vcenter version 5.0 hadware version ESX 5.0
3. Yes
4. HP 3PAR
01-13-2014 06:04 AM
Have you tried a nbd backup for this client yet?
01-13-2014 06:12 AM
yes the backup gave the same error
01-13-2014 06:14 AM
environment:
1. Backup host OS Windows 2008 R2 Enterprise
2. Vcenter version 5.0 hadware version ESX 5.0
3. Yes
4. HP 3PAR
01-13-2014 06:17 AM
The strange thing is that I can make up other vms these same conditions successfully
01-13-2014 06:33 AM
Error opening the snapshot disks using given transport mode: Status 23
see the Solution in this older thread:
https://www-secure.symantec.com/connect/forums/error-opening-snapshot-disks-using-given-transport-mode-status-23
01-13-2014 06:39 AM
If you get the same error when you try the backup over the LAN there it sounds like you have an issue with your rights in vCenter - do all other clients work?
If all other clients work then it may be specific to that client - so try unchecking BLIB, file level restore, quiesce etc. to see which one solves the issue - it may be caused by Ubuntu not supporting one of the features you have selected in the policy
01-13-2014 07:32 AM
could you attach the VXMS logs to this post
for both SAN backup and NBD backup.
see the below note for VXMS log enable
Delete the contents of:
C:\Program Files\Common Files\VERITAS\VxMS\Logs
To enable VxMS log, run regedit and set the value of following registry value to 7580 hexadecimal
HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxMS\Logging
Also create the following for Backup jobs that fails to mapped the disk:
DWORD registry value "VIXLog" under the registry key
"HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxMS\" and set the value of VIXLog to 1
Assuming C: to be the root drive, the VxMS logs will be collected at: C:\Program Files\Common Files\VERITAS\VxMS\Logs
Change the logging level back to 0 after testing is completed
01-13-2014 09:06 AM
I performed the tests follows the attached logs
01-13-2014 09:25 AM
16:49:00.0912 : g_vixInterfaceLogger:bvix.cpp:1829 <INFO> : diskLibPlugin: 2014-01-13T14:49:00.912-02:00 [04736 error 'Default'] Cannot use advanced transport modes for vw-vcenter-01.central.iamspe.com.br:443/moref=vm-26190/snapshot-28300: Cannot create directory C:\Windows\TEMP\vmware-SYSTEM\422df1b7-b118-8c38-c8b9-1c1381d58d37-vm-26190.
one of possible reasons
File lock or corruption in temp path
Removed all files and directories in temp path
C:\DOCUME~1\OWENT~1.ADM\LOCALS~1\Temp\vmware-useraccount\
http://www.symantec.com/business/support/index?page=content&id=TECH170743
01-13-2014 10:27 AM
01-13-2014 10:42 AM
good catch Nagalla