OS migration - Existing server is on Solaris need to change to Suse Linux

Dear SDN,
My Development server is on Sun solaris 10 and need to change the OS SUSE linux 10.
kinldy guide.
1.This is migration activity or Heteogenues copy.
Kindly suggest the steps invloed in it.
please provide your expert guidelines.
Database is Oracle 10.2.0.2 .(only need to change the os not database)
Regards,
Ravi Ghangurde

My Development server is on Sun solaris 10 and need to change the OS SUSE linux 10.
1.This is migration activity or Heteogenues copy.
This is a heterogeneous system copy.
please provide your expert guidelines.
Since it´s a heterogeneous copy you need to have a certified migration consultant on-site, otherwise you will loose support for the target system (see the FAQ at http://service.sap.com/osdbmigration).
Database is Oracle 10.2.0.2 .(only need to change the os not database)
I´d use the R3load method. This will give you a "free reorganization". There are however other ways of doing that (transportable tablespaces).
Be aware that Solaris on SPARC is a BigEndian platform whereas Linux is implemented as LittleEndian - so if you exchange binary data with other systems they need to be aware of that fact.
Markus

Similar Messages

Migrating from server 2003R2 to 2008R2 User cannot change password box unchecks after being checked.

After Migrating the domain controller from server 2003 R2 to 2008 R2 the check box for users cannot change password wont stay checked. This is happening to ALL users and no they are not a member of any Protected Groups. I have searched for a solution
for months but cant not find.
And now after migrating the exchange 2003 to 2010 I have to keep applying the inherited permissions every hour until a user finally makes an active sync.
Now having more AD issues, cant remove users from Exchange 2010...And again have to go to the DC and applying the inherited permissions, then I can remove the user.
I really need help with this...
John

Hi,
Did you use the migration tools to do the user migration?
Permissions on a user that is migrated from an Active Directory domain are reset to default values during migration.
I think this is by design:
http://technet.microsoft.com/en-us/library/cc974359(v=ws.10).aspx
Regards.
Vivian Wang

When I try to send an email with photo attachment to a contact a screen appears stating "the sender name is not recognized by the server " what do I need to change so this will not happen in the future. I am a novice!!!!!

When I try to send an email with photo attachment on my iPad a screen appears which states " the sender is not recognized by the server" . What do I have to change so I can always send emails fr om my iPad with or without attachments. I am a novice!!!!!!

If you purchased about 2 years ago new I am sure it is a Intel iMac. To find out what type of iMac you have just click on the Apple menu item in the finder and select about this Mac. I would check the ISP mail site and get the correct outgoing mail server info.

How to migrate BI Server?

Hello,
I have installed BI server on linux server (A server). Also i have installed Dev Repo database on C Server.
Now i need to migrate this server with all data (answer, dashboard, report) to other linux server (B server).
How can i do it? What is the strategy?
BR,
Eba

Found by self.
Create new repo using rcu (Different prefix DEV1). Installed OBIEE on B server.
And archive all model folder including answers, dashboard, report than unarchive to B Server.
Mr.Happy :-)

Migration from physical server to zone (solaris 10)

Hello all,
I found an old thread about the subject Migrate Solaris 10 Physical Server to Solaris 10 Zone but i have a question.
Using the flarcreare command, will add to the flar archive all the zpools i have in the server?. Right now we have 14 zpools.
If i execute this command "flarcreate -n "Migration File" > -S -R / -x /flash /flash/Migration_File-`date '+%m-%d-%y'`.flar" will take all the zpools?
This is for migrating from a E25k Server to a M9k Server
The E25k (Physical Server) have this release "Solaris 10 10/08 s10s_u6wos_07b SPARC" and the zone server (M9k) have this release "Oracle Solaris 10 8/11 s10s_u10wos_17b SPARC" this could be an issue?
Thanks for any help.
Edited by: 875571 on Dec 9, 2011 7:38 AM

