- What's New
- Function Overview
-
Service Overview
- EVS Infographics
- What Is EVS?
- Disk Types and Performance
- Device Types and Usage Instructions
- Shared EVS Disks and Usage Instructions
- EVS Encryption
- EVS Backup
- EVS Snapshot (OBT)
- Differences Between EVS Backups and EVS Snapshots
- EVS Three-Copy Redundancy
- Billing
- Permissions
- Constraints
- EVS and Other Services
- Basic Concepts
- Change History
- Getting Started
-
User Guide
- Permissions Management
- Purchasing and Using an EVS Disk
- Attaching an Existing EVS Disk
- Viewing EVS Disk Details
- Changing the EVS Disk Type (OBT)
- Expanding EVS Disk Capacity
- Detaching and Deleting an EVS Disk
- Managing EVS Snapshots (OBT)
- Managing Encrypted EVS Disks
- Managing Shared EVS Disks
- Managing EVS Disk Backups
- Managing EVS Transfers
- Managing EVS Tags
- Managing EVS Quotas
- Cloud Eye Monitoring
- Recording EVS Operations Using CTS
-
Best Practices
- Using LVM to Manage EVS Disks
- Handling Insufficient Disk Space on a Windows ECS
- RAID Array Creation with EVS Disks
-
Extending Disk Partitions and File Systems (Linux Kernel Earlier Than 3.6.0)
- Preparing for Extending Disk Partitions and File Systems (Linux Kernel Earlier Than 3.6.0)
- Extending System Disk Partitions and File Systems (Linux Kernel Earlier Than 3.6.0)
- Extending Data Disk Partitions and File Systems (Linux Kernel Earlier Than 3.6.0)
- Extending SCSI Data Disk Partitions and File Systems (Linux Kernel Earlier Than 3.6.0)
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
- API Version Query
- API v2
-
OpenStack Cinder API v2
-
EVS Disk
- Creating EVS Disks
- Deleting an EVS Disk
- Updating an EVS Disk
- Querying EVS Disks
- Querying Details About All Disks
- Querying Details About a Disk
- Querying EVS Disk Types
- Querying Details About an EVS Disk Type
- Querying Details of Tenant Quotas
- Adding the Metadata for an EVS Disk
- Querying Metadata of an EVS Disk
- Updating the Metadata of an EVS Disk
- Querying One Piece of Metadata for an EVS Disk
- Updating One Piece of Metadata for an EVS Disk
- Deleting One Piece of Metadata for an EVS Disk
- Querying Extension APIs
- Querying All AZs
-
EVS Disk Actions
- Expanding Capacity of an EVS Disk
- Setting Bootable Flag for an EVS Disk
- Setting Read-Only Flag for an EVS Disk
- Exporting EVS Disk Data as an Image
- Attaching an EVS Disk (Deprecated)
- Detaching an EVS Disk (Deprecated)
- Reserving an EVS Disk (Deprecated)
- Canceling Reservation of an EVS Disk (Deprecated)
-
EVS Snapshot
- Creating an EVS Snapshot
- Deleting an EVS Snapshot
- Updating an EVS Snapshot
- Querying EVS Snapshots
- Querying Details About EVS Snapshots
- Querying Details About an EVS Snapshot
- Adding Metadata of an EVS Snapshot
- Querying Metadata of an EVS Snapshot
- Updating One Piece of Metadata for an EVS Snapshot
- Updating the Metadata of an EVS Snapshot
- Querying One Piece of Metadata for an EVS Snapshot
- Deleting One Piece of Metadata for an EVS Snapshot
- EVS Disk Transfer
-
EVS Disk
- Out-of-Date APIs
- Permissions Policies and Supported Actions
- Appendix
- Change History
- SDK Reference
-
FAQs
- Summary
-
General
- How Do I Start Using a Newly Purchased Disk?
- Can EVS Disks Be Used Directly for Storage?
- Can EVS Disks Be Used Alone?
- How Can I View My Disk Details?
- How Do I Change the Name of My Disk?
- Can I Change the AZ of My Disk?
- Can I Change the Disk Type, Device Type, or Sharing Attribute of My Disk?
- What Should I Do If an Error Occurs on My EVS Disk?
- How Can I Obtain ECS NIC Information?
- Why Do Some of My EVS Disks Not Have WWN Information?
- How Can I Migrate Data from an EVS Disk?
- What Are the Differences Between System Disks and Data Disks?
- Will I Lose My Disk Data If I Reinstall ECS OS, Change the OS, or Change the ECS Specifications?
- How Can I Export the Original Data After I Changed My Server OS from Windows to CentOS?
- What Are the Differences Between MBR and GPT Partition Styles?
- What Does the "reserveVolume" Trace Mean in CTS?
- How Can I Download My EVS Disk Data to a Local PC?
- How Can I Upload Files to My EVS Disk?
- Billing
-
Attachment
- Why Can't I View the Attached Data Disk on the Server?
- Why Can't I Attach My Disk to a Server?
- Can I Attach a Disk to Multiple Servers?
- Can I Attach a Disk to a Server in a Different AZ?
- How Can I Add a Data Disk to an Existing Server?
- Can I Attach Different Types of Disks to the Same Server?
- Can I Switch Between System Disks and Data Disks?
- What Should I Do If a Linux EVS Disk Is Attached to a Windows Server?
- Can I Change the Function of a System Disk or Data Disk Purchased Along with a Server?
- How Do I Obtain My Disk Device Name in the ECS OS Using the Device Identifier Provided on the Console?
-
Capacity Expansion
- Can I Reduce or Temporarily Expand the Disk Capacity?
- What Are the Differences Between Expanding Capacity by Expanding an EVS Disk and Creating a New EVS Disk?
- Will My Disk Data Be Lost After I Expand the Disk Capacity?
- Can I Use Backups or Snapshots Created Before Capacity Expansion to Restore Data on Expanded Disks?
- Do I Need to Restart the Server After Expanding the Disk Capacity?
- Do I Need to Detach an EVS Disk Before Expanding Its Capacity?
- What Should I Do If My Disk Capacity Exceeds 2 TiB After Expansion?
- How Can I Allocate Newly Added Space to a New Partition?
- How Can I Allocate Newly Added Space to an Existing Partition?
- Why Did My Disk Capacity Remain Unchanged on the Server After Capacity Expansion?
- Why Can't I Expand Capacity for My Disk?
- How Do I Extend the File System of an Unpartitioned Data Disk in Linux?
- How Do I Extend the Root Partition of a Quickly Provisioned BMS?
- How Do I View the Disk Partition Style in Linux?
- Detachment
- Deletion
-
Capacity
- What Is the Maximum Capacity Supported for the System and Data Disks?
- What Should I Do If My Disk Starts to Run Out of Space?
- How Do I Clean Up My Disk Space on a Windows Server?
- What Can I Do If the Capacity of My Disk Reaches the Maximum But I Still Need More Space?
- What Should I Do If I Use fdisk to Initialize a Disk Larger Than 2 TiB and Then the Space in Excess of 2 TiB Cannot Be Displayed?
- How Can I View My Disk Usage?
- How Can I Monitor My Disk Usages?
- Can I Transfer the Data Disk Capacity to a System Disk?
- Why the Space of My New Disk Is Full After I Uploaded Only 500 MB of Files to the Disk?
-
Snapshot
- What Are the Typical Causes of a Snapshot Creation Failure?
- Does EVS Support Automatic Snapshot Creation?
- Can I Create Snapshots for Multiple Disks at a Time?
- How Is a Snapshot Created for My Disk?
- Why Can't I Roll Back My Disk Data from a Snapshot?
- Can I Roll Back Data from a Snapshot After Reinstalling the OS or Formatting the Disk?
- How Is the Snapshot Size Calculated?
- Do Snapshots Take Space on the Disk?
- Can I Perform Multiple Rollback Operations for a Snapshot?
- Can I Replicate Snapshots to Other Regions or Accounts?
- Why Can't I Find My Snapshot?
- Can I Use a Snapshot to Create a Disk and Roll Back Disk Data at Almost the Same Time?
- Can I Modify Data in My EVS Snapshot?
-
Performance
- How Do I Test My Disk Performance?
- Why Does My Disk Performance Test Using Fio Have Incorrect Results?
- How Can I Handle a Slowdown in Disk Read/Write Speed or Increased I/Os?
- How Can I Improve My Disk Performance?
- Why My Disk's Read IOPS Can't Reach the Theoretical Maximum IOPS When the Disk I/O Usage Is Almost 100%?
- Sharing
- Backup
CBR Overview
What Is CBR?
Cloud Backup and Recovery (CBR) enables you to easily back up cloud servers and cloud disks. In case of a virus attack, accidental deletion, or software or hardware fault, you can restore data to any point when the data was backed up.
CBR protects your workloads by ensuring the security and consistency of your data.
CBR Architecture
CBR involves backups, vaults, and policies.
- Backup
A backup is a copy of a particular chunk of data and is usually stored elsewhere so that it may be used to restore the original data in the event of data loss. There are the following types of backups:
- Cloud server backup: uses the consistency snapshot technology to protect data for ECSs and BMSs. Backups of non-database servers are non-database server backups, and those of database servers are application-consistent backups.
- Cloud disk backup: provides snapshot-based backups for EVS disks.
- Vault
CBR stores backups in vaults. Before creating a backup, you need to create at least one vault and associate the resources you want to back up with the vaults. Then the resources can be backed up to the associated vaults.
Vaults can be either backup vaults or replication vaults. Backup vaults store resource backups, and replication vaults store backup replicas.
Different types of resources must be backed up to different types of vaults. For example, cloud servers must be backed up to server backup vaults, not disk backup vaults or any other types of vaults.
- Policy
There are backup policies and replication policies.
- A backup policy defines when you want to take a backup and for how long you would retain each backup.
- A replication policy defines when you want to replicate from backup vaults and for how long you would retain each replica. Backup replicas are stored in replication vaults.
Backup Mechanism
The first backup is a full backup and backs up all used data blocks.
For example, if a disk size is 100 GB and 40 GB has been used, only the 40 GB of data is backed up.
Subsequent backups are incremental backups. An incremental backup backs up only the data changed since the last backup to save the storage space and backup time.
When a backup is deleted, data blocks will not be deleted if they are depended on by other backups, ensuring that other backups can still be used for restoration. Both a full backup and an incremental backup can be used to restore data to a given backup point in time.
When creating a backup of a disk, CBR also creates a snapshot for it. CBR keeps only the latest snapshot. Every time it creates a new snapshot during backup, it deletes the old snapshot.
CBR stores backups in OBS to ensure data security.
Backup Options
CBR supports one-off backup and periodic backup. A one-off backup task is manually created by users and is executed only once. Periodic backup tasks are automatically executed based on a user-defined backup policy.
Item |
One-Off Backup |
Periodic Backup |
---|---|---|
Backup policy |
Not required |
Required |
Number of backup tasks |
One manual backup task |
Periodic tasks driven by a backup policy |
Backup name |
User-defined backup name, which is manualbk_xxxx by default |
System-assigned backup name, which is autobk_xxxx by default |
Backup mode |
Full backup for the first time and incremental backup subsequently, by default |
Full backup for the first time and incremental backup subsequently, by default |
Application scenario |
Executed before patching or upgrading the OS or upgrading an application on a resource. A one-off backup can be used to restore the resource to the original state if the patching or upgrading fails. |
Executed for routine maintenance of a resource. The latest backup can be used for restoration if an unexpected failure or data loss occurs. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.