on 2016 Jun 27 2:34 PM
Hi Experts,
We have an upgrade coming up and for the same have to create sandbox systems for CRM (ABAP, Linux, Oracle), BW (ABAP+Java, Linux, Oracle) and EP (Java, Windows, MS SQL) from the production systems.
All our systems are on VMWare. We have high availability setup but only on the VM level, not on SAP level. The sandbox systems will be copied over as clones from the production systems. I have below two queries -
1. Can I use the system rename tool? I have checked all the prerequisites and we qualify all of that, except the HA. I am not sure this HA restriction (according to note 1619720) will apply in this case also where HA is only at the VM level.
2. If I don't or can't use the system rename tool, how can I change the systems. There will be a DB<sid> and SAP<sid> change. I know the post steps (running BDLS etc), but not sure how to change the SIDs of the system.
Thanks for your help in advance.
Regards,
Neha Bhardwaj
Hello Neha,
The HA being addressed at the SAP note 1619720 is when SAP itself is installed at an HA environment (cluster).
If the HA is at the VM level (by this I believe you mean that VMware will move the VM through different physical servers as needed), then you can consider that SAP is not under HA scenario for the purposes of the rename tool (in fact, SAP itself is not at HA , it is the VM that is).
Thus, I believe it should be OK to use the rename tool.
Regards,
Isaías
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Experts,
Can anyone throw some light on this please?
Thanks,
Neha Bhardwaj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Neha,
Based on your requirement i don't see any need for system rename tool !!! System rename tool will be generally used if you want to change the SID/instance number/host name of your existing system.
In your case it should be just a straight forward system copy or DB refresh you have to perform in the way Prithvi suggested above.
Regards,
Srikanth
Hi Neha,
After cloning you may need to perform SID rename using SWPM.
Few steps that includes after cloning are...
Change Profile.
Environment variables for SIDADM, DBSID.
Services file entries.
Check sapnote and link
1709155 - System Provisioning with SAP Landscape Virtualization Management
Cloning a System - SAP Landscape Virtualization Management, Enterprise Edition - SAP Library
You can also build sandbox system using old Production backup and perform post steps.
Regards
Prithviraj
User | Count |
---|---|
66 | |
10 | |
10 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.