flarcreate will only include data from the root pool (typically called rpool). The odds are that this is what you actually want.
Presumably, on a 25k you would have one pool for storing the OS and perhaps home directories, etc. This is probably from some sort of a disk tray. The other pools are likely SAN-attached and are probably quite large (terabytes, perhaps). It is quite likely that instead of creating a multi-terabyte archive, you would instead want an archive of the root pool (10's to 100's of megabytes) and would use SAN features to make the other pools visible to the M9000.
One thing that you need to do that probably isn't obvious from the documentation is that you will need to add dataset resources to the solaris10 zone's configuration to make the other zpools visible in the solaris10 zone. Assuming that these other pools are on a SAN, the zpools are no longer imported on the 25k, and the SAN is configured to allow the M9000 to access the LUNs, you will do something like the following for each zpool:
# zpool import -N -o zoned=on +poolname+
# zonecfg -z +zonename+ "add dataset; set name=+poolname+; end"In the event that you really do need to copy all of the zpools to the M9000, you can do that as well. However, I would recommend doing that using a procedure like the one described at http://docs.oracle.com/cd/E23824_01/html/821-1448/gbchx.html#gbinz. (zfs send and zfs recv can be used to send incremental streams as well. Thus, you could do the majority of the transfer ahead of time, then do an incremental transfer when you are in your cut-over window.)
If you are going the zfs send | zfs recv route and you want to consolidate the zpools into a single zpool, you can do so, then use dataset aliasing to make the zone still see the data that exists in multiple pools as though nothing changed. See http://docs.oracle.com/cd/E23824_01/html/821-1448/gayov.html#gbbst and http://docs.oracle.com/cd/E23824_01/html/821-1460/z.admin.task-11.html#z.admin.task-12.

Migrating existing portable homes to new server

aside from moving the homedir data from the old server to the new, there seem to be at least a few issues with migrating existing portable home accounts to a new server:
1. some of users' account details, like GeneratedUID, authentication authority, kerberos principals, OriginalNFSHomeDirectory, are different, while others (name, shortname, UID, GID, etc.) remain the same.
2. home directory (OriginalNFSHomeDirectory, etc.) point to the old server.
3. there's data on local machines that we don't sync back to the server, so we can't just blow away the existing local accounts and start fresh.
the quickest way to migrate these users to the new server (with all the same shortnames and UIDs, etc.) seems to be to remove the local cached accounts (leaving the home folders) and have them recreate new PHDs on login, syncing things back down to the original home folder. i'm guess this won't involve much syncing, it's all the same data, essentially.
the other way i can see resolving this is to replace the account attributes for each client to match what they should be when pointed to the new server. this would involve scripting the process for reliability and not moving any data or deleting accounts, but it will take more testing on my part.
what do you think? can you think of better ways to accomplish this task?
summary: what's the best way to move existing portable home accounts bound to "Server A" to "Server B," while maintaining data and portable homes pointed to the new server and storage?
thanks.

