EP 6 SP15 migration to new hardware

Is there any documents for Portal migration 6 SP15 from HP oracle to AIX oralce ? Did anyone perform this yet ? Please let me know.

Hi Jitendra,
you have to do a Java Migration. Please read the System copy manuals.
Regards,
Benny

Similar Messages

SQL cluster 2008 R2 migration to new Hardware in VM

Hi,
We have a task to migrate existing Physical SQL Cluster DB to new Hardware but in VM. (cannot argue with the client)
hence our plan is to install new Cluster in VM with same Windows and SQL version i.e Win 2K8 R2 ENT w/SP and SQL 2K8
R2 STD w/SP and use SQL mirroring option for the DB to migrate on the new Server (keeping the downtime to as low as possible and advantage of bringing the old server online in case of any issues..)
Below points are for a single instance, couple of DB to migrate:
Keep the physical production server running
In-Parallel build New SQL Cluster in VM (keep same version windows/sql)
Keep Same drive letter for Quorum, MSDTC, DATA, LOG & Backup
Keep the same Instance Name, SQL Network Name can be different (will be changed to old network name once the PROD is shutdown)
Check all logins windows and SQL to be same on both the clusters
Copy all the jobs, SSIS packages etc.. .create the location folder as per current server on the VM SQL Cluster
Perform full backup of old cluster company-db databases or use the existing latest backup (full, differential, transaction)
Restore databases in the new cluster with no recovery so additional log file or differential backup can be restored
Create SQL Mirroring for the Database and select the principal server (old cluster) and the mirror server (new VM cluster)
Choose mirroring without witness ( no auto failover as we don’t need the old server later)
Start the mirroring – (hopefully everything synchronized and working)
During the downtime –
Stop the application/ client connection – if possible
Failover the DB through Mirroring option
Once the mirrored server becomes Principal and data is accessible – stop the mirroring
Now the new VM SQL Cluster DB is online
Shutdown the old cluster company-db (Node1 & Node2)
Come back to VM SQL Cluster and change the Network name to the old server network name (so that client connections are not affected)
Check if the DNS entries are updated with correct name and IP address
Delete DNS entries for old company-db on DNS Servers if not deleted, delete the old server SQL network name in computer object
Stop SQL Resources on the new VM SQL Cluster (take it offline all the resources)
Bring online the SQL Resource and make sure the SQL resources are online and new network name is reachable
Wait till you see machine name company-db in active directly (AD) and DNS server will have entry for company-db
Verify connectivity for company-db from outside.
If things are not going as per the plan then shut down the new VM cluster
Revert back the DNS settings
Power up the Old SQL Server
The DB will show “restoring mode” – use command to make it online “RESTORE DATABASE (dbname) WITH RECOVERY”
Check the DB
Start using the OLD server again
Troubleshoot the failed scenario ;)
Need to know if the above steps are okay, and any consideration once the new VM SQL Cluster is online.
Kindly let me know if there anything else to transfer apart from the logins, jobs, folder location etc.. !!
Many Thanks

Hello,
Well if you don’t change the instance name (name = ABC) then its OK.
Try the following resources about transferring SQL Server logins:
http://support.microsoft.com/kb/918992/en-us
http://www.mssqltips.com/sqlservertip/2081/transfer-sql-server-jobs-task-and-transfer-sql-server-logins-task-in-ssis/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SBS 2008 - SBS Console and AD errors after migration to new hardware

