Open topic with navigation
To upgrade from a previous version of the SAP Recovery Kit, perform the following steps.
Prior to upgrading, please review the Plan Your Configuration topic to make sure you understand all the implications of the new software.
Note: If running a version prior to SAP Netweaver 7.3, the SAPHOST agent will need to be installed. See the Important Note in the Plan Your Configuration topic for more information.
It is recommended that you take a snapshot of your current hierarchy.
To start the process, download the new SAP Recovery Kit (steeleye-lkSAP-7.4.0-#.rpm - where # stands for a version number).
Make sure your mounts are correct. There are two SAP file systems that should be mounted. The following example uses a host name of sap10 and an SAP System ID of STC.
mount sap10:/exports/sapmnt/STC /sapmnt/STC -o rw,sync,bg,intr,udp
mount sap10:/exports/saptrans/usr/sap/trans -o rw,sync,bg,intr,udp
Enter the upgrade command.
> rpm -Uvh steeleye-lkSAP-7.4.0-#.rpm
This will start the upgrade procedure.
A backup will be performed of the existing hierarchy. The upgrade will then destroy the old hierarchy and recreate the new hierarchy. If there is a failure, see In Case of Failure below.
At the end of the upgrade, you will be prompted to run lkGUIserver restart to restart the LifeKeeper GUI server.
The LifeKeeper GUI server caches pages, so a restart is needed for it to refresh the new pages. As root, enter the command "lkGUIserver restart" which should stop and restart the GUI server. Exit all clients before attemtping such a restart.
Note: Restarting your entire LifeKeeper system is not necessary, but it would be advisable in a production setting to schedule some down time and go through an orderly system preparation time even though testing has not required a system recycle.
Log in to the LifeKeeper UI, note the hierarchy and make sure the hierarchy is correct.
It is possible to retry the upgrade. The upgrade script is kept intact in /tmp directory (lkcreatesaptmp). This is a temporary file that is used during the upgrade. The commands are written here and can be executed to create the hierarchy.
If there is a failure, an error or you suspect the hierarchy is not correct, the following steps are recommended:
Stop LifeKeeper using lkstop.
Remove the new rpm "rpm -e steeleye-lkSAP".
Install the old rpm "rpm -i steeleye-lkSAP-6.2.0-5.noarch.rpm".
Restore the old hierarchy using lkbackup -x (filename created in Step 4 above).
Contact SIOS Support for help. Prior to contacting Support, please have on hand the logs, the previous snapshot of the hierarchy, the hierarchy that was created and failed and the error messages received during the upgrade.
© 2012 SIOS Technology Corp., the industry's leading provider of business continuity solutions, data replication for continuous data protection.
Open topic with navigation