Overview

In actual services, services need to be deployed in different AZs to improve availability due to equipment room faults.

However, when components are deployed in different AZs, each component must be configured as required. This is complex and error-prone. In addition, the components need to be deployed and run immediately after being created, and do not support on-demand deployment. If the component configurations are incorrect, the deployment fails. In this case, you need to delete the components, create them again, and then deploy them.

ServiceStage release management can be used to migrate and upgrade components across AZs.

• Batch clone release tasks can be used to migrate components across AZs.
• Batch upgrade release tasks can be used to upgrade components across AZs and specify the upgrade sequence of components in different AZs.