Backup/Recovery of NW70 Java/ABAP System

[Zoom]

Hi,

Some questions regarding setting up and testing the recovery of Java plus
ABAP systems. I recovered ABAP systems multiple systems, so the issue
is the Java backup/restore (In this case Windows/Oracle)

From what I can read in SAP's documentation, as well as some previous
discussions, the idea is something along the lines of (Please correct me if I am
wrong):

- Backup /usr/sap/<SID> : Ensure a backup after SDM changes (Preferably, configtool changes also):
- Backup the database using DB tools.
- Backup the JDK
- I haven't read it, but I would backup the env. variables and registry settings.

To restore (Assuming a new server with a different name as the original system
needs to be up when testing the procedure)

- Restore JDK
- Build DB
- Restore database.
- Build NW with the patch level of original
- Restore /usr/sap/<SID>
- Make hostname changes as per #757692.

I realize that this is essentially a system copy and that it should be done using the
NW system copy tools, but I don't think (And I would like to be proven wrong)
that the NW system copy procedure can be automated to run, say, weekly?


Thanks,

Zoom

[ERP]

You can just restore the binaries (at least for netweaver) and follow note 8307 to change the hostname for the abap bits.

[Zoom]

Hi ERP,

Thanks for the info.

Given that you used #8307 to change the hostname from the ABAP side,
did you not need #757692 to do so for the Java side?


Thanks,
Zoom

[ERP]

Yep I used both notes to do it.

[Zoom]

Hi ERP,

Thanks. I tried the procedure, and the restart of the restored NW system fails because
instance.en.host fails; It contains the original hostname.

Note #1120872 mentions that in releases NW70SP9 and lower, this can be changed
in a Properysheet in configtool, but our server is higher than SP9. The procedure did not
work.

Have you managed to change this parameter, or did you have issues with it?


Thanks,
Zoom

[ERP]

OK - this may look funky as I cut and paste from a word document with screenshots and did some quick replace's of hostnames, sids etc, but these are the steps I followed and they worked fine.

15) SAP Configuration Changes for the new hostname

The following is based on SAP Notes 8307 & 757692. Get the latest copies of these notes and ensure all steps listed in the notes are followed.

For user <sid>adm

Adapt the Instance Profiles.

cd /sapmnt/<SID>/profile

All files that include the hostname need to be renamed to include the new hostname

eg. <SID>_DVEBMGS33_sap<SID>1 needs to renamed to <SID>_DVEBMGS33_<hostname>

Edit all of these files looking for the old hostname and changing them to the new hostname

As /usr/sap/trans on <hostname> comes from the <hostname> host a new mount must be created for the BI transport directory. This was mounted on /usr/sap/<SID>trans
The DIR_TRANS parameter in the instance profile needs to be changed to /usr/sap/<SID>trans. Also change any values of /oracle/<SID>/920_64 to /oracle/<SID>/102_64 in the above files.

Run the configtool from /usr/sap/<SID>/DVEBMGS33/j2ee/configtool

You will get an error regarding connecting to the database, choose OK and the configtool will start. In the tree on the left hand side choose Secure Store and change admin/host/<SID> to the new hostname. Also check the jdbc/pool/<SID>/Url value.



Once these changes are made, close the configtool and restart it.

We had an issue where we still couldn’t connect to the database. The issue was in the config.properties file. Change all instances of /oracle/<SID>/920_64 to /oracle/<SID>/102_64.

Once successfully logged into the database using the configtool, perform the following changes to global and local properties (if available);

Global Dispatcher Configuration à Managers à Cluster Manager.
Change the ms.host property to point to the new hostname.


Do the same for the Global Server Configuration node. Also check the same nodes under Instance_IDXXXX

Global Dispatcher Configuration à Locking Manager
Change enqu.host to point to the new host name. Also check enq.profile.filename as the profile name changed



Do the same for the Global Server Configuration node. Also check the same nodes under Instance_IDXXXX

Select Instance_IDXXXX and change the Message Server Host parameter to the new host.



Under Instance_IDXXXX à Dispatcher_IDXXX à Managers à Configuration Manager check the values to ensure the old hostname isn’t mentioned.



Do the same for the Instance_IDXXXX à Server_IDXXX à Managers à Configuration Manager node.



Under Global Server Configuration à Services à com.sap.security.core.ume.server change the property ime.r3.connection.master.ashost to the new host name.



Apply all changes by choosing the menu option File à Apply

Exit the Configtool.

Now to change the properties of the SDM.

cd /usr/sap/<SID>/DVEBMGS33/SDM/program

edit the file localsdmgui.properties so that the workingHost property reflects the new value. Also change the transport directory to point to the BI transport directory.



cd /usr/sap/<SID>/DVEBMGS33/SDM/program/config

edit the file sdmrepository.sdc. Change the host and mshost tags to reflect the new value (Do a global replace of sap<SID>1 to <hostname>). NOTE: Be careful editing this file. Any extra characters or formatting errors will cause the SDM to be unusable.



To do a global replace use %s/sap<SID>1/<hostname>/g

cd /usr/sap/<SID>/DVEBMGS33/j2ee/cluster/boodevrap

Edit the boodevrap.properties file to replace any occurrences of the old host name with the new one. There weren’t any for <SID>.

[Zoom]

Hi ERP,

Thanks for posting the detailed information. I remember going through these steps, but I may have missed one or two.

What operating system and SP level were the systems that you had recovered?


Zoom

[ERP]

Was a CRM 2007 system SP6 I think (not sure of the patch level at the time).

HP-UX 11.31, Ora 10.2.0.2