When a deployment fails—for example, a server crashes or network connectivity lapses—you can often recover as follows:
In the Business Control Center Admin Console, navigate to the Details tab for the deployment’s target site and stop the deployment.
Click Resume.
The deployment operation picks up where it stopped and continues to completion. You can resume full and incremental deployments, and you can resume a deployment multiple times in the event of successive failures.
If attempts to resume deployment fail:
Stop the deployment.
Click Rollback. The target site deployment agents undo all work completed thus far in the failed deployment and restore the previous set of assets as the active set on the target. Only incremental deployments are candidates for roll back; a full deployment starts by deleting all target site data, which cannot be restored.
Deploy the project again.
Note: You can roll back only once. If a failure occurs while rolling back a target site, the target site is in an indeterminate state. In this situation you must perform a full deployment of the previous set of assets (created by one or more projects) to reestablish it as the active set on the target site.
After deployment recovery is complete, the target site is in a known, stable state and you can resume deploying to it as usual.
For information on full and incremental deployments, see Deployment Scope.
Resuming Deployment from a Failed Asset Management Server
In a clustered environment, an asset management server might fail during a deployment that it initiated. In that case, you cannot access the deployment from other asset management servers in the same cluster, When viewed from other servers, the Details tab for the deployment target does not display the usual deployment options, such as resume, stop, and roll back. Instead, it displays the following error message:
An RMI error encountered calling remote current deployment 'deployment-id' to target 'Production': getStatus() may or may not have been passed to the running deployment
After the initiating server restarts, all available actions that pertain to the deployment become available again, and are accessible from any asset management server in the ATG Content Administration cluster.