![refresh option on db solo refresh option on db solo](https://help.msp360.com/content/images/restore-sql-db-backup-options.png)
![refresh option on db solo refresh option on db solo](https://blogs.sap.com/wp-content/uploads/2020/12/12-7.jpg)
REFRESH OPTION ON DB SOLO LICENSE
![refresh option on db solo refresh option on db solo](https://i0.wp.com/ittutorial.org/wp-content/uploads/2020/08/restore-db-4.png)
Compare and fix the SAP profile (DEFAULT) parameters from copied profile directory.Safer side execute sp_help_revlogin scripts on Primary and Secondary nodes (Similar to when initial installation was done).Check database status in both Nodes (It should be synchronized).Check ILB IP Address and Port 59999 is properly assigned to Listener (* This is relative to Microsoft Azure Cloud Cluster).Check Dashboard for the Availability Group Status if there is any error or not.Add both nodes in Availability Group as Primary & Secondary during Availability Group Creation.Create Availability Group from Primary Node.Check & Set the security settings for Always On Group.Restore Backup taken from Primary Node with option “RESTORE WITH NORECOVERY”.Database () can also be deleted from Databases as it will be restored later. Login to SQL Management Console on Secondary Node and check if Availability group or Listener exists (If entry still exists then simply delete it).Initiate Backup from Primary Node and transfer this backup to Secondary Node.TLOCK, DBSNP, DDLOG etc) as per SAP System Copy Guide. After SAP Installer runs successfully, login to SQL Management Console and delete tables (e.g.Need to select “Homogeneous System Copy (MS SQL Server Specific: Detach/Attach or Backup/Restore) option.Run SWPM and select option System Copyà High Availability System à Database Instance as per your SAP Release/Version.Restore Source Database from Disk or Tape on Primary Database Node.Delete Data and Log Files from both Nodes.
REFRESH OPTION ON DB SOLO OFFLINE
Bring your Database Offline on Secondary Node.Logon to Secondary (Replica) Node of Database and open SQL Management Console as Administrator.Bring your Database Offline on Primary Node.Delete Database From Availability Group (Always On High Availability à Availability Groupà (Primary)àAvailability Databasesà Database).Logon to Primary Node of Database and open SQL Management Console as Administrator.Stop Target System SAP Application & Database.Hope this will help fellow group members Steps To Perform I have tried to consolidate all points & steps included in doing such kind of activity. Now as part of maintenance we might have to do database refresh (as part of regular support or if you build new system and want to restore database from existing system). SQL Server AlwaysOn is very good functionality introduced by Microsoft as you can achieve high availability solution with actual copy of database with real time synch mode.