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 Troubleshooting 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).
Appendix

Appendix

Adding eBackup Servers to a FusionStorage Cluster

If the planned production storage of eBackup backup management system is FusionStorage, after installing eBackup, you need to add backup server and backup proxies into the FusionStorage cluster. Otherwise, backup and restore services cannot be performed on eBackup servers. A set of backup server and backup proxies can only be added to a FusionStorage cluster.

Prerequisites

You have obtained FusionStorage block Api package FusionStorage Block V100R006C20SPC200_api.zip. and tool package FusionStorage Block V100R006C20SPC200_tool.zip. The name of the installation package varies with site conditions. You can obtain the installation packages as follows:

FusionStorage Block V100R006C20SPC200_api.zip:

FusionStorage Block V100R006C20SPC200_tool.zip:

  • For enterprise users: Click here
  • For carrier users: Click here
    NOTE:

    When downloading a software package, obtain the .asc signature file and use the digital signature public key and validation tool provided by the Huawei support website to validate the software package integrity.

    1. Click the download button to download the digital signature file (.asc) that has the same name as the software package. Specifically:
      • For enterprise users:
      • For carrier users:
    2. The public key file, verification tool and its usage can be obtained as follows:
Procedure

Changing the name of an NIC

  1. Log in to the FusionSphere OpenStack web client. (In Region Type I scenario, log in to the cascading layer FusionSphere OpenStack web client.)

    The default user name and password are admin and cnp200@HW respectively.

  2. Choose Configuration > Resource Pool , In the Resource Pool area, click .

  3. In the Storage Cluster area, click .

  4. On the Configure Parameter page, Floating IP Address in General Configuration is the floating IP address of FusionStorage Manager.
  5. Use PuTTY to log in to FusionStorage Manager.

    The login address is the floating IP address of FusionStorage Manager, which is obtained in 4.

    The default user name and password are Dsware and IaaS@OS-CLOUD9! respectively.

  6. Run the following command to prevent user logout due to session timeout:

    TMOUT=0

  7. Run the following command to go to the bin directory:

    cd /opt/dsware/client/bin

  1. Run the following command to query the information of an NIC.

    sh dswareTool.sh --op querySysPara -n sys_network_mark

    Enter user name cmdadmin and default password IaaS@PORTAL-CLOUD9! as prompted.

    [dsware@FSM01 bin]$ sh dswareTool.sh --op querySysPara -n sys_network_mark
    [Tue Apr 17 17:14:35 CST 2018] DswareTool operation start.
    Enter User Name:cmdadmin
    Enter Password :
    Operation finish successfully. Result Code:
    parameterName                       parameterValue             type   
     --------------------------------------------------------------------------------------
    sys_network_mark                    storage_data0                1       
    [Tue Apr 17 17:14:54 CST 2018] DswareTool operation end.

  2. The parameterValue parameter in the command output displays only the network port name. The NIC on the production storage plane of an eBackup server is bonded. Therefore, you need to modify the configuration of FusionStorage Manager, and add the NIC name of the production storage plane of eBackup servers (backup server and backup proxy) to FusionStorage. For details, Add the Network Adapter Name of the Production Storage Plane of an eBackup Node to a FusionStorage Cluster.

Configuration at the FusionStorage side

  1. Install FusionStorage Agent on an eBackup server(backup server and backup proxy).

    For details, see Block Storage Service > Installation > Block Storage Service Software Installation Guide > Installation Process (FusionSphere OpenStack) > Deploying FSA > Separated Deployment > Installing FSA Nodes in FusionStorage V100R006C20 Product Documentation.

    When installing FSA components, pay attention to the following parameters:
    • Management IP address of the server is the management plane IP address of the backup server and backup proxy.
    • User hcp is used for server login, and its default password is PXU9@ctuNov17!.
    • The default password of user root is Cloud12#$.

  2. Create a block client for the eBackup server(backup server and backup proxy).

    For details, see Block Storage Service > Configuration > Block Storage Service Administrator Guide > Resource Management > Block Storage Client Management > Creating a Block Storage Client in FusionStorage V100R006C20 Product Documentation.

    When creating a block client, pay attention to the following parameters:
    • Set nodetype to 1.
    • ip indicates the management plane IP address of an eBackup server.

      For details about how to obtain ip.

    • When creating a block client, ensure that the eBackup storage plane can communicate with the FusionStorage cluster storage plane.

      FSA configures the storage network according to the network port names. Therefore, the production storage plane of eBackup must be able to communicate with the storage network where the host of the FusionStorage Block cluster resides. The names of ports where the production storage plane of eBackup resides must be the same as those of the FSA storage network ports.

