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.0 Solution Description 05

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 7-8.

In VRM scenarios, if data storage of the VIMS type is used, the storage supports only some functions of the EVS, as listed in Table 7-9.

Table 7-8 Restrictions on EVS

Item

Restriction

Backend storage

  • Supported Huawei storage device types and versions include enterprise storage OceanStor V300R006C10 or V300R006C20, OceanStor V500R007C00 or V500R007C10, Dorado V300R001C21 or V300R001C30, and distributed storage FusionStorage V100R006C20.
  • The following version of heterogeneous storage devices is supported: HP3PAR 8400.
  • Dorado V3 supports Kernel-based Virtual Machine (KVM), but does not support Virtualization Resource Management (VRM) or Bare Metal Server (BMS).
  • Heterogeneous storage access supports KVM virtualization and BMS, but does not support VRM virtualization.
  • An AZ supports only a storage type.
  • Only one FusionStorage system can be deployed in the same AZ. The deployment of multiple FusionStorage systems in the same AZ is not supported.
  • FC SAN and IP SAN protocols cannot be used in the same AZ at the same time.
  • It is recommended that a disk type contain only backend storage of the same storage type, ensuring that the backend storage capabilities are the same.

Creating an EVS disk

  • Shared disks can be used as data disks and cannot be used as system disks.
  • If the backend storage device is a heterogeneous device, only blank disks can be created, and the device type SCSI or shared disk is not supported.
  • 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.
    • In VRM scenarios, when you use an existing disk to create a disk, the disk capacity cannot be configured and must be the same as that of the source disk. You cannot select an attached EVS 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.
    • In KVM scenarios, 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.
    • In VMware scenarios, 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. You cannot select an attached EVS 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 the disk capacity and disk type have been preset for the selected product, you can choose only a disk whose capacity is less than or equal to the preset disk capacity of 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.
    • New disks cannot be created when the source disk is in Reserved or Maintenance state.
    • 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

  • The ECS supports the attaching of disks in VBD mode and SCSI mode.
  • 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.
  • Data disks can only be attached to ECSs as data disks. System disks can be attached to ECSs as system disks or data disks.
  • 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.
  • When a disk is attached to an ECS configured with the disaster recovery service (CSDR, CSHA, or VHA), you must ensure that the disk is created using the same backend storage as the existing disk on the ECS.
  • An EVS disk created using vAPP cannot be attached to an instance.

Creating a snapshot

  • If backend storage is one of OceanStor V3, OceanStor V5, or Dorado V3 series, it is necessary for the administrator to import the license for HyperSnap in advance on the device side.
  • Snapshots can be created only for disks in the Available or In-use state.
  • A snapshot name cannot be the same as that of the prefix of the temporary snapshot created by the backup service (VBS or CSBS) or the disaster recovery service (CSDR, CSHA, or VHA).
  • Snapshots created using the EVS console consume the capacity quota instead of quantity quota of EVS disks.
  • 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. Snapshots created using the VM snapshot function do not consume EVS disk quotas.
  • Snapshots created using the EVS console, temporary snapshots created by DR&backup services, and snapshots created using the VM snapshot function 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.
  • If backend storage of the disk is heterogeneous storage, snapshots cannot be created.
  • No snapshots can be created for disks that have expired.
  • No snapshots can be created for disks that have been soft deleted.
  • Snapshots cannot be created when the disk status is Reserved or Maintenance.
  • No snapshots can be created for disks created using vAPP.

Rolling back a disk from a snapshot

  • Temporary snapshots created by the backup service (VBS or CSBS) or the disaster recovery service (CSDR, CSHA, or VHA) cannot be rolled back.
  • Snapshots created for disks having any DR service (CSDR/CSHA/VHA) configured cannot be rolled back.
  • You can only roll back the snapshot to its source EVS disk. A rollback to another EVS disk is not supported.
  • A rollback can be performed only when the snapshot status is Available and the status of the snapshot source disk is Available (that is, the snapshot is not attached to any instance) or Rollback failed.

Creating a backup

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

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.
  • If backend storage of the disk is heterogeneous storage, the capacity of the disk cannot be expanded.
  • The capacity of a disk created using vAPP cannot be expanded.
  • Capacity expansion cannot be performed when the disk status is Reserved or Maintenance.

Changing the disk type

  • The disk type can be changed only to OceanStor V3 or OceanStor V5 series, and the administrator needs to import the SmartMigration license on the device side in advance.
  • 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.
  • If backend storage of a disk is heterogeneous storage, the disk type cannot be changed.
  • Data can be migrated among different storage pools only in a single storage device.
  • The disk type of a disk created using vAPP 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

  • If you need to detach an EVS disk from an ECS of the KVM virtualization type, the ECS must be in Stopped state.
  • Shared disks can be detached from ECSs of the non-KVM virtualization type online (when the ECSs are running). Non-shared disks cannot be detached from ECSs of the non-KVM virtualization type online.
  • 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 UVP VMTools has been installed on the ECS and is running properly. At the same time, ensure that this 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 snapshots, 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.
  • A shared disk to be deleted must have been detached from all instances.
  • In the Type II and Type III scenarios, a local disk can be selected as the system disk or a data disk for an ECS. When a local disk is used as the system disk or a data disk, its life cycle starts and ends with the ECS, and cannot be manually detached or deleted.

Deleting a snapshot

  • Users are allowed to delete a temporary snapshot created by the backup service (VBS or CSBS). After the snapshot is deleted, if users want to back up the EVS disk corresponding to the snapshot, 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.
Table 7-9 Data storage functions of the VIMS type in VRM scenarios

Function

Sub-function

Supported or Not

Creating an EVS disk

Creating a blank EVS disk

Yes

Creating an EVS disk using a snapshot

Yes

Creating an EVS disk using the backup

No

Creating an EVS disk using an existing disk

Yes

Specifying the shared EVS disk

Yes

Specifying the EVS disk of the SCSI type

No

Specifying the AZ, capacity, name, disk type, and quantity

Yes

Specifying the validity period

Yes

Managing an EVS disk

Querying the EVS disk list and details

Yes

Changing the disk type

No

Changing the name and description of an EVS disk

Yes

Moving the EVS disk to the recycle bin and deleting it from the recycle bin

Yes

Attaching and uninstalling EVS disks

Yes

Extending the validity period of an EVS disk

Yes

Expanding the capacity of an EVS disk

Expanding the disk capacity online

No

Expanding the disk capacity offline

Yes

Snapshot

Creating a snapshot

Yes

Restoring the EVS disk from a snapshot

No

Deleting a snapshot

Yes

Backup

Creating a backup

No

Quota

Specifying the capacity and number of EVS disks

Yes

Specifying the EVS disks metering

Performing metering by capacity, disk type, or duration

Yes

Snapshot metering

Performing metering by capacity or duration

Yes

Translation
Download
Updated: 2019-04-23

Document ID: EDOC1100026685

Views: 173911

Downloads: 277

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next