cancel
Showing results for 
Search instead for 
Did you mean: 

P2V Coversion fails with Status 7

Greetings,

I  got involved with one P2V conversion issue which is segementation fault (core dumping) when executing through GUI and nbrestorevm command fails with P2V conversion job status 7.

We have Appliances Based Master/Media Server running 2.6.1.2 version NetBackup.

VIC (VMware Instance Converter) is on VM based Windows 2008R2 Server also running on 7.6.1.2 version NetBackup client.

vSphere/vCenter is 5.5 and ESXi 5 version.

Actual Physical Server is Windows 2008R2 with around 300GB of two disk volumes.

I could successfully restore test VMware VM's backup and restore to verify the permission and networking setting which includes firewall setting. In this case VIC VM/Proxy was involved though. I'm suspecting 32 Bit VMware Coverter or wrong VDDK version.

Let me know If you have faced similar issue and have resolved the issue or have idea about any limition on 7.6.1.2.

 

Cheers!

Veerendra

2 Solutions

Accepted Solutions
Accepted Solution!

If you are able to clarify

If you are able to clarify whether the ESXi v5 (does this imply v5.0?) have been patched or not, then this may help some others provide comment.

This TN has a link to another TN detailing how to check logs:

https://support.symantec.com/en_US/article.HOWTO92139.html

If you could attach the logs here, then someone will probably check them for you.  Please don't post the text in a posting, if you see what I mean :catwink:    Thanks.

View solution in original post

Accepted Solution!

Your version is up-to-date,

Your version is up-to-date, but maybe you want to check this known issue:

http://www.symantec.com/docs/TECH222564

just to see if those logs error message is similar, or if the workaround can resolve your issue. 

Otherwise, it's better to log a support case since this may require support analysis to the detailed bmrb2vrst log (OID 434)  

View solution in original post

2 Replies
Accepted Solution!

If you are able to clarify

If you are able to clarify whether the ESXi v5 (does this imply v5.0?) have been patched or not, then this may help some others provide comment.

This TN has a link to another TN detailing how to check logs:

https://support.symantec.com/en_US/article.HOWTO92139.html

If you could attach the logs here, then someone will probably check them for you.  Please don't post the text in a posting, if you see what I mean :catwink:    Thanks.

View solution in original post

Accepted Solution!

Your version is up-to-date,

Your version is up-to-date, but maybe you want to check this known issue:

http://www.symantec.com/docs/TECH222564

just to see if those logs error message is similar, or if the workaround can resolve your issue. 

Otherwise, it's better to log a support case since this may require support analysis to the detailed bmrb2vrst log (OID 434)  

View solution in original post