Hi there,
I'm trying to work out how to fix some of the errors and random behaviour I'm experiencing with the SBS 2008 console and AD related matters since I had to quickly migrate SBS 2008 to new hardware using Windows Server Backup after a failure of the old server.
In my haste to get our email and ftp services back up and running (which use Smartermail and Filezilla respectively instead of Exchange etc) I overlooked the fact that the new server had 3 NICs installed and not one and so restored SBS 2008 and loaded up new
drivers for those and other hardware that had changed (such as the graphics card and mobo. I have since removed the two additional NICs by disabling them on the mobo).
Whilst I got the server up and running again with email and ftp services, even though I currently don't use any AD related stuff directly I have since noted that if I try to say view a list of users that I had previously created via the SBS console, more often
than not it will show no users, and then randomly it will (but when you do see them you can't edit or delete them. I'm aware that I have probably broken a number of golden rules in doing this 'migration' but having a metaphorical gun to my head meant that
I rushed things out of desperation.
Common errors that I experience generally will say things like 'Current security connect is not associated with an Active Directory domain or forest' if I try to list users, or DC not found for domain "xyz.local' etc. I have been searching the net and
trying out some things to fix this but I'm like a dog chasing its tail as I'm not so clued up on server related issues as I am with workstation problems, so if anyone could at least point me in the right direction I would be very grateful. If you require any
info from me (eg diag logs etc) I will be happy to provide them!
Regards,
Dave

Hi Dave,
Based on current situation, please run SBS BPA and fix all that it can find, then monitor the result. For more details, please refer to the following KB.
Windows SBS Best Practices Analyzer (BPA)
Meanwhile, please refer to the following article and repair SBS console.
Repair the Windows SBS 2008 Console
By the way, I noticed that you had got some error messages (such as: “DC not found for domain” and so on). Would you please let me know complete error messages? In addition, when you migrate SBS 2008 to the new hardware, had you done any preparation for
that Source Server? For more details, please refer to the following article.
Migrate Windows Small Business Server 2008 to New Hardware
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Best practice for migration to new hardware

Hi,
We are commissioning new hardware for our Web Server. Our current webserver is version 6.1SP4, and for the new server we've decided to stay with 6.1 but install SP7.
Is there a best practice for migrating content from one physical server to another?
What configuration files should I watch out for?
Hopefully the jump from SP4 to SP7 won't cause too many problems.
Thanks,
John

unfortunately, there is no quick solution for migrating from 1 server to other. you will need to carefully reconstruct
- acl rules
- server hostname configurations
- any certificates that have been created on the old machine

9i migration to new hardware

does anyone know of a migration guide for moving a 9i database to new hardware?

Other than
1) install new hardware,
2) install Oracle, preferrably 10gR2 since 9i is in extended (expensive) support
3) export/import OR (if same hardware platform and OS and DB version) copy database (all files) and configure tns files.
I don't know of a guide, per se. And I could not give details unless you decided to give details.

Exchange 2003 /2010 Co-existence plus 2010 migration to new hardware