that createmobileaccount syntax was wrong. i guess you don't need the -t option and can instead specify the whole path to the user's home. it seems to work well enough, creating a portable home with no default sync settings -- basically manual. for my needs that's fine. the sync settings are managed via mcx anyway.
here's an updated version of the standalone script. i realized just now the script assumes the diradmin usernames and passwords are the same between servers. if that's not the case, you can hard code it or add a couple of variables. since they're just taken in order on stdin, add them in order. i should also add a function to interactively ask for the passwords with stty -echo to avoid having the passes logged in command history or allowing the script to curl the pass from another file on a web server or something. for now, this seems to work for my purposes. edit as you see fit.
#!/bin/bash
# nate@tsp, 3/4/10: initial version
# 3/5/10: added prettier heredoc usage statement, variables, further tested
# todo: add function to add user to local admin group, as needed. this shouldn't be required in most environments.
# todo: convert some of these one-liners to functions for better modular use; make it "smarter"
# todo: convert the whole thing to ruby for practice
# automates the process of unbinding from the old OD server, binding to the new, removing the existing local user, adding it back, and other bits
# there are no "smarts" in this script, so use carefully
# variables
diradminpass=$1
account=$2
password=$3
oldserver=$4
newserver=$5
mkdadmin=$6 # not used in this version
# if no parameters are passed, display usage, exit
if [ ! -n "$5" ] ; then
cat<<endofnote
usage: you must include at least 5 arguments (6th isn't used right now)
run with `basename $0`
1. [directory admin password]
2. [shortname of account to change]
3. [account password, which should be the default 'xxxxxxxx' on the new server]
4. [name of old server]
5. [name of new server]
6. [yes or no to make this account a local admin - optional and not used now]
ex: `basename $0` diradminpass jbrown password oldserver newserver yes
endofnote
exit 1
fi
# if you're running this as root or with sudo, proceed; otherwise, quit it!
if [ $(whoami) = "root" ]; then
echo "you're root. let's proceed..."
# delete the user in question from the local directory store
echo "deleting local account: $account"
dscl . -delete /users/$account
# remove the old od config
echo "removing the old OD bind..."
dsconfigldap -v -r $oldserver -c $HOSTNAME -u diradmin -p $diradminpass
# remove the old server from the search and contacts paths
echo "removing the old search paths..."
dscl /Search -delete / CSPSearchPath /LDAPv3/$oldserver
dscl /Search/Contacts -delete / CSPSearchPath /LDAPv3/$oldserver
# add the new one
echo "adding the new OD bind..."
dsconfigldap -v -f -a $newserver -n $newserver -c $HOSTNAME -u diradmin -p $diradminpass
# create and add the new ldap node to the search policy
echo "adding the new search paths..."
dscl -q localhost -create /Search SearchPolicy dsAttrTypeStandard:CSPSearchPath
dscl -q localhost -merge /Search CSPSearchPath /LDAPv3/$newserver
# create and add the new ldap node for contacts lookups
dscl -q localhost -create /Contact SearchPolicy dsAttrTypeStandard:CSPSearchPath
dscl -q localhost -merge /Contact CSPSearchPath /LDAPv3/$newserver
# give directoryservice a kick to point it to the new server
echo "killing directoryservice and waiting for 20 seconds..."
killall DirectoryService
# rest a bit to ensure everything settled down
sleep 20
# optional: lookup the $account you deleted as the first step to ensure it exists in the new directory
echo "this id lookup should return details because it exists in the new OD:"
id odtestor
echo "this id lookup should fail because it doesn't exist in the old OD:"
id odtestor
# check the search path to ensure it looks like you need
echo "verify the new OD server is in the search path:"
dscl /Search -read / CSPSearchPath
# optional: create a mobile account on the local machine with various options set.
echo "creating a portable home for the user..."
/System/Library/CoreServices/ManagedClient.app/Contents/Resources/createmobileaccount -n $account -v -p $password -h /Users/$account -S -u afp://$newserver/homes/$account
killall DirectoryService
cat<<endofnote
you should be ready to login with this account now.
if you have trouble, revert the process by re-running with the old and new server names
(and diradmin passwords, if they're different) reversed.
endofnote
else
echo "you're not root or an admin. please re-run the script as an admin or via sudo."
exit
fi
exit 0

Migrate existing infracture from Solaries to linux plateform

Hi,
We want to migrate existing infracture from Solaries to linux plateform.
Please suggest me the way.
Our Current Infracture:-
Serve 1 (on Sun Sparc):-
indianDBA-1 (Contain:- Infrastructure database (Meta) 10.1.0.4.2 10G R1, Infrastructure middle tier 10G R2)
Server 2 (on Sun Sparc):-
indianDBA-2 (Contain:- Application Server middle tier 10G R2 10.1.2.0.2)
Server 3 (on Sun Sparc)
indianDBA-3 (Contain:- contains Discoverer report, EUL schema) 11G R2
Thanks
Anup

Hi,
You can use export/import or transportable tablespaces to migrate the database.
10gR2 Transportable Tablespaces Certified for EBS 11i
http://blogs.oracle.com/stevenChan/2010/04/10gr2_xtts_ebs11i.html
Migrating E-Business Suite Release 11i Databases Between Platforms
http://blogs.oracle.com/stevenChan/2008/08/migrating_ebusiness_suite_databases_between_platfo.html
Note: 362205.1 - 10g Release 2 Export/Import Process for Oracle Applications Release 11i
How long the task would take? Depends on the hardware resources you have. The best practice is to try this on a test instance first.
The application should work as expected once the task is completed.
Thanks,
Hussein

Migrating OBIEE Repfrom Oracle database to SQL server database in Solaris.

Hi,
I need inputs in how we would migrate our connections in Repository from Oracle database to SQL server database in Sloaris server.
Is there a complication here.
Regards,
Bhavik

Well that makes more sense, you probably have phrased your question better. Microsoft SQL Server Connectivity Components are not supported in any other operating system than Windows. So you will not be able to use the SQL Server native drivers to connect to your SQL Server. ODBC it's an option but there aren't many ODBC drivers for Unix systems. Luckily for you OBIEE includes the DataDirect ODBC drivers and supports using them to connect to a SQL Server. Check [the documentation|http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/e10416/general_101331.htm#sthref9] on how to use them. Having said that I would say that whoever is pushing to move your DWH to SQL Server should consider also moving OBIEE to a Windows server to be able to use the SQL Server native drivers to connect to SQL Server.
PS: No needs to post 3 times. :-)

Need to transfer/migrate production server from HP-Unix to SuseLinux 11.5

Background : We are having ECC 6.0 running on HP Unix
What we need to do : want to migrate the entire production application to a new server under o/s SuseLinux 11.5 certified by SAP AG
What we are doing : there is a utility called Software Developer Tool DRYRUN using this utility want to export application to storage and from store we shall restore the application into the new server under o/s SuseLinux 11.5
What error I am getting :
Sapinst could not find the required software logistics java libraries DIAGNOSTS. The global directory may not be available at u2018/usr/sap/fpp/flobalu2019 or its contain may not be up-to-date in addition the version of the SAP NetwWeaver java system might be lower than AP6. SOLUTION, Mound the global directory and/or apply the latest support package.
Using above method we could migrate development server to SuseLinux 11.5 successfully.
If I have posted this question on wrong forum pl. guide me
Thanks
Nitin

Hi Nitin,
Just to check with you, OS/DB migrations has to be performed following certain rules. HPUX is big endiand and Linux is little endian so an Heterogeneous system copy should be performed and theres only a few supported ways to perform the migration. Have you check that the usage of DRYRUN is ok and that your system will be supported after the migration?...
Regards
Juan

Migrating an Existing Server Setup to a Raid

I just wanted to pass this by the community in the hopes of avoiding any unexpected results before I embark on this "seemingly" simple project.
I have inherited a small client site that is running Lion server off of a Mac Mini with Dual 500GB drives. The person who originally set this server up opted to split the 2 drives into 2 separate volumes with one volume running OS and data, and the second drive is being used for Time Machine backups of the first drive.
Since I have come on board I am wanting to change this setup and set up a mirrored raid using the 2 internal drives and an external drive for the Time Machine backups. So the question is what is the best way to move forward to accomplish this. Obviously I need to backup the first drive and then reformat the 2 drives into a raid and then restore the server off the back up that I made onto to the new raid. The catch is that I have never done a full server restore. So what is the best way to backup the server and then restore it so as to minimize any headaches?
Should I use something like Carbon Copy Cloner, and if so, would I want to actually create a disk image? Or is it possible to actually restore a full server setup from a Time Machine backup?
Of course another choice would be to remove the first drive from the Mini and replace it with a new drive. Then create the raid and then migrate the server from the first drive that I removed onto the new raid setup. So is there any advantage to migrating vs. restoring?
Thank you.

The cleanest way is to use Disk Utility and create a DMG of the boot volume. Server will be down during this process. Run the scan for restore process once complete. Then create your mirror. Then restore the dmg to the mirror. Do not try to restore from TimeMachine if the systems is an OD master. The sum of the whole will not be equal to the parts.

Need to change snmp string for a solaris server

Hi Everyone ,
i am new to solaris and i need to change a snmp string for solaris server and we need to add this server into the monitoring system.
Please tell me the PKG which need to installed in the client ( solaris box ) .
As of now , i can find these PKGs installed in the machine .
# pkginfo -i |grep -i snmp
system SUNWjsnmp Java SNMP API
system SUNWmibii Solstice Enterprise Agents 1.0.3 SN MP daemon
Do i need to install any package for setting the snmp string and please tell me the configuration file where i need to
change the snmp string file ?
Regards
Chenthil

Hi Bhanu,
I am fine, thanks. Hope you are fine too.
will this step not required
$sqlplus apps/appspass
SQL>exec fnd_conc_clone.setup_clean
before running autoconfig?If you have the latest AutoConfig patch applied, then I believe it is not required. However, it should be OK to run this command to purge FND_NODES table before running AutoConfig.
Regards,
Hussein

Methods for migrating existing servers to new hardware

I have 10 Solaris 8 and 9 boxes (SF4800 and V480). We are moving these to new hardware (V490 and V440).
All have mirrored boot disks, some using VxVM and some using SDS. All are connected to SAN storage (Sun 3900 and EMC).
I am looking for the easiest, simplest and least risky method to migrate.
Possible methods:
1) Pull boot disk from existing server, move to new server. Issues: drive compatibility between old and new servers.
2) Flasharchive to NFS server, install new servers from flash image. Issues: SDS/VxVM encapsulation?, old server Solaris versions do not support new server hardware.
3) Break boot disk mirrors, Live upgrade to latest Solaris 9 on this disk, then Flasharchive this image to NFS server. Issues: none that I can think of.
Any input/ideas are appreciated.

