Updated on 2024-09-20 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.

Notes and Constraints

  • The new load balancer must be in the same VPC as the original one.
  • 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 AZ of the new load balancer, which defaults to the same AZ as that 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 AZ planning, 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, which cannot be changed.

    Network Type

    Specifies the specifications of the new load balancer. It defaults to the same specifications as the original load balancer, which 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 of where the new load balancer will work, which defaults to the 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 load balancer to receive client requests.

    IPv4 Address

    Specifies how you want the IPv4 address to be assigned. 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 to the load balancer.

    IPv6 Address

    Specifies how you want the IPv6 address to be assigned. If the original load balancer can route IPv6 requests, the new load balancer can too.

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

    Backend Subnet

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

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

    Dedicated load balancers will occupy some IP addresses in the backend subnet. See 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 Groups

    Specifies whether to reuse or copy a backend server group.

    If you have enabled enterprise project and use the same project for both the new and original load balancers, you can enable this option.

    • Reuse: The backend server groups of the original load balancer will be associated with the new load balancer.
    • Copy: A new backend server group with the same settings 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.