Restarting a CBH Instance

Scenarios

To fix an abnormal instance, you can try restarting it.

Important Notes

• Before restarting a bastion host instance, make sure no operations or O&M tasks are in progress. Once the bastion host instance is restarted, ongoing operations and O&M tasks will be forcibly logged out immediately.
• Restarting a bastion host instance will interrupt system services for about 5 minutes. If you upgrade an instance and then change its specifications, the restart may take a longer time. During the restart, the Status of the instance is Restarting, and the bastion host system is unavailable.

Notes and Constraints

Only bastion hosts in the Running state can be restarted.

Restarting an Instance

1. Log in to the CBH console.
2. Click in the upper left corner on the displayed page and select a region.
3. Locate the target instance. In the Operation column, choose More > Restart.
4. In the displayed dialog box, click OK.
   • To forcibly restart a CBH instance, select the Forcibly restart check box. Forcibly restarting an instance may cause data loss. Make sure all data files have been saved before performing this operation, and no operations are performed in the mapped bastion host system.
   • During the restart, an error might be reported indicating that the instance is abnormal and asking you to contact technical support. This is normal.
   • The instance status changes from Running to Restarting > Running. When the instance status changes to Running, the bastion host instance can be used.