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

OceanStor BCManager 6.5.0 eReplication User Guide 02

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).
Adding FusionSphere Components

Adding FusionSphere Components

If you want to add new FusionSphere VMs to a site for protection, you need to add necessary FusionSphere components, including FusionCompute, FusionManager, and VRGs.

Adding FusionManager

FusionManager monitors and manages cloud computing hardware and software. It provides automatic resource provisioning and automated infrastructure operation and maintenance (O&M). Additionally, it provides a web user interface (UI) for O&M administrators to operate and manage the resources in the system. If protected objects are FusionSphere VMs, eReplication provides data protection for them. Before creating protected groups, add FusionManager.

Prerequisites

  • A site has been created.
  • The FusionManager to be added has not been added to any site.
  • The FusionManager to be added is running properly.
  • The FusionManager to be discovered and storage devices are communicating properly with the eReplication on the same network plane.
  • The SOAP northbound interface of the FusionManager to be discovered has been opened. For details, see FusionSphere VMs (in Non-OpenStack Architecture).
  • The account and password provided by FusionManager to eReplication have been obtained. The default username and password of the account are CIDC-RP-05 and Huawei@CLOUD8!.

Context

  • When adding FusionManager, you must discover FusionCompute associated with FusionManager and FusionCompute must reside at the same site as FusionManager.
  • One piece of FusionManager can be added only to one site on eReplication.
  • In mote DR mode, a remote management server must be added and FusionManager must be added to the remote management server.

Procedure

  1. On the menu bar, select Resources.
  2. In the navigation tree, select the site where FusionManager is to be added.
  3. Choose Add FusionSphere Component > FusionManager.

    • In the Resource Statistics, choose Add FusionSphere Component > FusionManager.

    • In the navigation tree, select FusionSphere and choose Add FusionSphere Component > FusionManager.

  4. Optional: Select Apply the port, username, and password of the first row to the newly added row.. The system will copy the port number, user name, and password of the FusionManager in the first row to the FusionManager row to avoid repeated inputs.
  5. Set parameters for the FusionManager to be added as described in Table 5-24.



    Table 5-24  Parameters for adding FusionManager

    Parameter

    Description

    Value

    IP Address

    IPv4 or IPv6 address of FusionManager.

    [Example]

    192.168.10.11

    Port

    Communication port of FusionManager.

    [Value range]

    1 to 65535

    [Default value]

    8195

    Username

    Northbound interface account of FusionManager.

    It can be obtained from the FusionManager system administrator.

    Password

    Password of FusionManager's northbound interface account.

    It can be obtained from the FusionManager system administrator.

    NOTE:

    If added FusionManager does not need to be discovered, click Delete to delete it. The default information row cannot be deleted.

  6. Click OK.

Follow-up Procedure

After the FusionManager is added, you can refresh, modify, and delete FusionManager information. For details about subsequent operations, see Table 5-25.

Table 5-25  Related operations

Related Operation

Prerequisite and Result

In the row where the FusionManager resides, click More > Modify on the Operation list. In the Modify Device Information dialog box that is displayed, modify the name or authentication information of the FusionManager.

If authentication information of the FusionManager is modified, you need to synchronize the latest information to eReplication in time to ensure successful running of subsequent DR protection services.

In the row where the FusionManager resides, click More > Delete on the Operation list.

If one piece of FusionManager is no longer needed, you can delete it.

In the row where the FusionManager resides, click Refresh on the Operation list.

If FusionManager information is modified, you need to refresh the information on eReplication immediately.

Adding FusionCompute

FusionCompute is cloud operating system software, which virtualizes hardware resources and centrally manages virtual resources, service resources, and user resources. If protected objects are FusionSphere VMs, eReplication provides data protection for them. Before creating protected groups, add FusionCompute.

Prerequisites

  • A site has been created.
  • The FusionCompute to be added has not been added to any site.
  • The FusionCompute to be added is running properly.
  • The FusionCompute to be discovered and storage devices are communicating properly with the eReplication on the same network plane.
  • Before adding FusionCompute, an interconnection user has been created to connect FusionCompute to eReplication.

