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

eSight V300R010C00 Maintenance Guide 07

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).
Managing Replication Volumes

Managing Replication Volumes

This topic describes how to manage replication volumes using the Cluster Explorer and commands.

Importing a Disk Group

This topic describes how to import a disk group. You can import a disk group by using the commands.

Prerequisites

The VxVM process must be started.

NOTE:

To check whether VxVM process has been started, run the ps -ef | grep vx command.

Context

Generally, the disk group has been imported when the VxVM starts and this operation is not required in this case. Perform this operation when the disk group fails to be automatically imported.

Procedure

In the SUSE Linux OS:

vxdg import <diskgroupname>

vxrecover -g <diskgroupname> -sb

Command example:

vxdg import datadg

vxrecover -g datadg -sb

Recovering a Disk Volume

This operation enables you to recover a disk volume using the commands.

Context

Run the vxprint -v command to check the status of a disk volume.

Check if STATE is ACTIVE and KSTATE is ENABLED. If not, it indicates that the disk volume is abnormal. Perform the following operations to restore the disk volume.

Procedure

Run the following commands to recover and start the disk volume.

vxrecover -g <diskgroupname> -sb

vxvol -g <diskgroupname> start <volumename>

Example

vxrecover -g datadg -sb

vxvol -g datadg start lv_nms_data

NOTE:

You can run the vxdg list command to query the <diskgroupname>, and run the vxprint -v command to query the <volumename>.

Recovering the RVG

This operation enables you to recover the RVG using commands.

Context

Run the vxprint -Vl command to check the RVG status.

Check if state is ACTIVE and kernel is ENABLED. If not, it indicates that the RVG is abnormal. Perform the following operations to restore the RVG.

Procedure

Run the following commands to recover and start the RVG.

vxrvg -g <diskgroupname> recover <rvgname>

vxrvg -g <diskgroupname> start <rvgname>

Command example:

vxrvg -g datadg recover datarvg

vxrvg -g datadg start datarvg

NOTE:

You can run the vxdg list command to query the <diskgroupname>, and run the vradmin printrvg command to query the <rvgname>.

Recovering the RLink

This operation enables you to recover the RLink using commands.

Context

Run the vxprint -Pl command to check the RLink Status.

Check if state is ACTIVE. If not, it indicates that the RLink is abnormal. Perform the following operations to restore the RLink.

Procedure

Run the following commands to recover the RLink.

vxrlink -g <diskgroupname>

recover <rlinkname>

Command example:

vxrlink -g datadg recover datarlk

Re-synchronizing the Data on Primary and Secondary Servers

This topic describes how to recover and reestablish the replication relationship and how to synchronize the latest data on a server to the other by using commands, if the replication relationship between the primary and secondary servers is abnormal.

Procedure
  1. Check that the replication relationship between the primary and secondary servers is normal.

    Run the following command to check the replication relationship between the primary and secondary servers:
    vradmin -g <diskgroupname> -l repstatus <rvgname>
    Command example:
    vradmin -g datadg -l repstatus datarvg
    Check the following items:
    • Whether Data status is consistent, up-to-date
    • Whether Replication status is replicating (connected)

    If not, it indicates that the replication relationship is abnormal. run the following command to recover the replication relationship between the primary and secondary servers:

    In the SUSE Linux OS:
    vxrlink -g <diskgroupname> att <rlinkname>
    Command example:
    vxrlink -g datadg att datarlk
    NOTE:

    This command needs to be run on both the active server and the standby server.

  2. Run the following command to synchronize the latest data on a server to the other:

    vxrvg -g <diskgroupname> resync <rvgname>

    Command example:

    vxrvg -g datadg resync datarvg

    NOTE:

    This command needs to be run on both the active server and the standby server.

Checking the Status of Data Replication Between the Primary and Secondary Servers in the Veritas HA System

This topic describes how to check the status of data replication between the primary and secondary servers in the Veritas HA system.

