From an elevated PowerShell window, run Get-Cluster.
In the Deployment Properties, change Does your deployment include Disaster Recovery (DR)? to No. Re-run LRII, removing the host record for the Secondary server. Change any components using the shared DNS or failover IPs in DR to instead use the management IP of the XM/PM. The SQL job LogRhythm DR Job Management is gone, and that all remaining SQL Server agent jobs are enabled. The environment variable CONSUL_CLIENT does not exist on the XM/PM. The LogRhythm folder in the Windows Task Scheduler has been removed. No databases are in a state of Synchronizing, Not Synchronizing, Restoring, or Suspect. Post-Uninstall Considerations and ValidationĪfter uninstalling DR, you may need to verify the following conditions and make configuration changes elsewhere in your LogRhythm environment: If you are running DR (but not HA+DR) in LogRhythm 7.3 and later, enter 2. If you are running DR in LogRhythm 7.2 and older or an HA+DR deployment in any version of LogRhythm, enter 1. The uninstall script on the secondary server includes a prompt to properly identify your deployment. From the DR Install folder, right-click DR Re-IP Uninstall.exe, and then click Run as Administrator.Įnter the IP addresses for the deployment. This port can be changed with the DR Re-IP and Uninstall tool. Replication Ports. By default, listeners are open for replication traffic on port 5022. The DR Re-IP and Uninstall tool updates these elements with no additional manual steps. 
Replication IPs used to facilitate transaction movement between SQL Servers (XMs and PMs in LogRhythm) must be applied to endpoints for SQL and mapped to endpoints for Availability Groups, all of which is difficult to update manually. Cluster names can be updated with the DR Re-IP and Uninstall tool. Failover IPs can be changed with the DR Re-IP and Uninstall tool.
Management IPs also facilitate SQL queries from scripts and are used in certain SQL jobs. These typically do not impact data mirroring, but changes to a management IP impact the failover IP, which must be in the same subnet as the management IP. Multiple pieces of a DR deployment can be changed with the LogRhythm DR Re-IP and Uninstall tool: As of LogRhythm 7.5, the DR Re-IP and Uninstall tool only works with SQL authentication. Due to SQL restrictions, changing IPs in older versions of DR and HA+DR requires re-installation. The DR Re-IP utility only works on DR deployments that leverage Always-On High Availability Groups, which exist in standalone DR versions in LogRhythm 7.3 and later.
0 kommentar(er)