Context

  • When adding FusionManager, you must discover FusionCompute associated with FusionManager and FusionCompute must reside at the same site as FusionManager.
  • One piece of FusionCompute can be added only to one site on eReplication.
  • In mote DR mode, a remote management server must be added and FusionCompute must be added to the remote management server.
  • When adding FusionCompute, you need to discover the storage device associated with FusionCompute and must add them to the same site.

Procedure

  1. On the menu bar, select Resources.
  2. In the navigation tree, select the site where FusionCompute is to be added.
  3. Choose Add FusionSphere Component > FusionCompute.

    • In the Resource Statistics, choose Add FusionSphere Component > FusionCompute.

    • In the navigation tree, select FusionSphere and choose Add FusionSphere Component > FusionCompute.

  4. Optional: Select Apply the port, username, and password of the first row to the newly added row.. The system will copy the port number, user name, and password of the FusionCompute in the first row to the FusionCompute row to avoid repeated inputs.
  5. Set parameters for the FusionCompute to be added as described in Table 5-26.



    Table 5-26  Parameters for adding FusionCompute

    Parameter

    Description

    Value

    IP Address

    IPv4 or IPv6 address of FusionCompute.

    [Example]

    192.168.10.11

    Port

    Communication port of FusionCompute.

    [Value range]

    1 to 65535

    [Default value]

    7443

    Username

    Username of the interconnection user of FusionCompute and eReplication.

    It can be obtained from the FusionCompute system administrator.

    Password

    Password of the interconnection user of FusionCompute and eReplication.

    It can be obtained from the FusionCompute system administrator.

    NOTE:

    If added FusionCompute does not need to be discovered, click Delete to delete it. The default information row cannot be deleted.

  6. Click OK.

Follow-up Procedure

After the FusionCompute is added, you can refresh, modify, and delete FusionCompute information. For details about subsequent operations, see Table 5-27.

Table 5-27  Related operations

Operation

Prerequisite and Result

In the row where the FusionCompute resides, click More > Modify on the Operation list. In the Modify Device Information dialog box that is displayed, modify the name or authentication information of the FusionCompute.

If authentication information of the FusionCompute is modified, you need to synchronize the latest information to eReplication in time to ensure successful running of subsequent DR protection services.

In the row where the FusionCompute resides, click More > Delete on the Operation list.

If one piece of FusionCompute is no longer needed, you can delete it.

In the row where the FusionCompute resides, click Refresh on the Operation list.

If FusionCompute information is modified, you need to refresh the information in eReplication immediately.

Adding FusionSphere OpenStack

FusionSphere OpenStack is the enterprise edition of OpenStack. Enhanced and hardened by Huawei, the enterprise edition provides unified external RESTful interfaces and centrally schedules and manages computing, storage, and network resources. If protected objects are FusionSphere VMs, eReplication provides data protection for FusionSphere OpenStack. Before creating protected groups, add FusionSphere OpenStack.

Prerequisites

  • A site has been created.
  • The FusionSphere OpenStack to be added has not been added to any site.
  • The FusionSphere OpenStack to be added is running properly.
  • The FusionSphere OpenStack information has been checked.
  • The DNS IP address has been configured on the eReplication server. For details, see Adding a DNS server IP address.
  • The Keystone domain name, name of the domain where the tenant administrator resides, and the account and password of the tenant administrator have been obtained.
  • To select IAM, ensure that the IAM service is connected. For details about how to connect to the IAM service, see Connecting to the IAM Service.

Context

If multiple OpenStack share one Keystone, information about all OpenStack is added after the Keystone is added. Do not add one Keystone to multiple sites.

Procedure

  1. On the menu bar, select Resources.
  2. In the navigation tree, select the site where FusionSphere OpenStack is to be added.
  3. Choose Add FusionSphere Component > OpenStack.

    • In the Resource Statistics, choose Add FusionSphere Component > OpenStack.

    • In the navigation tree, select FusionSphere and choose Add FusionSphere Component > OpenStack.

  4. Set parameters for the FusionSphere OpenStack to be added as described in Table 5-28.



    Table 5-28  Parameters for adding FusionSphere OpenStack

    Parameter

    Description

    Value

    Keystone Domain Name

    • Keystone: The Keystone domain name includes identity, the AZ name, DC name, and domain name suffix. Each level of domain name consists of uppercase and lowercase letters, digits, and hyphens (-), cannot start with a hyphen (-), and contains a maximum of 63 characters. Different levels of domain names are connected by periods (.).
    • IAM: Enter the IP address of IAM as the domain name.

    [Example]

    • Keystone: identity.az1.dc1.domainname.com
    • IAM: iam.az1.dc1.domainname.com

    Type

    Keystone and IAM are components used for system authentication. When authenticating the interconnected system, select the type based on site requirements.

    • Keystone: native component of OpenStack
    • IAM: enhanced component based on the OpenStack community edition.
    • Keystone: used by default when ManageOne 3.x is interconnected.
    • IAM: used by default when ManageOne 6.x is interconnected.

    Version

    Supported versions of OpenStack include:

    • 6.0 (default)
    • 6.1

    -

    Port

    Port number of the Keystone domain or IAM domain.

    [Value range]

    1 to 65535

    [Default value]

    • Keystone: 443
    • IAM: 31943

    Domain

    Name of the domain where the tenant administrator resides. The value of Domain is Default by default. The actual domain name is the one configured during the DR management administrator creation. For details about how to create a DR administrator account.

    [Default value]

    • Keystone: Default
    • IAM: op_service

    Username

    • If the type is Keystone, the user name is the DR administrator who can manage the network, compute, and storage resources of tenants.
    • If the type is IAM, the user name is the internal account's name of the cloud server HA or cloud server DR.
    • To interconnect with Keystone, set Username to scdr_admin.
      NOTE:

      For details about the user name information, see Account Information Overview in the ManageOne ServiceCenter 3.0.9 Product Documentation .

    • When interconnecting with IAM, contact IAM O&M personnel to create internal account csha_service and csdr_service for the cloud server HA orcloud server DR, and set Domain to op_service.

    Password

    • When the type is Keystone, the password is the password of the DR administrator.
    • If the type is IAM, the password is the internal account's password of the cloud server HA or cloud server DR.
    • To interconnect with Keystone, set Password to Huawei@CLOUD8!.
    • When interconnecting with IAM, contact IAM O&M personnel to create internal account csha_service and csdr_service for the cloud server HA orcloud server DR, and set Domain to op_service.
    NOTE:

    To ensure system security, change the password periodically. Otherwise, security risks may exist.

    To check Keystone Domain Name and Port, perform the following steps:
    1. Log in to the page for deploying FusionSphere OpenStack.
    2. In the navigation tree, choose Configure > System.
    3. In the operation area, click Change Domain Name.
    4. In the Change Domain Name dialog box that is displayed, check Keystone.

      The following figure is used as an example, the n Keystone is az1.dc1.domainname.com:443, Keystone Domain Name is identity.az1.dc1.domainname.com and Port is 443.



    NOTE:

    If added FusionSphere OpenStack does not need to be discovered, click Delete to delete it. The default information row cannot be deleted.

Follow-up Procedure

After the FusionSphere OpenStack is added, you can refresh, modify, and delete FusionSphere OpenStack information. For details about subsequent operations, see Table 5-29.

Table 5-29  Related operations

Related Operation

Prerequisite and Result

In the row where the FusionSphere OpenStack resides, click More > Modify on the Operation list. In the Modify Device Information dialog box that is displayed, modify the name or authentication information of the FusionSphere OpenStack.

If authentication information of the FusionSphere OpenStack is modified, you need to synchronize the latest information to FusionSphere OpenStack in time to ensure successful running of subsequent DR protection services.
NOTICE:
  • If the shared Keystone domain name of the OpenStack is changed to the shared Keystone domain name of other OpenStack, eReplication will add the modified OpenStack to overwrite the current OpenStack information. As a result, the existing protected groups and DR services become unavailable.
  • If the Keystone of OpenStack switches, you need to modify the Keystone connection information in eReplication.

In the row where the FusionSphere OpenStack resides, click More > Delete on the Operation list.

If one piece of FusionSphere OpenStack is no longer needed, you can delete it.

In the row where the FusionSphere OpenStack resides, click Refresh on the Operation list.