Hi,
I am not an expert in Portal Migrations but I would suggest you to do a homogenous system copy, then restore it on SLES10 32-bit and then migrate it to 64 bit. But you need to do a fair amount of homework before you carry out this exercise.
Even if you are not touching the database, I would suggest going for a homogenous system copy. The reason being, there are some database related files stored on Portal server and whenever you restart the Portal server, it's gonna check the timestamps there with the ones available on DB. We ran with a problem once doing the same. We were using Oracle then.
Secondly, before taking a decision to move over to 64-bit, I would suggest you to check the PAM and have a look whether all the portal components are supported or not. We had a problem with HP-IA64 bit because we finally found out that it doesn't support Adobe Document Services. So things like these need to be thought over and confirmed before stepping forward.
Hope this helps.
Cheers,
Sunil
PS: Reward points for helpful answers.

Mirroring Windows Server to a Solaris Server using filesync & NFS

I am trying to mirror the data from a Windows 2000 server to a Solaris 10 server using filesync over NFS. I have been able to do this from one solaris/sparc machine to another without problems, but this heterogeneous sync is failing. The Windoze machine is running Hummingbird NFS Maestro Server. I've tried both an old version of Maestro (5.x) and the newest version. On the solaris machine, I craft the .packingrules file by hand and issue "filesync -o src" to copy from the nfs mounted source to a local directory. The initial copy seems to go well, albeit with numerous complaints about ownership and permissions. On either the second or third running of "filesync -o src", it wants to delete all of the files that it just wrote. Argh! Sometimes it works, sometimes it does not.
Perhaps I need to mirror in some other way. If all else fails, next I'll compile rsync on the solaris machine, trying it over NFS.
I'd appreciate any suggestions of how best to mirror.
By the way, my goal here is to show to Windoze PC users that this Solaris server can do everything that the Windows server can do, and more. With hopes, I'll be able to migrate completely off of the Windoze server.
Thanks

