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


To have a better experience, please upgrade your IE browser.


FusionCloud Troubleshooting Guide 03

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).
Verifying the Integrity of a Backup File

Verifying the Integrity of a Backup File

Before restoring data using a backup file, verify the file integrity.


The node where the master (or single) instance resides has the backup file and signature file.


  • To verify the integrity of a backup file, calculate the backup file digest and compare the digest with the digest saved in the file.
    • If they are consistent, the backup file can be used to restore data.
    • If they are inconsistent, the backup file has been modified. In this case, do not use the file to restore data. Delete it instead.
  • If an incremental backup file exists, verify both the full and incremental backup files.


  1. Use PuTTY to log in to the node where the master database instance or single instance resides.


    You can log in to the ManageOne deployment plane and choose Deployment > Database > RDBMS to query the node.

    Default account: sopuser; default password: D4I$awOD7k

  2. Run the following command to switch to the root user:

    su root

    The default password is Changeme_123.

  3. Run the following command to access the directory where the backup file is located:

    cd /opt/pub/backup_local/

  4. Run the following command to decode the signature file:

    base64 --decode ossdbsvr-1-999@2-999_ossdbsvr-2-999_20160527151800_auto_full_day_physical.tar.gz.sign > tmp.sign

  5. Verify the file signature.

    openssl dgst -sha256 -verify Installation directory/manager/etc/cipher/backup_sign_pub.pem -signature tmp.sign ossdbsvr-1-999@2-999_ossdbsvr-2-999_20160527151800_auto_full_day_physical.tar.gz


    Generally, Installation directory is /opt/oss/.

    • If "Verified OK" is displayed, the verification is successful. Go to 6.
    • If "Verification Failure" is displayed, the verification fails. Go to 7.

  6. Run the following command to delete the tmp.sign file generated:

    rm tmp.sign

  7. Run the following command to delete the backup file:

    rm ossdbsvr-1-999@2-999_ossdbsvr-2-999_20160527151800_auto_full_day_physical.tar.gz*

    If the verification fails, the backup file has been tampered and therefore cannot be used to restore data.

    Contact technical support for assistance.

Updated: 2019-08-16

Document ID: EDOC1100063248

Views: 25210

Downloads: 40

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