cancel
Showing results for 
Search instead for 
Did you mean: 

Homogeneous system copy on the same hardware and OS

Former Member
0 Kudos

Hi!

When I installed our Q system I was given the wrong user, a local admin instead of a domain admin. Now we can not perform backup with our backup tool, HP dataprotector, because of authorization issues.

My solution is to "move" the system to the domain and to do that I need to do a Homogeneous system copy.

Our system is a 64-bit CRM 7.0 ABAP and J2EE on Windows 2008 with Oracle 10.2

I've read note 676468, 1238351 and the System Copy Guide - System Copy for SAP Systems Based on SAP NetWeaver 7.0 and from this I can see the following ways to do it

1. using SAPinst for export and import

2. using an offline backup

3. copy database files

What are your experiences with the different methods and what would you recommend?

rollo

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

When I installed our Q system I was given the wrong user, a local admin instead of a domain admin. Now we can not perform backup with our backup tool, HP dataprotector, because of authorization issues.

I'm use Local installation and use the Data Protector for backup without issues . Explain and post your error's in detail.

Regards.

Former Member
0 Kudos

We got this error

BR0278I Command output of 'D:\usr\sap\DCT\SYS\exe\uc\NTAMD64\backint.exe -u DCT -f backup -i F:\oracle\DCT\saparch\.aedyqjez.lst -t file -c':

[Critical] From: OB2BAR_BACKINT @ crmtest.europe.com "TARGET" Time: 2010-08-23 13:14:48

[131:51] #User "SAPSERVICEDCT.CRMTEST @ crmtest.europe.com" is not a valid Data Protector user

[main] OB2_Init(OB2_APP_SAP, appName=DEFAULT, errCallBack) failed. Error: [13] The data is invalid.

[Critical] From: OB2BAR_BACKINT @ crmtest.europe.com "TARGET" Time: 2010-08-23 13:14:48

[139:24] #Cannot init Data Protector Cell Manager.

Anyway, to have a homgeneous enviroment, we should reinstall the system.

rollo

Former Member
0 Kudos

Try for example create this user in "USERS" list in DATA PROTECTOR.

Only sap backup does't works ? Are you install without problem SAP agent?

In any case if you need reinstall , do it ... But why ?

Regards.

Former Member
0 Kudos

The system ernviroment should be homogeneous, D, Q and P, that is the reason for the copy

rollo

volker_borowski2
Active Contributor
0 Kudos

Hm,

that seems to me a bit overdosed for just a user mismatch...

Read the Instguide. There is a section how to create the domain users

manually in case you can not do an installation with Domain Admin privs.

After you have created the users, you only need to set the environment.

That might be a bit of look-left-screen look-right-screen action, but should

not take more than 15 minutes.

As for the permissions on windows, those should have all been assigned

on local group level, so you only need to assign your new domain users

to the local groups and you are done.

As none of these touches the exiting accounts. I'd give this a try first.

If it fails, you can always revert to the local users and try option two.

Volker

markus_doehr2
Active Contributor
0 Kudos

> that seems to me a bit overdosed for just a user mismatch...

It is not "just" a user mismatch, the full environment is wrong (wrong user ID).

Windows stores users not as usernames but as UIDs (see HKEY\USERS in the registry). All permissions and ACLs and registry access permissions are using that UID - including the enviornmental settings, DCOM configurations etc.

Therefore I would go for system copy as stated in

Note 1233320 - Domain migration for SAP system

Technically it may work on the first look, problems may arise later. <sid>adm has to have some special permissions/policies that are not visible (like 'locking pages in memory' or 'act as part of the operating system' or 'run as batch') etc.

Markus

volker_borowski2
Active Contributor
0 Kudos

Hi Markus,

thanks for that note, never came across this one.

So rollo, do NOT do it my way

Volker

markus_doehr2
Active Contributor
0 Kudos

> 1. using SAPinst for export and import

> 2. using an offline backup

> 3. copy database files

The quickes way is

- running sapinst and select "backup/restore" as system copy option

- sapinst halts and ask you to restore the database

- sapinst continiues and adapts the environment

Markus