No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionCloud 6.3.1.1 Solution Description 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Restrictions

Restrictions

Before using EVS, learn the restrictions described in Table 8-11.

Table 8-11 Restrictions on EVS

Item

Restrictions

Backend storage

  • Huawei storage devices supported in the Region Type I scenario include enterprise storage OceanStor V3/V5, Dorado V3, and distributed storage FusionStorage. Huawei storage devices supported in Region Type II and Region Type III scenarios include enterprise storage OceanStor V3/V5 and Dorado V3. You can visit Cloud Computing & Big Data Information Service Platform to query the specific storage models and versions.
  • The supported heterogeneous storage type and version are HP 3PAR 7200.
  • Heterogeneous storage access supports KVM virtualization and BMS, but does not support VRM virtualization.
  • Dorado V3 supports Kernel-based Virtual Machine (KVM) and Bare Metal Server (BMS), but does not support Virtualization Resource Management (VRM).
  • An AZ can contain multiple Huawei SAN storage devices, such as OceanStor V3/V5 and Dorado V3. FusionStorage, Huawei SAN storage, and heterogeneous storage cannot be used in one AZ.
  • It is recommended that a disk type contains only one type of backend storage to ensure that backend storage has the same performance.

Creating an EVS disk

  • When the backend storage type is heterogeneous: Blank EVS disks can be created and EVS disks can be created from an existing disk or a snapshot. EVS disks cannot be created from a backup and the disk type cannot be VBD or shared.
  • BMSs cannot use EVS disks as system disks.
  • Shared disks can be used as data disks and cannot be used as system disks.
  • When you use an existing disk to create a disk, the restrictions are as follows:
    • If backend storage is one of OceanStor V3 or OceanStor V5 series and you use an existing disk to create a disk, it is necessary for the administrator to import the license for HyperCopy in advance on the device side.
    • If the selected product has preset disk capacity and disk type, you can choose only a disk whose capacity is smaller than or equal to the preset disk capacity as the source disk, and the disk type of the disk must be the same as the preset disk type.
    • The source disk and the disk to be created must be in the same AZ.
    • When you use an existing disk to create a disk, the disk capacity can be configured but must be greater than or equal to that of the source disk. The disk type cannot be changed, which is the same as that of the source disk. The device type cannot be changed, which is the same as that of the source disk.
    • If you use vAPP to create a disk, no disk can be created from an existing disk.
  • If you use a backup to create a disk, the created disk cannot be used as a system disk.
  • When creating a disk using a snapshot, if the backend storage type is OceanStor V3/V5 series, the administrator needs to import the license of the HyperCopy feature on the device in advance.
  • Snapshots in one AZ cannot be used to create disks in another AZ.

Attaching an EVS disk

  • Only SCSI EVS disks can be attached to BMSs.
  • Whether a shared EVS disk or non-shared EVS disk is attached to an instance, the EVS disk and the instance must be in the same AZ.
  • An EVS disk cannot be attached to an instance that has expired.
  • An EVS disk cannot be attached to an instance that has been soft deleted.
  • An EVS disk cannot be attached to an instance that has been stopped.
  • An EVS disk created using vAPP cannot be attached to an instance.
  • A shared EVS disk can be attached to only one BMS at a time. To attach a shared EVS disk to multiple BMSs, attach it to each BMS.

Creating a snapshot

  • When the backend storage type is OceanStor V3/V5 or Dorado V3, the administrator needs to import the HyperSnap license on the device in advance.
  • Snapshots can be created for only disks in the Available or In-use state.
  • A snapshot name cannot be the same as the prefix of the temporary snapshot created by the backup service, such as Volume Backup Service (VBS) and Cloud Server Backup Service (CSBS), or the disaster recovery service, such as Cloud Server Disaster Recovery (CSDR), Cloud Server High Availability (CSHA), and VHA.
  • Snapshots created using the EVS console consume the capacity quota instead of quantity quota of EVS disks.
  • Snapshots created using the EVS console and temporary snapshots created by the DR&backup service (VBS, CSBS, CSDR, CSHA, or VHA) consume backend storage capacity. If a large number of snapshots are created, contact the administrator to set the thin provisioning ratio of backend storage to a large value, preventing EVS disk provisioning failures caused by excessive snapshots.
  • Temporary snapshots created by the backup service (VBS or CSBS) or the disaster recovery service (CSDR, CSHA, or VHA) do not consume EVS disk quotas.
  • No snapshots can be created for disks that have expired.
  • No snapshots can be created for disks that have been soft deleted.
  • No snapshots can be created for disks created using vAPP.
  • If a task for creating a snapshot fails, the task is automatically deleted.
  • If backend storage of the disk is heterogeneous storage, snapshots can be created.

