Usage Scenario
Generally, the configurations and service entries of cluster members are consistent. If the automatic backup function of the cluster cannot ensure the synchronization of the configurations and service entries, you can run this command to manually back them up in batches. For example, during the establishment of a cluster, configurations or service entries may be inconsistent between devices. In this case, you can run this command to perform batch backup.
Impact
After this command is run, the management master device backs up its excess configuration commands and status entries to the peer device, but does not synchronize or delete the excess configuration commands and status entries that are generated by the peer device.
Batch backup takes a certain period of time. The more the configurations to be backed up, the longer the backup time. Therefore, after running this command, you need to wait for a period of time before you can view the backup configuration on other devices.
If cluster members have the same configuration command with different parameters, the command configuration cannot be synchronized. You need to manually modify the configuration.
This command can be run only in the root system and cannot be run in a virtual system. However, the configuration in the root system takes effect for the root system and all virtual systems. That is, after this command is run, the configurations and status entries of the root system and all virtual systems can be backed up to the peer end.