Halaman ini belum tersedia dalam bahasa lokal Anda. Kami berusaha keras untuk menambahkan lebih banyak versi bahasa. Terima kasih atas dukungan Anda.

Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Copying a Dedicated Load Balancer

Updated on 2024-11-14 GMT+08:00

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.

NOTE:

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.

Kami menggunakan cookie untuk meningkatkan kualitas situs kami dan pengalaman Anda. Dengan melanjutkan penelusuran di situs kami berarti Anda menerima kebijakan cookie kami. Cari tahu selengkapnya

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback