Updated on 2025-06-23 GMT+08:00

Copying a Dedicated Load Balancer

Overview

After a copy is complete, you will get a new load balancer that has the same basic settings, listeners, and log settings as the original one.

This feature is available in certain regions. You can see which regions support them on the console.

Constraints

  • The new load balancer must be in the same VPC as the original load balancer.
  • The public network configuration of the original load balancer will not be copied. You can bind an EIP to the new load balancer after the copy is complete.
  • Only pay-per-use load balancers can be copied. After the copy is complete, you can change the billing mode of the new load balancer.

Procedure

  1. Go to the load balancer list page.
  2. Locate the load balancer and click Copy in the Operation column.
    In the Copy Load Balancer dialog box, configure parameters for the new load balancer based on Table 1.
    Table 1 Parameters for the new load balancer

    Parameter

    Description

    New Load Balancer Name

    Specifies the name of the new load balancer.

    The name defaults to original-load-balancer-name-copy. You can change it if you want to.

    AZ

    Specifies the AZs of the new load balancer, which defaults to the same AZs as those of the original load balancer. You can change it if you want to.

    An AZ is a part of a region and has its own independent power supplies and networks. AZs are physically isolated but interconnected through an internal network.

    For details about how to change AZs, see Changing an AZ.

    Billing Mode

    Specifies the billing mode of the new load balancer. Only Pay-per-use is available.

    Specification

    Specifies the specifications of the new load balancer. It defaults to the same specifications as the original load balancer and cannot be changed.

    Network Type

    Specifies the private network configurations of the new load balancer. It defaults to the same settings as the original load balancer and cannot be changed.

    The public network configuration of the original load balancer will not be copied. You can bind an EIP to the new load balancer after the copy is complete.

    Frontend Subnet

    Specifies the frontend subnet where the new load balancer will work, which defaults to the same subnet as that of the original load balancer. You can change it if you want to.

    A private IP address in this subnet will be assigned to the new load balancer to receive client requests.

    IPv4 Address

    Specifies how you want to assign an IPv4 address to the new load balancer. There are two options:

    • Automatically assign IP address: The system automatically assigns an IPv4 address to the load balancer.
    • Manually specify IP address: You need to manually specify an IPv4 address for the load balancer.

    IPv6 Address

    Specifies how you want to assign an IPv6 address to the new load balancer. This parameter is available only when the original load balancer can route IPv6 requests.

    Automatically assign IP address: The system automatically assigns an IPv6 address to the load balancer.

    Backend Subnet

    Specifies the backend subnet where the new load balancer will work, which defaults to the same subnet as that of the original load balancer. You can change it if you want to.

    The load balancer uses the IP addresses in the backend subnet to forward requests to the backend servers.

    Dedicated load balancers will use some IP addresses in the backend subnet. Check the number of required IP addresses on the console.

    If you select a different backend subnet for the new load balancer, ensure that the security group and network ACL rules of backend servers allow traffic from this backend subnet.

    Enterprise Project

    Specifies an enterprise project by which cloud resources and members are centrally managed.

    The default project is default.

    Backend Server Group

    Specifies whether to reuse or copy backend server groups.

    You can reuse or copy backend server groups only when the new and original load balancers are in the same enterprise project.

    • Reuse: The backend server groups of the original load balancer will be associated with the new load balancer.
    • Copy: New backend server groups with the same settings as those of the original load balancer will be created and associated with the new load balancer.
  3. Click OK.

    The copy duration depends on the load balancer settings. In general, each copy completes within 2 minutes.

  4. Wait until the copy is complete and click Close.