What Do I Do If Data on ServiceCenter Fails to Be Backed up

4

【Product�?
ManageOne ServiceCenter

【Version�?
3.X

【Question�?
What do I do if data on ServiceCenter fails to be backed up?

【Answer�?
Step 1 Use PuTTY and the management IP address of the active node to log in to the ServiceCenter active node as user galaxmanager. The default user password is Huawei@CLOUD8.
If ServiceCenter is deployed in single-node mode, the management IP address of the node is used for login.

Step 2 Run the following command to disable logout on timeout:
TMOUT=0

Step 3 Run the following command to enter the engineering mode:
gotoEngineerMode

Step 4 Run the following command to disable logout on timeout:
TMOUT=0

Step 5 Run the following command to go to the /opt/gmbackup/db directory:
cd /opt/gmbackup/db

Step 6 Run the following command to check the number of automatic backup files. The default number of automatic backup files is 7.
cat /opt/gmbackup/backup.conf | grep "MAX_AUTO_BACKUP_NUM"

Step 7 Run the following command to view the backup files under the /opt/gmbackup/db directory:
ls

Step 8 Check whether the number of backup files under the /opt/gmbackup/db directory is greater than the configured number of automatic backup files.
If yes, go to Step 9.
If no, contact Huawei technical support.

Step 9 Run the following command to delete the backup files whose sequence number is relatively small until the number of backup files under this directory is equal to that of automatic backup files.
rm -r Name of the backup file with the smallest sequence number


----End

Other related questions:
How do I back up the MQ data?
MQ information is persistently stored on an SSD. When an exception occurs, SSD data can be automatically collected if the SSD is unformatted. The cluster does not provide independent MQ data backup and restoration functions.

Failed to Back Up System Configuration Data
1.Use PuTTY to log in to the OceanStor BCManager node. Use the Management IP address to log in as user ICUser. 2.Run the following command to disable logout on timeout. TMOUT=0 NOTE: After you run this command, the system continues to run when no operation is performed, resulting a risk. For security, run exit to exit the system. 3.Run the following command and enter the password of user root to switch to user root: su - root 4.Run the following command to go to the directory of the configuration file. cd /etc/ssh 5.Run the following command to open the configuration file. vi sshd_config 6.Press I to enter the editing mode. 7.Change parameter values in the configuration file, as shown in the following: PermitRootLogin yes PasswordAuthentication yes PermitEmptyPasswords no ChallengeResponseAuthentication no UsePAM yes 8.Press ESC and enter :wq to save the settings and exit the VI editor. 9.Run the following command to restart the sshd service. service sshd restart 10.After the next backup point in time, check whether the backup failure alarm has been cleared. If yes, no further action is required. If no, contact technical support.

What Do I Do If ServiceCenter Failed to Interconnect with FusionManager
【Product�? ManageOne ServiceCenter 【Version�? 2.X 【Question�? What do I do if ServiceCenter fails to interconnect with FusionManager? 【Answer�? Step 1 Check whether the following two conditions are met: "no connector found in db" exists in the connector.log file of ServiceCenter. "system account already locked" exists in the portal.log file of FusionManager. If the preceding two conditions are met, the status failure occurs because FusionManager locked the FMRest account. Unlock the account to resolve the problem. Step 2 Use PuTTY and the floating IP address of the management nodes to log in to FusionManager as user galaxmanager. If FusionManger is deployed in single-node mode, use the management IP address to log in to FusionManager. Step 3 Run the following command to disable PuTTY logout on timeout: TMOUT=0 Step 4 Run the following command to unlock the FMRest account: unlockSysAccount FMRest ----End

In FusionManager V100R005,what's the mean of the alarm "ALM-ServiceCenter.9206 Failure to Back up Data"
The backup and restoration module automatically backs up the data to the local server at 02:00 every day and uploads the backup files to the third-party server every 30 minutes. This alarm is generated when the backup and restoration module fails to automatically back up data, execute backup operations, or upload the backup files to the third-party server. The corresponding error codes and error information will be displayed in the additional information about the alarm.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top