Procedure
  1. Log in to the OS as the root user.
  2. Run the following commands on the primary and secondary servers:

    # df -h

    The following information is displayed:
    Filesystem    kbytes  used  avail  capacity Mounted on 
    /dev/sda1              50G  5.9G 41G  13% / 
    devtmpfs              7.8G  168K  7.8G 1% /dev 
    tmpfs                 8.0G  3.8G  4.3G  47% /dev/shm 
    /dev/sda4              10G  8.0K 10G 1% /boot/efi 
    /dev/sda3             197G 14G  174G 8% /opt 
    tmpfs                 4.0K     0  4.0K 0% /dev/vx 
    /dev/vx/dsk/datadg/lvfiledata 
                          9.9G  152M  9.2G 2% /opt/iEMPSync 
    /dev/vx/dsk/datadg/lvdbdata 
                          443G  5.9G  415G 2% /opt/iEMPData     

  3. Run the following commands on the primary and secondary servers:

    # vxdisk list

    In the case of two hard disks, the terminal displays the following information:
    DEVICE       TYPE            DISK         GROUP        STATUS 
    sda     auto:none       -            -            online 
    sdb     auto:sliced     disk02       datadg       online 
    sdc     auto:sliced     disk03       datadg       online     
    NOTE:

    The equipment names in the DEVICE column may be different from those displayed on the terminal according to the actual situation of the workstation.

  4. Run the following commands on both the primary and secondary servers:

    # vxdg list

    The screen output is similar to the following:
    NAME STATE      ID 
    datadg enabled 1338278125.7.PriMaster
    If the following standards are met, the disk group status is normal:
    • If over two disks are available on the workstation, two disk groups should be displayed, including rootdg and datadg. Otherwise, there is a problem with the disk groups.
    • If only two disks are available on the workstation, only one disk group, that is, datadg, should be displayed. Otherwise, there is a problem with the disk group.
    • The STATE of each disk group should be enabled. Otherwise, there is a problem with the disk groups.

  5. Run the following commands to check whether the disk volume status is normal, according to the disk volume information:

    # vxprint -v

    The screen output is similar to the following:
    Disk group: datadg 
     
    TY NAME         ASSOC        KSTATE LENGTH PLOFFS STATE    TUTIL0  PUTIL0 
    v  lvdbdata       datarvg      ENABLED  943718400 -       ACTIVE -       - 
    v  lvfiledata datarvg      ENABLED  20971520 -        ACTIVE -       - 
    v  srl          datarvg      ENABLED  20971520 SRL      ACTIVE -       -
    NOTE:
    The displayed information varies with the data of the disks that are actually configured.
    • If over two disks are configured, the two disk groups including rootdg and datadg are available.
    • If only two disks are configured, only one disk group (datadg) is available.
    If the following standards are met, it indicates that the disk volume status is normal:
    • Disk volumes used by the eSight exist. Currently, disk volumes used by the eSight is lvdbdata and lvfiledata.
    • For all the disk volumes, KSTATE must be ENABLED.
    • For all the disk volumes, STATE must be ACTIVE.

  6. Run the following command to view the mounting status of the eSight file system and the oracle file system.

    # df -k

    The screen output is similar to the following:
    Filesystem           1K-blocks      Used Available Use% Mounted on 
    /dev/sda1             51597400 6091172  42885228  13% / 
    devtmpfs               8162632       168 8162464 1% /dev 
    tmpfs                  8388608 3927036 4461572  47% /dev/shm 
    /dev/sda4             10464144         8  10464136 1% /boot/efi 
    /dev/sda3            206422068  13979504 181956940 8% /opt 
    tmpfs                        4         0         4 0% /dev/vx 
    /dev/vx/dsk/datadg/lvfiledata 
                          10321208    155220 9641700 2% /opt/iEMPSync 
    /dev/vx/dsk/datadg/lvdbdata 
                         464455440 6118804 434743676 2% /opt/iEMPData

    If the preceding file system information is displayed, the eSight file system and Oracle file system are mounted correctly.

  7. Run the following commands to check the status of data replication between the primary and secondary servers on the primary server:

    # vradmin -g datadg repstatus datarvg

    The following information is displayed:
    Replicated Data Set: datarvg 
    Primary: 
      Host name:                  192.88.190.2 
      RVG name:                   datarvg 
      DG name:                    datadg 
      RVG state:                  enabled for I/O 
      Data volumes:               2 
      VSets:                      0 
      SRL name:                   srl 
      SRL size:                   10.00 G 
      Total secondaries:          1 
     
    Secondary: 
      Host name:                  192.88.190.3 
      RVG name:                   datarvg 
      DG name:                    datadg 
      Data status:                consistent, up-to-date 
      Replication status:         replicating (connected) 
      Current mode:               asynchronous 
      Logging to:                 SRL 
      Timestamp Information:      behind by 0h 0m 0s

  8. Run the following command to check the process of data replication between the primary and secondary servers on the primary server:

    # vxrlink -g datadg -i 5 status datarlk

    The following information is displayed:
    ...... 
    VxVM VVR vxrlink INFO V-5-1-4467 Rlink datarlk is up to date 
    VxVM VVR vxrlink INFO V-5-1-4467 Rlink datarlk is up to date 
    VxVM VVR vxrlink INFO V-5-1-4467 Rlink datarlk is up to date 
    ......
    NOTE:
    • To stop running the command, press the shortcut keys Ctrl+C.
    • This command can be executed only on the primary server.

Reference Standard

The data replication status is normal in the scenario where the Table 1 standard is complied with.

Table 3-8 Standard data replication status

Command

Item

Standard

vradmin -g datadg repstatus datarvg

Data status

Data status is in the consistent, up-to-date state.

Replication status

Replication status is in the replicating (connected) state.

vxrlink -g datadg -i 5 status datarlk

Output information

The output information is Rlink datarlk is up to date.

Troubleshooting
If the data replication status is abnormal, run the vxrlink -g datadg -i 5 status datarlk command and observe the output replication process, and then repair the data replication function according to the actual condition.
  • If the terminal displays that the required data remains the same (that is, the number of bytes following AUTOSYNC in the screen remains the same), data replication between the primary and secondary servers is abnormal. In this case, check the communication status between the primary and secondary servers such as the bandwidth, stability, and firewall settings, and repair the data replication function in time.
  • If the terminal displays that the amount of the required data becomes smaller (that is, the number of bytes following AUTOSYNC becomes smaller), the system is synchronizing and restoring data. After Rlink datarlk is up to date is displayed in the screen, wait for a period of time (about 30 minutes). During this period of time, if Rlink datarlk is up to date is displayed in the screen continuously, data replication between the primary and secondary servers is normal. Otherwise, check the network stability between the primary and secondary servers such as the bandwidth and packet loss, and repair the data replication function in time.

If the fault persists, contact the local Huawei representatives in a timely manner or customer service center to obtain technical support based on the actual maintenance situation.

Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044373

Views: 25064

Downloads: 74

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