Copying the FusionStorage API file to the backup server

  1. On the maintenance terminal, decompress FusionStorage Block V100R006C20SPC200_api.zip. The following files are generated.

    • dsware-api-V100R006C20SPC200.jar
    • dsware-api.properties
    • client_self.keystore
    • client_trust.keystore

  2. Use WinSCP to log in to the backup server and backup proxy nodes using their management plane IP addresses.
  3. Copy the files obtained in 12 to the target directories of the backup server and a backup proxy, as shown in Table 17-4.

    When performing backup and restore jobs, the eBackup server needs to invoke APIs of FusionStorage.
    NOTE:

    The permission on copied files must be consistent with that on target paths (you can run the ll command in the upper-level directory of the files or target paths to view the permission). Otherwise, backup data may become invalid.

    Table 17-4 Copying files to a target path

    File to be Copied

    Target Path

    dsware-api-V100R006C20SPC200.jar

    /opt/huawei-data-protection/ebackup/vbstool/lib

    dsware-api.properties

    /opt/huawei-data-protection/ebackup/vbstool/conf

    client_self.keystore

    client_trust.keystore

Add the Network Adapter Name of the Production Storage Plane of an eBackup Node to a FusionStorage Cluster

This section describes how to add the network adapter name of the production storage plane of an eBackup node to a FusionStorage cluster, taking name bond1 as an example.

Context
  • If the HA function has been configured on FusionStorage Manager, perform the following steps on the standby node of FusionStorage Manager and then on the active node of FusionStorage Manager.
  • FusionStorage V100R006C20 is used as an example. If the version that matches a site is FusionStorage V100R006C20 or others, obtain the corresponding FusionStorage installation packages and product documents.
Procedure
  1. Log in to the FusionSphere OpenStack web client. (In the Region Type I scenario, log in to the FusionSphere OpenStack web client at the cascading layer.)

    The default user name and password are admin and cnp200@HW respectively.

  1. Choose Cloud Service > FusionStorage. The IP addresses under the External OM IP Address column are the IP addresses of the active and standby nodes of FusionStorage Manager.
  2. Use PuTTY to log in to the active and standby nodes of FusionStorage Manager one by one.

    The login address is the management IP addresses of the active and standby nodes of FusionStorage Manager are the IP addresses obtained in 2.

    The default user name and password are Dsware and IaaS@OS-CLOUD9! respectively.

  3. Run thefollowingcommand and enter the password of user root to switch to user root:

    su root

  4. Run the following command to prevent user logout due to session timeout:

    TMOUT=0

    NOTE:

    After you run this command, the system continues to run when no operation is performed, resulting in a risk. For security purposes, run exit to exit the system after completing required operations.

  5. Run the following command to go to the /opt/dsware/manager/webapps/dsware/WEB-INF directory:

    cd /opt/dsware/manager/webapps/dsware/WEB-INF

  6. Run the following command to back up the SystemConfiguration.xml file:

    cp SystemConfiguration.xml SystemConfiguration.xml.bak

  7. Run the following command to edit the configuration file:

    vi SystemConfiguration.xml

  8. Press i to enter the editing mode.
  9. Modify the following configuration items:

    Change <sys_network_mark desc="storage network plane in UVP" type="initial" >eth3, storage_data1</sys_network_mark> to <sys_network_mark desc="storage network plane in UVP" type="initial" >eth3, storage_data1,bond1</sys_network_mark>.

    bond1 is the NIC name of the eBackup production storage plane. In this section, bond0 is the NIC name of the eBackup management plane, bond1 is the NIC name of the eBackup production storage plane, and bond2 is the NIC name of the eBackup backup storage plane.

    Change <sys_enable_network_type desc="enable not bonding port" type="initial" >1,2</sys_enable_network_type> to <sys_enable_network_type desc="enable not bonding port" type="initial" >0,1,2</sys_enable_network_type>.

  10. Press Esc to exit the editing mode, and input :wq and press Enter to save the settings and exit the vi editor.
  11. Run the following command to restart the service:

    su - omm -c restart_tomcat

Translation
Download
Updated: 2019-06-10

Document ID: EDOC1100063248

Views: 23045

Downloads: 37

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