Hi,
Here is our current scenario;
Exchange 2003/2010 co-existence. This has been running perfectly for a couple of months now.
Exchange 2003 - exch1.domain.lan
Exchange 2010 (SP3) - exch2.domain.lan (local domain name) / mail.domain.com.au (external domain name)
ActiveSync, autodiscover, legacy etc are all working. Our UAC certificate from GoDaddy has all the required names for exch2 - except it doesn't have the local domain name as they don't allow certificates with that anymore. I've configured all the required
services to be the external domain name and am running split DNS.
The first Exchange 2010 server I installed was lower spec'd and only has about 25 users on it. I now need to install a second Exchange 2010 server (exch3.domain.local), which is properly spec'd and will host the entire company. I won't be running DAG as
I need to repurpose the first Exchange 2010 server once it's removed.
My high level questions are;
1) Should I migrate everyone off Exchange 2003 onto Exchange 2010, decommission the 2003 server, and then install the second 2010 server? OR
2) Should I install the second Exchange 2010 server, migrate everyone from the first Exchange 2010 server, decommission that one, then do the migration from 2003 to 2010?
OR does it matter which way I do it?
I've read what I can find about installing the second Exchange 2010 server into the organisation. It seems to be pretty simple at first. Just install Exchange 2010 with HT, mailbox and CAS roles which will automatically configure it into the same Exchange
organisation.
1) Do I configure CAS to be externally facing right from the get go or do I do that later?
2) As soon as I install the second Exchange 2010 server, will I encounter any mail flow problems? Will mail be trying to flow out of the second Exchange 2010 server as well as the first?
In regards to SSL, so obviously the second Exchange 2010 server will have a different local domain name than the first, but ultimately, I want it to have the same external domain name, eg mail.domain.com.au. As my certificate doesn't contain any local domain
names, can I export the certificate from exch1 and import it into exch2, or should I just generate a new CSR from exch2 and get GoDaddy to reissue it?
OR should I look at creating a CAS Array from exch1 and adding exch2 to it. (I don't fully understand the workings of this at the moment).
Any guidance on the above is helpful.
Thanks.
Steve

Hi Steve I will try my best to answer each of these
My high level questions are;
1) Should I migrate everyone off Exchange 2003 onto Exchange 2010, decommission the 2003 server, and then install the second 2010 server? OR
2) Should I install the second Exchange 2010 server, migrate everyone from the first Exchange 2010 server, decommission that one, then do the migration from 2003 to 2010?
OR does it matter which way I do it?
doesn't matter at all. Since you want to move to a new hardware you can setup a new Server CASH/HUB/Mailbox. Once installed start migrating the mailboxes from Exchange 2003 to this mailbox server. This way you will not have to redo the migration from 2010
to new 2010 sever -- like you mentioned in 1) it will save you a lot of time and repeating procedure.
I've read what I can find about installing the second Exchange 2010 server into the organisation. It seems to be pretty simple at first. Just install Exchange 2010 with HT, mailbox and CAS roles which will automatically configure it into the same Exchange organisation.
1) Do I configure CAS to be externally facing right from the get go or do I do that later?
Keep your existing 2010 internet facing for now. Once you finished migrating the mailboxes then you will need to do it.
2) As soon as I install the second Exchange 2010 server, will I encounter any mail flow problems? Will mail be trying to flow out of the second Exchange 2010 server as well as the first?
Mail will not flow to 2ndry server unless you add that server as a source serve in the transport.
In regards to SSL, so obviously the second Exchange 2010 server will have a different local domain name than the first, but ultimately, I want it to have the same external domain name, eg mail.domain.com.au. As my certificate doesn't contain any local domain
names, can I export the certificate from exch1 and import it into exch2, or should I just generate a new CSR from exch2 and get GoDaddy to reissue it?
You can always export the certificate and then import it to the newly installed Exchange 2010.
OR should I look at creating a CAS Array from exch1 and adding exch2 to it. (I don't fully understand the workings of this at the moment).
You will only need to setup the CAS array if you are going to use both the server which can be done later.
Hope that help
Where Technology Meets Talent

Migrating to new hardware using maintenance Mac OSX Server

Hi,
I'm in the process of migrating a G4 Xserver to a G5 Xserve. The older G4 is running 10.3.9 and the newer G5 will be running Mac OS server 10.4.7.
We have a maintenance agreement with Apple, so I want to migrate from our 10.3.9 server license to the 10.4.7 server license - but it's the same 'license' and when I install it on the new hardware, Server Admin/Overview tells me that it's License Type is "0-client license". Also the Serial number fields format in Server Admin/Settings is clearly different from the documentation that came with the maintenance copy of the server software:
Server format;
x-xxx-xxx-xxx-xxx-xxx-xxx-xxx-xxx-xxx-x
Documentation License;
xxxx-xxx-xxx-x-xxx-xxx-xxx-xxx-xxx-xxx-x
So my question is
How do I migrate from one server to another using the same license while minimizing downtime for this production system?

I would say that Apple should be able to update your 36-months maintenance agreement with a OSXS 10.4 serial number.
As far as I know, the structure of 10.3 and 10.4 serial numbers is different (wasn't the case between 10.2 and 10.3) so I'm short of a technical answer here.
Maybe you could try :
/System/Library/ServerSetup/serversetup -setServerSerialNumber xxxx-xxx-xxx-x-xxx-xxx-xxx-xxx-xxx-xxx-x
in a Terminal window on the server. It's theorically the same as using Server Admin but maybe this could help.

Using the OES migrations for new hardware

I need to change my hardware, is it possible to use the migration tool to change from one hardware with OES linux to a new hardware with also OES linux just as we did from Netware to Netware ?

Thanks, that was the information I was looking for, I had migrated this hardware from Netware to Linux, now I needed to change the hardware and migrate from OES linux to OES linux
Originally Posted by Marcel_Cox
Yes, but you need to use the migration tool provided with OES2/Linux, not the "old" NetWare migration tool.
The conditions are:
- the destination server must be running OES2SP1 or later (OES2SP2 fully patched is very highly recommended because otherwise you may have trouble because of bugs in the migration tool)
- the destination server must be installed with the premigration pattern as well as with all services you want to migrate
- the "temporay" installation is done into the main tree, not into a temp tree like for NetWare migrations
- you run the migration GUI tool from the destination server. There is no workstation involved
Apart from these main recommendations, follow the documentation of the migration tool found here:
Novell Doc: OES 2 SP2: Migration Tool Administration Guide - OES 2 SP2: Migration Tool Administration Guide

Migrate to new Hardware ( RAC-2-RAC )

Dear all
We have a 4 node oracle 10g R2 RAC and want to migrate to new machines with database size of 2 Terabytes. We took a backup and restore it on the new machines and everything is ok. However, we planned to migrate in a week and I don't want to restore the whole database again. What concerns me is I have to open the database at the destination with resetlogs option.
My question is : What is the best way to keep the migration downtime minimum ? I want to restore a level 1 incremental only.
Thank you
Kamy

Hi Kamy,
I will skip the backup part and restore controlfile part of you question I think you know how to do it.
If you copy your backup pieces to the new system you can use them to perform a restore/recovery (but do not open the database) in mount phase:
<
SET UNTIL TIME "TO_DATE('define_time','yyyy-mm-dd:hh24:mi:ss')";
restore database;
recover database;
>
For the next recovery step you can copy the newly created archivelogs (or the pieces containing the archivelogs) to the new system and apply them with
<
SET UNTIL TIME "TO_DATE('define_time','yyyy-mm-dd:hh24:mi:ss')";
recover database;
>
Regards,
Tycho

WCS Migration to new Hardware

I'm trying to find some documentation on how to migrate a WCS install from one server to another. I can't seem to find any documentation on this process. Does anyone have any documentation or a quick procedure for this?

That may not do it entirely. From the software install perspective I believe it is valid but I recall seeing another thread on this subject referencing having to take some additional steps to move your license file to the new server name.
I suppose if you happened to use the same server name then this may have just worked out for you but in case you may not have this may still be an open item for you.
And it is possible there could be other gotchas with this process.

NW04S Java - Distributed System. DB Instance migration to new hardware.

Hi, I have a distributed NW04S Java only system. CI and CSC on Host A and DB on host B.
1.We want to move the DB instance from Host B to Host C. We will move the database from B to C using Oracle methods. What are the steps that need to be done on the CI/SCS instances/Host A to make the application connect to the DB on host C instead of B.
2. The new DB host is actually a node of 2 node MSCS setup. How can we enable clustering for the DB instance alone and still make the CI?SCS connect to the clustered DB?
For unavoidable reasons we do not want to follow the sapinst/jload system copy method.
Any directions, higly appreciated.
Thanks-Gopalan

Hi, I ve managed to get this working.
3 simple steps
1. Change db host entries in the Default profile
2. Change tnsnames.ora to new DB host in usr..\profile\oracle\ in the App Host.
3. Change host name in secure store on app server using config tool.
Thanks
Gopalan

Documentation Required: Migrate uPerform to New Hardware

Hi All,
I am currently looking at what it would take to migrate the uPerform server to updated hardware that is still in compliance with the recommended specifications. So far I haven't found anything helpful in OSS notes or other documentation from the SAP support side. I did find what appears would help me on Ancile's support portal but the site requires login credentials: Online Guide to Moving uPerform Databases in Microsoft SQL in uPerform 4.30 or Higher .
Can anyone provide information on where to find any SAP documentation on hardware migration activities for uPerform? Can the software just be installed on the new target and databases restored from the source application server, or are other flat files etc. required? Any document or input would be appreciated.
Thank you!

Thank you, I have opened an incident as directed. Additionally, I would still be interested for any info or issues encountered from others who migrated to new hardware.
Thank you.

Migrate to New Server

OES 11 SP2 on an older PE2850 that does not support virtualization!! This existing OES 11 install runs eDir, iFolder, LUM, and imanager (all installed from the disc). We need to migrate off the existing server, replace it with a new server and then migrate back to new server. Can someone point me to a document or instructions on how to do this?

Originally Posted by mrosen
Willem,
Am 14.03.2015 um 22:36 schrieb magic31:
>
> Hi,
>
> carnold6;2349684 Wrote:
>> ...This existing OES 11 install runs eDir, iFolder, LUM, and imanager
>> (all installed from the disc). We need to migrate off the existing
>> server, replace it with a new server and then migrate back to new
>> server.
>
> I'm curious why you are needing to do this (as you are already running
> OES 11 and you want to migrate back)?
Yeah, good question. I understand heneeds to migrate to new hardware,
but why back and forth is a good question. I wonder if there's a SAN
involved which could make it allso much easier..
Yes, need to migrate to new hardware (server) as our current poweredge CPU's do not support virtualization and as i understand it, you can not upgrade from non-virtualization CPU's to CPU's that support virtualization on this poweredge. The reason i say back and forth is because we do not have the new hardware yet. We do have a system that we can virtualize SLES11 on while waiting for the funds and waiting for the new hardware to get here.

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.

Migration from 7.0.2-10000 to 9.1.1 with new Hardware

Hello,
a customer from us wants to upgrade from Version 7.0.2-10000 to the new CUCM 9.1.1.
I know that we have to use new hardware.
My plan is the following:
- Update all needed phone firmware to the latest in 7.0.2
- Install the patch ciscocm.refresh_upgrade_v1.1.cop.sgn
- Install Version 9.1.1 on the old hardware
- Take a backup from the installed 9.1.1 on the old hardware
- Install the 9.1.1 on the new hardware
- Restore the taken Backup from the old hardware with the new Version
- Do the licensing stuff
- Great all things are running...
Can someone apply this way to migrate??
Thanks a lot...
Christian

If you want to avoid the phone FW upgrade after going to 9.1.1, upgrade to the same loads on your current version so you can control the upgrade process and do it with small groups of phones at a time.
Other than that,if your MCS supports the target version, you're good to go with that plan.
HTH
java
if this helps, please rate
www.cisco.com/go/pdihelpdesk

EP 6 SP15 migration to new hardware

Similar Messages

Maybe you are looking for