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
Situation Awareness
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

Configuring Management Data Backup Storage

Updated on 2024-10-25 GMT+08:00

Configure the backup storage for eBackup system management data (database and configuration files), which can be used to restore the eBackup system in the event of a disaster. eBackup supports the NFS, S3, FTP and SFTP storage as the backup storage of management data. This section describes how to configure the backup storage of the S3 type.

Context

  • When backing up eBackup management data, calculate the shared storage capacity in advance. If the shared storage capacity is not enough, the latest backup job will fail. The shared storage capacity is related to the backup data retention policy:
    • If Daily Backup is selected

      The capacity of shared storage for storing backup management data = [(Number of yearly backups + Number of monthly backups + Number of weekly backups + Number of daily backups +1) x 10 + 15] GB.

      • For example, if the default retention policy is used, the capacity of shared storage for storing backup management data = [(0 + 1 + 1 + 1 + 1) × 10 + 15] GB = 55 GB.
      • If Number of retained copies generated in yearly backup is set to Permanent, planned capacities depend on the number of years for saving backups. The capacity of shared storage for storing backup management data = [(Number of years for saving backups + Number of monthly backups + Number of weekly backups + Number of daily backups + 1) × 10 + 15] GB.
    • If Hourly Backup is selected

      The capacity of shared storage for storing backup management data = [(Number of yearly backups + Number of monthly backups + Number of weekly backups + Number of daily backups + Number of hourly backups + 1) x 10 + 15] GB.

      • For example, if the default retention policy is used, the capacity of shared storage for storing backup management data = [(0 + 1 + 1 + 1 + 1 + 1) × 10 + 15] GB = 65 GB.
      • If Number of retained copies generated in yearly backup is set to Permanent, planned capacities depend on the number of years for saving backups. The capacity of shared storage for storing backup management data = [(Number of years for saving backups + Number of monthly backups + Number of weekly backups + Number of daily backups + Number of hourly backups + 1) × 10 + 15] GB.
  • Configure separate backup storage space for eBackup management data.
  • You are advised to use the purchased hybrid cloud backup vault for S3 backup storage.

Prerequisites

  • You have planned the capacity of the S3 shared storage. The capacity of the shared storage must meet the requirements. Or, the backup job will fail. For details, see Context.
  • You have obtained the domain name or IP address of the S3 storage service plane, and the name, AK, and SK of the bucket that stores backup data.

Procedure

  1. Log in to the eBackup management system using the admin account.

    For details, see Logging In to eBackup.

  2. In the navigation tree, choose > Configuration > Management Data Backup.
  3. Click Set Backup Storage.
  4. Configure the backup storage of the eBackup management data.

    Table 1 describes the parameters.
    NOTICE:

    Do not use the same bucket as the backup storage of the management data and user VM data. Or, backup jobs will fail.

    Table 1 Backup storage (S3) parameters

    Parameter

    Description

    Setting Rule

    Type

    Type of the backup storage for the management data

    S3

    Protocol

    Network protocol for the communication between the eBackup management system and S3 storage. Options include HTTP and HTTPS.

    • If HTTPS is specified, import a valid certificate to verify the S3 storage. Obtain the certificate from the S3 storage administrator in advance.
    • Security risks arise if the protocol is set to HTTP. You are advised to select the HTTPS protocol.

    AK

    Access Key (AK) confirms the identity of a user accessing the object-based storage system.

    -

    SK

    Secret Key (SK) allows a user to access an object-based storage system. Secret access keys and access key IDs are in one-to-one match.

    -

    Path

    Path to access the S3 storage

    IPV4 path format: IP address or domain name:/bucket name

    IP address and domain name indicate the service IP address and the domain name of the object-based storage system, respectively. A bucket name contains 3 to 255 characters and can contain letters, digits, and special characters. Special characters include periods (.), hyphens (-), and underscores (_).

    Identifier

    Name of a subdirectory saving management data backups, which differentiates the management data backups of different eBackup systems

    An identifier contains 1 to 64 characters and can contain only letters, digits, underscores (_), and hyphens (-).

    If a subdirectory with the same name already exists, the system uses the existing subdirectory forcibly.

    Whether to write data if a subdirectory with the same name already exists
    • If selected

      The backup data will be written to the subdirectory even if a subdirectory with the same name exists.l

      NOTE:

      If multiple eBackup systems use the same backup subdirectory, management data backups may be unavailable. Use a subdirectory for each eBackup system.

    • If not selected

      You cannot create a backup subdirectory if a subdirectory with the same name already exists. In this case, use a different name for the subdirectory.

    -

  5. Click OK.

    After the configuration is completed, the backup storage configuration status will be shown to the right of the Set Backup Storage button.

    • : The configuration is in progress.
    • No icon: The configuration is successful.
    • : The configuration failed.
    NOTE:

    If the configuration fails, click Set Backup Storage and reconfigure.

  6. (Optional) Configure a backup policy for the management data.

    NOTE:

    To ensure the system database security of the backup software, you are advised to back up the database periodically. The system performs full backups for every time.

    • Click Automatic Backup Settings. In the dialog box that is displayed, configure an automatic backup policy as prompted.
      • If Daily Backup is selected, the default system settings are as follows.
        Figure 1 Setting daily backup
      • If Hourly Backup is selected, the default system settings are as follows.
        Figure 2 Setting hourly backup
      • Hourly backup: Backup generated every n hour(s) in the system.
      • Daily backup: first backup generated per day.
      • Weekly backup: first backup generated on Monday per week.
      • Monthly backup: first backup generated on the first Monday per month.
      • Yearly backup: first backup generated on the first Monday per year.
      NOTE:

      You are advised to set the backup time to off-peak hours to reduce impact on services, for example, 00:00 to 02:00.

      After the automatic backup policy is configured, restart the eBackup process on the backup server to make the policy take effect. For details, see "Restarting the eBackup Process."

      If the backup time overlaps (for example, monthly backup and weekly backup are both performed on Monday), the system performs backups based on the backup policy with the highest priority. The priorities of the following backup policies descend: yearly backup > monthly backup > weekly backup > daily backup > hourly backup.

    • Click Immediate Manual Backup. The backup job is executed immediately.
      NOTE:

      You are advised to manually back up the system database immediately before and after a major operation, such as an upgrade and critical data modification.

Follow-Up Operations

If you need to delete unnecessary backup data, you can find and delete the data according to package names of backup data. The file name is in the format of [Backup data type][Backup type][Service name][Year][Month][Day][Minute][Second][Backup period][No.].db. The following uses FMTEBACKUP20170811110307X001.db as an example.

Table 2 Parameter description

Parameter

Description

Rule

F

Backup type

The value can be:

  • F: full backup
  • I: incremental backup

MT

Backup option

The value can be:

  • MT: manual backup
  • AT: automatic backup

EBACKUP

Service name

Fixed at EBACKUP

20170811110307

Time when the backup was executed

In the format of YYYYMMDDHHMMSS

X

Backup Period

The value can be:

  • D: daily backup
  • W: weekly backup
  • M: monthly backup
  • Y: yearly backup
  • X: manual backup (Manual backups will not be automatically deleted.)
NOTE:

If the backup time overlaps (for example, monthly backup and weekly backup are both performed on Monday), the system performs backups based on the backup policy with the highest priority. The priorities of the following backup policies descend: yearly backup > monthly backup > weekly backup > daily backup > hourly backup.

001

Backup data number

-

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback