Go live phase
During the Go-Live phase it is important to follow the playbooks you developed in earlier phases. Execute the steps that you tested and trained. Don't accept last-minute changes in configurations and process. In addition, apply the following measures:
Verify that monitoring is operational. Recommended monitoring approach includes Azure portal, Azure Monitor as well as Perfmon for Windows and SAR for Linux. Monitor the following counters:
Average CPU time – Total (all CPU)
Average CPU time – each individual processor (so 128 processors on m128 VM)
CPU time kernel – each individual processor
CPU time user – each individual processor
Memory Page in/sec
Memory Page out/sec
Disk read kb/sec – per individual disk
Disk reads/sec – per individual disk
Disk read ms/read – per individual disk
Disk write kb/sec – per individual disk
Disk write/sec – per individual disk
Disk write ms/read – per individual disk
Network packets in/sec
Network packets out/sec
Network kb in/sec
Network kb out/sec
After the migration of the data, perform all the validation tests you agreed upon with the business owners. Accept validation test results only if you have results for the original source systems.
Verify that all interfaces are functioning and that applications can communicate with the newly deployed production systems.
Validate the transport and correction system through SAP transaction STMS.
Perform Database backups once the system is released for production.
Perform VM backups for the SAP application layer VMs once the system is released for production.
For SAP systems that were not part of the current go-live phase, but communicate with the SAP systems that you moved into Azure in the current go-live phase, you need to reset the host name buffer in SM51. This step will purge the cached IP addresses associated with the names of the application instances you moved into Azure.