Problem: The user is unable to move the vApp from its current datastore, to a different on datastore. The user has tried to move the vApp, and the move failed, the vApp started up but claimed that the you could not “copy/clone” the vApp.

The vApp console message would look something like this:

Cause:  Virtual Machine cloning is not permitted by the Axcient Virtual Appliance by design.

This is done for two reasons:

1. Any virtual appliance needs to be associated with a specific Service ID so as to permit successful offsite backups / management using the Axcient RMC. Cloning the vApp results in a situation where a more than one Virtual Appliance instance is associated with the same Service ID.

2. Customers are expected to request / purchase multiple virtual appliances instead of cloning their Axcient Virtual Appliance.

Solution: The main reason to clone the vApp is to deploy multiple instances of the vApp without reordering a new one from Axcient each time. For the present this is not possible and you must order a new vApp each time.