If the HA pair is using SSL, restore the server certificate by reloading it. Solace1(admin)# redundancy revert-activity If the backup virtual router on the primary appliance is local active, you may wish to restore the usual state by doing a revert-activity on the primary appliance:.mate active/mate active on the second appliance.local active/local active on the first appliance.Check activity status on both appliances:.Run the following command to rollback to the selected backup configuration file on the secondary appliance:.When the primary appliance is back in service, select the backup configuration file for the mate appliance.Solace1(configure/redundancy)# no shutdown Solace1(configure/hardware/message-spool)# exit Solace1(configure/hardware/message-spool)# no shutdown primary Solace1(admin/system/message-spool)# assert-disk-ownership Assert disk ownership on the primary appliance, and start the message spool and redundancy:.Solace2(admin/system/message-spool)# reset Solace2(configure/hardware/message-spool)# end Solace2(configure/hardware/message-spool)# shutdown Solace2(configure)# hardware message-spool On the secondary appliance, shut down the redundancy and message-spool, and then reset the message-spool:.The appliance restarts with the restored configuration. Solace1(admin/system/message-spool)# reset Solace1(configure/hardware/message-spool)# end Solace1(configure/hardware/message-spool)# shutdown Solace1(configure)# hardware message-spool Rollback to the selected backup configuration file on the primary appliance as follows:.The configuration file must have been taken while Guaranteed Messaging service was active. Select a backup configuration file for the primary appliance that you want to roll back to.To rollback to a previous Guaranteed Messaging configuration used by a redundant appliance pair, use the following procedure: The result is the restoration of a previously backed up Guaranteed Messaging service configuration.ĭuring the following procedure, all spooled messages are lost. The default procedure for restoring the configuration files for redundant appliance pairs running Guaranteed Messaging service is to use the reload Privileged EXEC command as described below. Solace recommends using a naming scheme for the backed up Guaranteed Messaging configuration files to help identify the appliance and Guaranteed Messaging activity at the time of backup.įor example, consider the backups for paired appliance R1 and R2, where R1 is active, and R2 is inactive:Ĭopy current-config config_R2_AD_inactive.Queue and topic endpoint configuration changes are only acknowledged on the inactive paired appliance when it assumes the active role.Further, a backup of the inactive appliance contains the queue and topic endpoint configuration that was present at the time this appliance was last active. Creating the configuration file backup while Guaranteed Messaging is inactive (that is, while the mate appliance is active), captures the Guaranteed Messaging configuration from when this appliance was last active.Creating the configuration file backup while Guaranteed Messaging is active captures the Guaranteed Messaging configuration at the time of backup.However, before creating configuration file backups, always note the local state of Guaranteed Messaging activity on the paired appliances and observe the following: The default backup procedure for paired appliances running Guaranteed Messaging is to run the copy current-config Privileged EXEC command. In addition, messaging data is not backed up, including: monitoring agents running in the broker (Datadog, SolGeneos).interface configuration (IP addresses, LAGs).trusted-root configuration (for appliances prior to software version 8.2.0 and software event brokers prior to version 8.7.0).TLS/SSL server certificate configuration.Some configuration information is not backed up, including:
0 Comments
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |