Rebuild Role Instance
Updated: June 29, 2015
The Rebuild Role Instance asynchronous operation reinstalls the operating system on instances of web roles or worker roles and initializes the storage resources that are used by them. If you do not want to initialize storage resources, you can use Reimage Role Instance.
The Rebuild Role Instance request may be specified as follows. Replace <subscription-id> with your subscription ID, <cloudservice-name> with the name of the cloud service, <deployment-slot> with staging or production, or <deployment-name> with the name of the deployment. Replace <role-instance-name> with the name of the role instance.
Required. Specifies that a role instance and its resources must be rebuilt.
Required. Specifies the resources that must be rebuilt. Currently, the only supported value is allLocalDrives.
The following table describes the request headers.
Required. Set this header to application/xml.
Required. Specifies the version of the operation to use for this request. The value of this header must be set to 2013-06-01 or higher.
Required. Must be set to 0.
The response includes an HTTP status code and a set of response headers.
A successful operation returns status code 200 (OK).
The response for this operation includes the following headers. The response may also include additional standard HTTP headers.
A value that uniquely identifies a request made against the management service. For an asynchronous operation, you can call Get Operation Status with the value of the header to determine whether the operation is complete, has failed, or is still in progress.
When the role instance is rebuilt, the instance is taken offline, a fresh guest operating system image is applied, and the data drives that are attached to the instance are initialized. The role instance is then brought back online.