smbmount doesnt exist for solaris 10.
The functionality would require a smbfs kernel module which is not available in solaris 10.
I think there might be a commercial product that provides this functionality, but its name escapes me at the moment..

Best Practice to migrate existing Message/Central Instance to new hardware?

I've done some searching for this, but it all seems to be fairly old (I found one decent thread from 2008, but it just seemed outdated). I would like to get some updated info & suggestions on a process to follow for this task.
Here is some info about the current config:
I have an existing SAP ERP 6.0 EHP5 system. SID "XYZ"
Everything is currently running on Windows x64.
ABAP only config.
It is currently setup as a distributed system.
DB server is SQL, which is running on its own hardware as a dedicated DB server. I don't need to touch this.
Uses logon groups to distribute the load between 3 App servers.
One of the App Servers is setup as the Message/CI server. This is what I am wanting to move to VM hardware.
The other two App Servers are setup just as Dialog Instances. VM already. I don't need to touch these.
What I am wanting to do:
I am wanting to migrate the existing Message/CI server to VM hardware to get the current Message/CI system off of very old hardware.
I need to keep the system with the same name & IP.
I do not need/want to mess with the DB server at all.
Need to minimize downtime as much as possible.
I do NOT want to go to an HA environment. That is a different project for the future.
Suggestions? I would like to hear what some of you have done.
Minimize downtime? I have a short maintenance window of a few hours coming up in the next few months, and would like to do this changeover during that downtime.
How do I handle setting this up on the new hardware using the same name & IP, especially with the existing system still running.
What I think I need to do: (Some of these may be out of order, which is why I'm asking for suggestions)
Setup new Windows VM server, named differently than current Message/CI server (Done already).
Run SAPINST to run Global Host Preparation on the new Windows VM server.
Run SAPINST to setup ASCS Instance on the new Windows VM server.
Skip the Database Instance installation, since I already have one running.
Run SAPINST to setup Central Instance on the new Windows VM server.
Copy all of the appropriate profile parameters that were on the old server.
Start SAP and make sure everything is running and working correctly.
Copy all job, spool files, etc. from the old server.
What needs to be done in between those steps for the server rename & IP changes?
Which of these steps can I do in advance of my maintenance downtime window, without it affecting the currently running system?
I have a test environment that I am going to test this with. I'm just trying to get a jump start on my instructions, so that I can hopefully do this quickly and easily. I'm very comfortable doing the installs. Just needing some guidance on how to handle this case.
I'm open to suggestions, and any links you can send my way that show some more recent success at doing this. Everything I keep finding talks about doing the migration for the DB. I am not migrating my DB. It is staying where it is. I'm just wanting to migrate my Message/Central Instance to a VM, without affecting the users, and hopefully them never noticing the changes.
Thanks!

If you're using VMWare, there is a tool provided to virtualize existing systems. Basically it makes a copy of the old system (while it is down) and recreates it as a VM with the same name, IP, etc. I haven't double-checked to see if this process is 'officially' supported by SAP, and I don't know the technical details about how it's done or how long it will take (VMWare is managed by the Network Operations group in my team, so as the SAP sysadmin I'm basically a customer of theirs). However, we have virtualized a few smaller systems that needed to get off failing hardware in a hurry and it worked very well, so I would expect it would for an SAP dialog instance as well. As you're not copying a database, just the app server, it probably would fit within your maintenance window.
If this route works for you, then there is no need to actually install the SAP system on the VM instance... you just copy the old server as-is, then make any adjustments required due to no longer needing old drivers, etc, plus potentially having different memory parameters.

How to migrate File server to NAS device?

All right so here's the scenario.
An external forest level trust is setup between two forests A & B as recently as we acquired the company B.
Users from forest B were already migrated to domain A.
Now I need to migrate file server from domain B to my domain A but the target where we need to move file shares is a NAS device, so basically we cannot do a simple server migration from domain B to domain A.
We need to copy over the data+ACL+Share permissions from fileserver in domain B to a NAS device in domain A whereas of course ACL permissions on file server present in domain B will obviously be as per source domain user accounts, example ACL permissions
currently will show as "B\user1".
So whats the best way to perform this in order to maintain the permissions & data.
Another question how do we copy share permissions from file server to NAS as I can robocopy the data with security permissions but how to copy over all the share permissions to destination NAS?

Hi,
You need to retain the SID History attribute when users across domains to ensure users in the target domain can access to files during migration.
For more detailed information, please refer to the threads below:
ACL migration
http://social.technet.microsoft.com/Forums/exchange/en-US/3c75a116-6bd3-407f-a76c-0d825d4f525a/acl-migration
File server migration using FSMT 1.2 in NAS environment
http://social.technet.microsoft.com/Forums/en-US/fb4bf505-2d95-4409-9777-8fd4a1c0c471/file-server-migration-using-fsmt-12-in-nas-environment?forum=winserverfiles
In additional, you could backup registry key SYSTEM\CurrentControlSet\Services\LanmanServer\Shares to copy share permissions.
Saving and restoring existing Windows shares
http://support.microsoft.com/kb/125996
ADMT and network mapped drives
http://social.technet.microsoft.com/Forums/windowsserver/en-US/9752e31d-2f35-4d7d-ae4d-2f9fe9400bfe/admt-and-network-mapped-drives?forum=winserverDS
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

OS migration - Existing server is on Solaris need to change to Suse Linux

Similar Messages

Maybe you are looking for