Laserfiche WebLink
REV: 10-03-24 MI <br />3. Upon clicking save, the Traffic Manager will immediately begin directing traffic to the backup <br />App Service. <br />SQL database <br />1. The Principal Architect or designated Senior Software Engineer will load the Azure Portal and <br />load primary SQL Server instance blade. <br />2. On the Failover groups tab, the designated resource will click into the failover group. <br />3. In the event of an outage, it is assumed there is no ability to sync the primary so Forced Failover <br />should be selected to initiate a failover to the backup SQL Server instance for all databases <br />File Storage <br />1. The Principal Architect or designated Senior Software Engineer will load the Azure Portal and <br />load the Storage accounts blade. <br />2. The primary storage account will be selected <br />3. The Geo-replication tab will be selected <br />4. The option for Prepare for failover will be selected <br />5. The designated resource will type in ‘yes’ to confirm, noting the last sync time and reporting to <br />the Outage Team <br />ATTY/AGR.2024.180/Neighborly Software (Page 25 of 26)