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.


Database Auto-scheduled Backup Failure

Publication Date:  2012-07-25 Views:  130 Downloads:  0

Issue Description

We use U2000 V100R002C00, The backup process failed to start, even though all the related server processes/services were active. When the database was backed up manually, the operation was successful.

Alarm Information


Handling Process

1. Run the following script to stop the MSuite process: /opt/HWENGR/engineering/ (c:\HWENG\ on Windows) 2. Run the following script to restart the MSuite process: /opt/HWENGR/engineering/ (c:\HWENG\ on Windows) 3. Back up the database again.

Root Cause

Because relevant logs are unavailable, the root cause failed to be located. There are three possible causes for this problem :- The possible causes are as follows: 1 The U2000 maintenance suite (MSuite) server (not the U2000 server) is not started. Run the following scripts to restart the engineering server process: /opt/HWENGR/engineering/ (c:\HWENG\ on Windows) /opt/HWENGR/engineering/ (c:\HWENG\ on Windows) 2- The U2000 MSuite client is running. The MSuite client is started on the U2000 server. In this case, database backup on the U2000 client inevitably fails because the U2000 client and MSuite client share the same engineering server. Stop the MSuite server to resolve this problem. Approximately 30% database backup failures are caused by the running of the MSuite client. 3- Memory or disk space is insufficient. Insufficient memory space (less than 500 MB) or disk space on the U2000 server may cause a database backup failure. Stop some memory-eating services or programs to resolve this problem. If database backup still fails, restart the U2000 server.


Restart the MSuite server, wait for several minutes, and then back up the database again.