Creating SAP system clones using Solaris 10 virtualization concepts (Part 2)
Creating SAP system clones using Solaris 10 virtualization concepts (Part 3)
This is the 4th part of a blogger series describing how to easily create runable shadow copies of productive SAP systems using Sun Solaris 10 native OS virtualization functionalities (Solaris Zones). These shadow systems can be used for applying updates, patches or similar tasks which would result in a downtime of the productive system otherwise.
After the desired task was performed successfully, the shadow systems can be switched with the productive systems. This way the planned downtime of the productive system landscape can be reduced dramatically.
This part demonstrates how the steps performed in Part 2 and Part 3 can be automatized using a bash script.
Automatizing the steps
Cloning the system
The first demo shows how the steps described in Part 2 can be simplified using the bash script attached.
Description: Initially two zones exist on the system which are sap_zone_1 and oracle_zone_1. These zone are installed within two ZFS volumes. The ifconfig command shows the initial configuration of the network of the two zones. Note that ce0:3 is holding the public IP address of the productive SAP system.
Using the sap_shadow.sh create two clones of the installed zones are created. Note that the timestamp used when executing the command includes the yes verification.
After booting the new zones the zoneadm command lists 2 new zones which are sap_zone_2 and oracle_zone_2. When listing the network configuration via ifconfig the network interfaces of the new zones are displayed.
Switching the systems
In the second part the switch of the systems using the bash script is demonstrated.
Description: First the SAP Management console is configured to monitor three SAP hosts: rigsun02 is the source system which is cloned in step 1, rigsun04 is the cloned system which is running now. rigsunvirtual01 is the virtual hostname of the SAP system. The name resolution of this system is established using a DNS entry. Note that the Process ID of rigsun02 and rigsunvirtual01 (e.g. 12915 for the SDM) is the same due to they are referring to the same system. The PID of the SDM of rigsun04 is 10481.
Afterwards two different folders in the old and in the new system are created to show how the content in both systems can be changed independently. This also demonstrates on which system rigsunvirtual01 is referring to.
The command “sap_shadow.sh switch” triggers the switch of the systems. Please note that the timestamps used when executing the command includes the time for verifying the command (“yes”). The system switch can be controlled by listing the virtual network interfaces: The interface ce0:3 of sap_zone_1 possess the private ip address which was bound to ce0:7 of sap_zone_2 before. Vice versa ce0:7 holds the public IP address 10.17.70.132 now. This is the public address of rigsunvirtual01 which is registered in the DNS.
Finally the result can be verified by controlling the new PID of rigsunvirtual01 and the folder names within the portal public documents directory.
Download the demo script
Part 5 will contain a conclusion and further considerations for implementing the setup described here.
Next Part: Conclusion (Available soon)