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 V300R010C00SPC200, 300, and 500 Local HA System Software Installation Guide (SUSE Linux + Oracle + Veritas) 11

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).
What Can I Do If the Active and Standby Servers of the Veritas System Failed to Be Connected Because the lvdbdata Partition Sizes Are Different

What Can I Do If the Active and Standby Servers of the Veritas System Failed to Be Connected Because the lvdbdata Partition Sizes Are Different

Question

An error message is reported when the maintenance tool is used to connect the active and standby servers, as shown in Figure 13-4. After I log in to the two servers and check the lvdbdata partition sizes, it is found that the sizes are different. What can I do?

# hares -online mountDBRes -sys Server host name

# df -h | grep /dev/vx/dsk/datadg/lvdbdata

/dev/vx/dsk/datadg/lvdbdata    345G  9.1G  318G    3% /opt/eSightData
Figure 13-4 Error message reported by the maintenance tool

Answer

  1. Check the lvdbdata partition on the active and standby servers and record the server whose lvdbdata partition size is smaller.

    1. Log in to either server as the root user.
    2. Run the following command to query the lvdbdata partition size and record the size:
      # fdisk -l 2>/dev/null | grep Disk | grep /dev | grep -i VxVM | awk '{print $2 $3}'|head -n 1
      /dev/VxVM27000: 350GiB, 375809638400
    3. Repeat 1.a and 1.b to check the lvdbdata partition size on the other server and record the IP address of the server with a smaller partition size.

  2. Based on the information in Step 1, expand the lvdbdata partition of the server with a smaller partition size to be the same as that on the other server.

    1. Log in to the server with a smaller lvdbdata partition size as the root user.
    2. Bring the resource group AppService offline.

      # hagrp -offline AppService -sys `hostname`

      Run the following command to query the AppService resource status. Perform subsequent operations after ensuring that the resource status is displayed as OFFLINE:

      # hagrp -state AppService -sys Server host name

    3. Run the following command to expand the lvdbdata partition:

      # /etc/vx/bin/vxresize -f -F ext3 -g datadg lvdbdata XXXg

      Ensure that the lvdbdata partition sizes on the active and standby servers are the same. In the preceding command, the value of XXX indicates the larger size of the lvdbdata partition.

    4. Bring the resource online.

      # hares-online mountDBRes -sys `hostname`

  3. Run the following command on the active and standby servers to check whether the partition sizes are the same:

    # fdisk -l 2>/dev/null | grep Disk | grep /dev | grep -i VxVM | awk '{print $2 $3}'|head -n 1

    /dev/VxVM27000: 350GiB, 375809638400

  4. Connect the active and standby servers again.
Download
Updated: 2019-12-13

Document ID: EDOC1100044372

Views: 38667

Downloads: 27

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next