If FusionSphere OpenStack information is modified, you need to refresh the information in FusionSphere OpenStack immediately.

Adding Mapping Information About FusionSphere OpenStack

FusionSphere The OpenStack mapping information is preset for AZ Mapping and Volume Type Mapping to facilitate your follow-up operations.

Prerequisites

  • A site has been created.
  • FusionSphere OpenStack has been added to the site.
  • FusionSphere OpenStack to be added is running properly.
  • Information about FusionSphere OpenStack has been checked.
  • The Keystone domain name, name of the domain where the DR administrator resides, and the account and password of the DR administrator have been obtained.
  • DR associations and volume type mappings planned in the site LLD have been obtained.

Procedure

  1. On the menu bar, select Resources.
  2. In the navigation tree, select the site where FusionSphere OpenStack has been added.
  3. In the navigation tree, select FusionSphere.



  4. Set parameters for AZ Mapping.
    1. Click the Add drop-down list.



    2. If HyperMetro is selected, set Region ID, Region Name, Availability Zone ID and Availability Zone Name.



      NOTE:
      The name must start with an underscore (_) or a letter and contain only underscores (_), letters, digits, and decimal points (.).

    3. If Cloud active/standby is selected, set Region ID, Region Name, Availability Zone ID, and Availability Zone Name.



      NOTE:
      The name must start with an underscore (_) or a letter and contain only underscores (_), letters, digits, and decimal points (.).

    NOTE:
    • If you want to add another AZ mapping, repeat these operations.
    • If an AZ mapping is no longer needed, click Delete to delete it.

  5. Set parameters for Volume Type Mapping.

    Type includes HyperMetro, Cloud active/standby, and Volume HA. Select a type based on the actual scenario.



Adding Information of Regions

If a region where OpenStack with DR relationship resides is specified, only OpenStack resources in this region will be added. If no region is specified, OpenStack resources of all regions will be added.

Prerequisites

  • A site has been created.
  • FusionSphere OpenStack has been added to the site.
  • FusionSphere OpenStack to be added is running properly.
  • Information about FusionSphere OpenStack has been check.

Procedure

  1. On the menu bar, select Resources.
  2. In the navigation tree, select the site where FusionSphere OpenStack has been added.
  3. In the navigation tree, select FusionSphere.



  4. Add information of regions.
    1. Click the Region tab.
    2. Click Add Region in the upper left corner.
    3. Enter Region ID in the Add Region dialog box that is displayed. .



      To view the information of regions, perform the following steps:
      1. Log in to the page for deploying FusionSphere OpenStack.
      2. In the navigation tree, choose Configure > Resource Pool.
      3. In the right OpenStack area, you can view the region name.


    4. In the Add Region dialog box, enter the registration information about Endpoint.

      In the dialog box, seven fields Compute, Volume, Network, DRExtend, Compute-ext, Metering, and Image in Endpoint correspond to seven services Nova, Neutron, Cinder, DrExtend, Nova-Ext, Ceilometer, and Glance.You need to enter the endpoint URLs of seven services to complete the registration. After the registration is complete, OpenStack Client can be used to invoke the corresponding interfaces.

      NOTE:
      The endpoint URL varies with the registered service. URL can be obtained by running openstack endpoint list on the OpenStack node.

Follow-up Procedure

After information of regions is added, you can modify and delete regions, and configure CSHA DR for regions. For details about subsequent operations, see Table 5-30.

Table 5-30  Related operations

Related Operations

Prerequisites or Results

Select the row where the region resides, and click Modify in the Operation area.In the Modify dialog box that is displayed, modify the endpoint registration information.

If information of the region is changed, you need to synchronize the latest information to FusionSphere OpenStack in time to ensure successful running of subsequent DR protection services.

Select the row where FusionSphere OpenStack resides.click More > Delete on the Operation list.

Delete the region if no longer needed.

Select the row where FusionSphere OpenStack resides, and choose More > CSHA DR Configuration in the Operation area .

After Network Adapter Switchover is enabled, the system can perform a planned migration or fault recovery on CSHA to switch network adapters of production VMs to placeholder VMs. You can enable or disable Network Adapter Switchover as required.
NOTE:
Before disabling Network Adapter Switchover, log in to the ECS console and ensure that network adapters are mounted on the corresponding placeholder VMs.

