How to Back Up Data for the FSM Node in FusionStorage

4

Use PuTTY to log in to the active FSM node.
Ensure that the FSM floating IP address and username dsware are used to establish the connection.
Run the following command to disable logout on timeout:
TMOUT=0
Back up data for the FSM node to the local server.

Run the following command to switch to the directory containing the FSM command configuration tool:
cd /opt/dsware/client/bin/
Run the following commands to issue the command for manually backing up FSM data on the local server:
NOTE:
Because of system security hardening, you are required to enter the username and password for authentication after running the dswareTool command of FusionStorage. The default username to be authenticated is cmdadmin, and its default password is cmdHuawei@123.
The system supports authentication using environment variables so that you do not need to repeatedly enter the username and password for authentication after running the dswareTool command each time. For details about how to import environment variables, see Authentication Using Environment Variables.
sh dswareTool.sh --op executeBackupCmd
If the command output contains "Operation finish successfully", the command is issued successfully.
...
Operation finish successfully. Result Code:0
...
Check the backup files stored on the local FSM server.

Run the following command and enter the password of user root to switch to user root:
su - root
Run the following command to disable logout on timeout:
TMOUT=0
About 5 minutes after the manual backup command is issued, run the following command to switch to the directory containing the manual backup files:
cd /opt/dsware/manager/backup/manual/
Run the following command to view the files stored in the directory:
ll
Check whether the directory contains the latest backup file.
If yes, go to Step 10.
If no, contact technical support.
Determine whether to back up data to a third-party backup server.

Determine whether a third-party backup server is configured.
If yes, go to Step 11.
If no, no further action is required.
Check the backup files stored on the third-party backup server.

Determine the type of the OS used by the third-party backup server.
If the server runs Windows OS, go to Step 12.
If the server runs Linux OS, go to Step 15.
About 10 minutes after the local backup is successful, log in to the third-party backup server over a remote desktop connection.
For details, see Logging In to a VM in Remote Mode.
Switch to the directory containing backup files.
Directory containing manual backup files: Directory configured on the FTPS server\CloudComputing\DswareMgr_FSM floating IP address\manual
Check the files in the directory, then perform Step 19.
About 10 minutes after the local backup is successful, use PuTTY to log in to the third-party backup server.
Ensure that the IP address of the third-party backup server and username root are used to establish the connection.
Run the following command to disable logout on timeout:
TMOUT=0
Run the following command to switch to the directory containing backup files:
cd Directory configured on the FTPS server/CloudComputing/DswareMgr_FSM floating IP address/manual
Run the following command to view the files stored in the directory:
ll
Check whether the directory contains the latest backup file.
If yes, no further action is required.
If no, contact technical support.

Other related questions:
How to back up and restore U1930 data
1. Log in to the device using the LMT and access the config mode. 2. Choose Version > Configuration File Management, select the files to back up, set Execution Mode to Back Up, specify the backup directory, select the corresponding device, and click Execute. 3. Check the backup files. 4. After the backup is complete, click Open Directory, open the backup directory, and check whether the folder named after the device IP address contains a configuration file with the file name in format of _YYYYMMDDhhmmss (for example, license_20131106114255.dat). 5. Archive the configuration file for future system recovery. 6. Use the TFTP tool to upload the configuration file to the device when you need to restore the data.

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.

Method used to back up data on the USG6000
The methods used for backing up configuration content and restoring the configuration are as follows: 1. Back up and restore profiles using the FTP, SFTP, and TFTP servers (recommended). This method is applicable to the situation in which a large number of devices are maintained in a centralized manner. 2. If the device serves as an FTP server, you can configure the FTP server function for configuration backup and restoration without configuring FTP software. Open FTP ports cause certain potential security risks. 3. Back up the profiles on the storage server. The operation is simple and does not require other software. If the data is backed up on the same storage media, the primary and backup profiles may be damaged simultaneously. 4. The configuration data backup and restoration on the web UI is simple. You need to configure the web login in advance.

Does the MQ data need to be backed up?
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.

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