S
SteffenMueller
Creating an SAP System Using Azure NetApp Files (ANF) for data- and logfiles for Microsoft SQL Server
By Ralf Klahr and Steffen Mueller
Management Summary
This blog is based on the blog Restoring an MS SQL 2022 DB from a ANF SnapShot for creating SQL Server database copies. In addition, the creation of a new SAP system based on an SAP provided installation and the use of a copied database as foundation for SAP system copy is described.
Since ANF volume-based files can only be mounted by their UNC name and not by an assigned Windows drive letter an empty database needs to be created for the initial setup of a NEW DB (SAP SID). The SAP Software Provisioning Manager (SWPM), however, does not support UNC names for Windows. Therefore, the database must be created manually via SQL Server Studio, T-SQL scripts or other automation tools. The name should be identical to the SAP standard naming conventions which is usually the SID name for the SAP system. During the execution of SWPM, SWPM will recognize an already existing database and offer to use it for the continuation of the installation. From this point onwards, the installation will continue with the standard workflow for the selected installation type.
Create 2 NetApp volumes – one for data and one for log files.
Create SQL Database based on previously created volumes
Run SAP Software Provisioning Manager (SWPM)
SWPM will pick up the existing DB, in this case SQ1, and resume the installation in the usual sequence.
Installation of NEW SAP system based on an existing SAP SQL Server DB
If the database is already up and running the rename can be performed within the SQL Server Management Studio by right-klick its name and select the Rename option. We now have a copy of the SAP source system DB. The file names in the restored snapshots are identical to the source DB file names. To make these unique you can mount the volume and change these data files name to reflect the file names of the target DB. The database must be detached before this step. If this step is skipped the physical file names will still refer to the old names. With the attach option the DB can now be attached with the new DB SID to the existing DB environment
This DB copy is the basis for either a SAP system refresh or the creation of a new SAP system. It should have the corresponding SID of the desired SAP system. Since the restored DB is a copy of the source DB, the schema within the DB needs to be adjusted. This can be done with SWPM. In case of a system refresh, the existing DB will be overwritten but no changes to the ASCS and PAS are required. In this case the SWPM menu sequence NW Version -> MS SQL Server -> System Copy -> Target System -> Based on AS ABAP -> Standard/Distributed/High-Availability -> Refresh or Move Database Instance
This will adapt the DB to the new schema of the target system.
If you want to create a NEW SAP system based on a DB copy the SWPM menu sequence: NW Version -> MS SQL Server -> System Copy -> Target System -> Based on AS ABAP -> Standard/Distributed/High-Availability -> Standard System. This will install an ASCS and a PAS and adapt the schema within the DB.
When asked for source of the DB make sure to choose Homogenous System Copy to indicate that the new DB already exists since it was previously created with AzAcSnap.
Continue reading...