Adding a VRG

If protected objects are FusionSphere VMs and host-based replication is used for DR, you need to add a VRG to the site.

Prerequisites

  • A site has been created.
  • The VRG to be added is running properly and is not added to any other site.
  • The VRG to be added and eReplication are on the same network plan and are communicating properly.
  • eReplication supports VRG alarm reporting. The SNMP service has been enabled for VRGs before the alarm reporting parameter configuration. SNMP v3 with higher security is used by default and a user name and password have been set for the VRG before the use of SNMP v3.

Context

One VRG can be added only to one site on eReplication.

Procedure

  1. On the menu bar, select Resources.
  2. In the navigation tree, select the site where the VRG is to be added.
  3. Choose Add FusionSphere Component > VRG.

    • In the Resource Statistics area, choose Add FusionSphere Component > VRG.

    • In the navigation tree, select FusionSphere, and choose Add FusionSphere Component > VRG.

  4. Optional: Select Apply the port, username, and password of the first row to the newly added row.. The system will copy the port number, user name, and password of the FusionSphere in the first row to the new row to avoid repeated inputs.
  5. Set the VRG parameters as described in Table 5-31.



    Table 5-31  Parameters for adding a VRG

    Parameter

    Description

    Value

    IP Address

    IPv4 or IPv6 address of the VRG's first network adapter

    [Example]

    192.168.10.11

    Port

    VRG communication port

    [Value range]

    1 to 65535

    [Default value]

    8080

    Username

    Username: admin

    -

    Password

    Password of user admin

    It can be obtained from an administrator.

    NOTE:

    If an added VRG does not need to be detected, click Delete. The default information row cannot be deleted.

  6. Optional: If the VRG alarms are required to be monitored by eReplication, click in the operation button area where the VRG information row resides, and set the reporting parameters as described in Table 5-32.



    Table 5-32  Parameters for alarm reporting

    Parameter

    Description

    Value

    Type

    Type of the SNMP protocol.

    The default version is SNMP v3. This parameter cannot be changed.

    The system uses SNMP v3 for communication by default.

    Retry Count

    Times for resending the SNMP operations. If this number of times is exceeded, the SNMP operation will be abandoned.

    [Value range]

    0 to 5

    [Default value]

    3

    Timeout Duration

    Time that needs to be waited after the protocol message is sent.

    [Value range]

    0 to 5

    [Default value]

    5

    Port

    Port used by eReplication to receive VRG alarms.

    [Value range]

    1 to 65535

    [Default value]

    161

    Username

    Username: admin

    admin

    Environment Name

    This parameter does not need to be configured.

    -

    Environment Engine ID

    This parameter does not need to be configured.

    -

    Authentication Protocol

    Protocol used for verifying messages.

    NOTE:
    They system uses HMAC_SHA 1 by default. This parameter cannot be modified.

    Authentication Password

    If the authentication protocol is used to verify messages, you need to set the authentication password.

    It must be the same as the authentication password set during the VRG configuration.

    Data Encryption Protocol

    Encryption protocol used for encapsulating data.

    NOTE:
    They system uses AES by default. This parameter cannot be modified.

    Data Encryption Password

    If the encryption algorithm is used for encapsulating data, you need to set the data encryption password.

    It must be the same as the data encryption password set during the VRG configuration.

  7. Click OK.

Follow-up Procedure

After the VRG is added, you can refresh, modify, and delete VRG information. For details about subsequent operations, see Table 5-33.

Table 5-33  Related operations

Related Operations

Prerequisite and Result

Select the host or host group that you want to modify and click More > Modify on the Operation list.In the Modify Device Information dialog box that is displayed, change the name, authentication information, or alarm reporting parameters of the VRG.

If you change the authentication or alarm reporting information about the VRG, synchronize the latest information to eReplication in time to ensure successful running of subsequent DR protection services.

In the row where the VRG resides, click More > Delete on the Operation list.

Perform this operation when a VRG is no longer needed.

In the row where the VRG resides, click Refresh on the Operation list..