Rolling back a disk from a snapshot

  • A temporary snapshot created by the backup service (VBS or CSBS) or the disaster recovery service (CSDR, CSHA, or VHA) cannot be used to roll back the EVS disk.
  • Snapshots created for disks having any DR service (CSDR/CSHA/VHA) configured cannot be rolled back.
  • A snapshot can be used to roll back its source EVS disk, and cannot be used to roll back any other EVS disk.
  • When the source disk of a snapshot is in the recycle bin, EVS disk rollback from the snapshot is not supported.
  • If backend storage of the disk is heterogeneous storage, EVS disk rollback from a snapshot is not supported.

Creating a backup

  • Only disks in the Available or In-use state can be backed up.
  • No backups can be created for disks created using vAPP.
  • For more constraints about EVS disk backup, see What Is Volume Backup Service?.
  • If the type of the backend storage which is used to create the disk is heterogeneous storage, backups cannot be created.

Expanding the capacity of an EVS disk

  • When you expand the capacity of a disk online, the instance to which the disk is attached must be in the Running or Stopped state.
  • Shared EVS disks do not support online capacity expansion, that is, the capacity of a shared EVS disk can be expanded only when the disk is in the Available state.
  • The capacity of a disk configured with the disaster recovery service (CSHA, CSDR, or VHA) cannot be expanded.
  • When the backend storage is Huawei SAN storage (OceanStor V3/V5 series, Dorado V3 series) or heterogeneous storage, if the EVS disk has snapshots, capacity expansion is not supported. When the backend storage is FusionStorage, capacity expansion can be performed for an EVS disk with snapshots.
  • The capacity of a disk created using vAPP cannot be expanded.
  • If the backend storage where the disk belongs is heterogeneous, online capacity expansion is not supported and offline capacity expansion is supported.

Changing the disk type

  • The disk type can be changed only when backend storage is one of OceanStor V3 or OceanStor V5 series and the administrator has imported the license for SmartMigration in advance on the device side.
  • When changing the disk type, you must set hw:devsn=sn (sn indicates the device serial number) in the additional information about the disk type. .
  • You can change the type of the EVS disk only in the Available or In-use state.
  • If a disk has snapshots or is configured with the backup service (VBS or CSBS) or the disaster recovery service (CSDR, CSHA, or VHA), the disk type cannot be changed.
  • Migration between different storage pools is supported only within a single set of storage devices.
  • The disk type of a disk created using vAPP cannot be changed.
  • If backend storage of a disk is heterogeneous storage, the disk type cannot be changed.

Extending the validity period of an EVS disk

  • The validity period of the data disk that is created with the instance is unlimited. The validity period of the system disk is the same as that of the instance.
  • If the validity period of an EVS disk is unlimited, the validity period cannot be extended.
  • When the status of an EVS disk is Creating, Error, Reserved, or Maintenance, the disk validity period cannot be extended.
  • The validity period of an EVS disk created using vAPP cannot be extended.
  • If an EVS disk has expired, operations including capacity expansion cannot be performed on it. To continue using this EVS disk, extend its validity period.
  • If an EVS disk has expired, its snapshot cannot be used to roll back the EVS disk or create an EVS disk. To continue using this EVS disk, extend its validity period.
  • When an EVS disk expires, its data will not be deleted. You can continue using this EVS disk after extending its validity period.

Modifying EVS disk information

The disk name and description information cannot be modified for a disk created using the vAPP service.

Detaching an EVS disk

  • Data disks can be detached online, that is, data disks can be detached from BMSs in running state.
  • System disks cannot be detached online.
  • Before detaching a disk from an instance running Windows, log in to the instance to perform the offline operation and confirm that the disk is not being read and written. Otherwise, the disk will fail to be detached.
  • Before detaching a disk from an instance running Linux, log in to the instance, run the umount command to cancel the relationship between the disk and the file system, and confirm that the disk is not being read and written. Otherwise, the disk will fail to be detached.
  • A disk created using vAPP cannot be detached.

Deleting an EVS disk

  • If a disk has been attached to an instance, the disk cannot be deleted.
  • If a disk has been configured with the disaster recovery service (CSDR, CSHA, or VHA), the disk cannot be deleted.
  • If a disk is created using vAPP, the disk cannot be deleted.
  • If an EVS disk has a snapshot, the EVS disk can be soft deleted only when the snapshot is in the Available or Error state.
  • When an EVS disk is permanently deleted, all snapshots of the EVS disk are also deleted.
  • A shared disk to be deleted must have been detached from all instances.

Deleting a snapshot

  • You can delete a temporary snapshot created by the backup service (VBS or CSBS). When you back up the EVS disk whose temporary snapshot is deleted, full backup is performed for the first time.
  • Temporary snapshots created by the disaster recovery service (CSDR, CSHA, or VHA) cannot be deleted.
  • You can delete a snapshot only when its state is Available or Error.
Translation
Download
Updated: 2019-10-23

Document ID: EDOC1100063247

Views: 64778

Downloads: 182

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next