Ansicht
Dokumentation
03733 - Moving SAP system
ROGBILLS - Synchronize billing plans ABAP Short ReferenceThis documentation is copyright by SAP AG.
Moving SAP system
I just moved a 4.0B v4r5 to new hardware. You will need to create ASP 2 on thetarget machine
first, you can do it later but I would just do it now and get it out of the way.
I did a GO SAVE
21 and restored it to the new box. I ran the new box side-by-side on a new IP
to make sure it was
all working fine, and I also had to disable the TCP/IP interface (can't have two
machines with the
same address). Along with this was changing the host table entries on the
DEV/TST to get it
talking to the new box and changing the hosts table on the new box to reflect
the new temporary
IP.
The only other thing I had to do was create a new journal reciever for QSQJRN in
ASP 2 and change
the journal to that new reciever so they all go into asp 2. I believe this is
normal.
It went great, only had a problem with 2 RMTR3DB jobs running (stopsap and
startsap too
quickly...) on monday morning (at 9 am of course).
Oh yeah, you'll also want to go through your system values. You will also need
to get a new
license key from SAP within 30 days of moving the system. You can run the
saplicense -temp
command on the target after the system is restored to run for those 30 days. I
also nixed all the
SQL packages just for good measure.
Good luck!
Andy Quaas
--- "mattmilneZEarthlink" <mattmilneZe...> wrote:
> Hi
>
> We are discussing moving a production system between two as/400's. Both
systems are at v4r5.
> SAP is 3.1i. One system has the production SAP system and the other just has
the OS. There is no
> ASP 2 configured on the target machine. We will need to configure the ASP on
the target machine
> first.
>
> One option is to do a type 21 save on the source machine and a type 21 restore
on the target
> machine. Both machines have Ethernet cards. Has anyone tried this ? We think
that in theory we
> will be able to back up the source machine , take it of the network and load
the target machine
> and bring it up as production. Before we test this I am interested if the
group has any
> thoughts/experiences of this technique. It is low risk because all we need do
is take the target
> box off the network and put the source box back if there is a problem.
>
> What we are doing is the same as if the source machine was lost and we
reloaded onto a new
> server.
>
> Matt Milne
>
__________________________________________________
Do You consolut?
Make a great connection at consolut Personals.
http://personals.consolut.net
Durban Tours - Südafrika Safari
General Data in Customer Master General Material Data
This documentation is copyright by SAP AG.
Length: 3253 Date: 20240425 Time: 141941 sap01-206 ( 2 ms )
