Restore of a VM to vCloud doesn't add the VM into the vApp due to bprd crashing

Article: 100045812
Last Published: 2019-06-25
Ratings: 0 0
Product(s): Appliances, NetBackup & Alta Data Protection

Problem

Restore of a VM to vCloud doesn't add the VM into the vApp due to VCD XML size of zero causing bprd crashing.

Environment

Issue has been seeing with:

NetBackup 8.1.2 and 8.2

vCloud Director 9.5 and 9.7

Error Message

Search the system for a bprd crash:

Apr 15 09:22:42 <hostname> kernel: bprd[25794]: segfault at 0 ip 00007fca816ac677 sp 00007ffc238e6e90 error 4 in libnbbase.so[7fca81612000+2c8000]


Restore completes, VM can be seen in vCenter.  However In vCloud Director the VM is displayed as discovered VM and is not added to the destination vApp.

Cause

Bprd crashes because the VM metadata length in the image header was unexpectedly zero.  Soap queries to vCloud Director for the properties of the VM and vApp did not return expected length or transport type in the soap headers.
 

Solution

There are no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. However, the issue is currently scheduled to be addressed in the next major revision of the product. Please note that Veritas Technologies LLC reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests.  Veritas’ plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

References

Etrack : 3973533 Etrack : 3983406

Was this content helpful?