The hrp sync command synchronizes the current configurations and status entries of one FW to the other FW in the hot standby networking.
| Parameter | Description | Value |
|---|---|---|
config |
Immediately backs up device configurations. |
- |
connection-status |
Immediately backs up status entries. |
- |
Application Scenarios
Generally, after the active/standby relationship is established for two FWs, the new configurations and status entries that support backup on one FW are automatically synchronized to the other FW. Before the establishment of the active/standby relationship, the existing configurations and status entries on two FWs are not synchronized automatically. In this case, you can run the hrp sync command to implement manual batch backup.
For example, there is only one FW in the original network. Now one more FW is required for hot standby. After the two FWs implement hot standby, you can run the hrp sync command on the original FW to synchronize configurations, such as policies, to the newly added FW.
Configuration Impact
If the hrp sync command is run on the FW, the FW synchronize its extra configuration commands and status entries with the peer device, but does not synchronize or delete the extra configuration commands and status entries of the peer device.
The configuration backup time depends the configurations to be backed up. After running the command, you may need to wait a specific period to view the backed up configurations on the peer device.
If the active and standby FWs have the same configuration commands but different parameters, the hrp sync command cannot synchronize the parameters, and you must modify them manually.
By default, the hrp sync config command does not back up static routes. If the hrp auto-sync config static-route command is run to enable the automatic backup function of static routes, static routes will be synchronized to the peer device after the hrp sync config command is run.
The command can be used only on the root system, but not on any virtual system. However, the configurations on the root system take effect for the root system and all virtual systems. After the command is run, the configurations and status entries of the root system and all virtual systems are automatically backed up to the peer device.
Precautions
When you run the hrp sync config command to manually back up data in batches, the configuration information in the SSL VPN database and user database cannot be backed up.