If the VRG information is changed, update the changes to eReplication.

Create a Resource Mapping

When the protected objects are FusionSphere VMs, map virtualization resources from the protected site to the DR site so that the VM can be recovered at the DR site based on the target attributes specified during resource mapping.

Prerequisites

  • A site has been created.
  • Resources, applicable to resource various DR technologies and FusionSphere components, are available for mapping creation.

Context

Resource mappings vary with DR technologies and FusionSphere components, as shown in Table 5-34.

Table 5-34  Description of resource mappings for different DR technologies

DR Technology

FusionSphere Component

Description

Host replication

FusionCompute

Create resource mappings for clusters or hosts, port groups, datastores, and VRGs.

FusionManager

Create resource mappings for clusters, networks, security groups, and VRGs. Resource mappings for security groups are optional. If the VMs that require DR have been added into a security group, you must create resource mappings for the security group.

Non-host-based replication

FusionCompute

Create resource mappings for port groups, and clusters or hosts.

FusionManager

Create resource mappings for clusters, networks, security groups, and VRGs. Resource mappings for security groups are optional. If the VMs that require DR have been added into a security group, you must create resource mappings for the security group.

A resource at the production or DR site can be mapped only to one resource of the same type.

Procedure

  1. On the menu bar, select Resources.
  2. In the navigation tree, select the site where resource mappings are to be created, and click FusionSphere.
  3. Select the FusionCompute and FusionManager VMs that need to be mapped to resources.
  4. Select the type of the resource mappings and click Add.

    The wizard for creating resource mappings is displayed.

  5. Select FusionCompute and FusionManager corresponding to the production and DR sites respectively.

    If FusionManager is selected, select the production VPC and DR VPC.

  6. Click Next.

    The page for configuring mapping views is displayed.

  7. Select the resource object to be mapped, and select resources from the production and DR sites respectively.
  8. Select a resource and click Add.

    In Mapping area, the mapping is displayed.

    You can go to add other resources and batch create resource mappings for VMs.

    NOTE:

    If you want to perform Test from the production site to same-city DR site or remote DR site, add the mapping between the production site and same-city DR site or between the production site and remote DR site to the Cluster Mapping area.

  9. Click OK.
  10. Perform 5 to 9 repeatedly, select FusionCompute related to FusionCompute, and select other resources to create resource mappings for VMs.
  11. Perform 3 to 10 repeatedly to create resource mappings one by one.

Configuring VRG Pairs

Before adding protected VMs using host-based replication DR technology, VRGs need to be paired for communication, providing a channel for using host-based replication to synchronize disk data.

Prerequisites

At the production center, FusionSphere components on the DR management server and storage devices are running properly and can communicate normally.

Context

In remote DR mode, two eReplication Servers are deployed and VRG pairing can be performed on the DR management server at either the production or the DR center.

Procedure

  1. On the menu bar, select Resources.
  2. In the navigation tree, select the site where VRG pairs are to be configured and click FusionSphere.
  3. Select VRG VMs that need to be paired.
  4. In the details area, click the Summary tab. On the tab page that is displayed, click VRG Pairing.
  5. Click OK.

Adding VMs

After VRGs are paired, you need to add VMs to be protected to VRG pairs.

Prerequisites

  • eReplication has VRGs that are successfully paired.
  • At the production center, FusionSphere components on the DR management server and storage devices are running properly and can communicate normally.
  • If the storage device is FusionStorage, log in to the FusionCompute page and select the VM to be protected. The VM is in the Stopped state. Choose Options > Basic Block Storage Settings, and check whether Basic Block Storage is set to Yes. If no, set it to Yes.

Context

In remote DR mode, two eReplication Servers are deployed. You need to add VMs to the DR management servers at the production and DR centers.

Procedure

  1. On the menu bar, select Resources.
  2. In the navigation tree, select the site to which VMs are to be added and select FusionSphere.
  3. Select the VRG for which you want to add VMs.
  4. In the details area, click the Associated VM tab. On the tab page that is displayed, click Add.
  5. Move the VMs that need to be protected from Available VMs to Selected VMs.
  6. Click OK.
Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 12186

Downloads: 64

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