Got alerts after migrated to BE15

[William_Lawance]

Hi,

Got alerts after migrated to BE15. Refe to attachement.

Found there is no unallocated partition in server.

• Please advice what's the root cause even no unallocated partition
• Anyway to removw these alerts on this server

Thanks

[VJware]

When a full SDR-enabled backup runs, a configuration file is created for the server being backed up. This file contains the disk layout of each and every disk present on the server whether its being backed up or not. And this file is required for the P2V operation.

For unsupported disks, this file does not get created and then the exception occurs.

I have already mentioned the reason for this alert in your earlier post - https://www-secure.symantec.com/connect/forums/failed-load-configuration-xml-file-alert

Pls do not open multiple threads for the same issue.

[William_Lawance]

This server has unsupported disk ?

Please refer to attachment 0001

[VJware]

Yes, the server seems to have a non-supported disk configuration which causes the failure to create the p2v.xml file. There are quite a few configurations which are not supported for P2V as mentioned in the KB article posted in your old post. Debugging usually helps one to identify as to what is the unsupported config. It could be a GPT disk or it could be an uninitialized disk and so on.

How to fix it ?

- Enable SGmon debugging on the BE media server and check the beremote log. It will show why the p2V.xml exception is occuring. If you need help with debugging, pls log a formal support case. Thanks.

[William_Lawance]

It should be caused by EFI System partition.

[VJware]

I don't think its due to EFI. Are any disks GPT ?