Video Screencast Help

CPU configuration is not preserved following a full virtual machine restore with the Backup Exec Agent for VMware.

Created: 10 Oct 2012
Chris Riley's picture
Login to vote
Me Too!I have the same issue
Product(s): Backup Exec - 2012, Backup Exec
Severity: Minor functionality
Status: Investigating/gathering information
Tech Note: More Information


Following a full virtual machine restore using the Backup Exec Agent for VMware, the CPU configuration is not preserved.

The example below shows a virtual machine configured with 4 CPUs (2 virtual sockets, 2 cores per socket). Following a restore back to the original location, this changes to 4 CPUs (4 virtual sockets, 1 core per socket).

Figure 1:


ESXi 5.0


The only workaround available is to manually set the correct CPU configuration following the restore.

Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns.  For information on how to contact Symantec Sales, please see

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.