Migrate Sun Cluster (+RACdisks to new hardware running Sun Cluster ( + RAC)

Hello,
We have old hardware (v490s) running Sun Cluster 3.2 + Oracle RAC 10.2.0.4.0 connected to SAN. We need to move to T4. Oracle advised against including new hardware into existing cluster, so we are planning on building a new cluster with T4's, same software (Solaris 10, Sun Cluster 3.2, RAC 10.2.0.4.0).
When ready, we plan to shut down existing cluster, zone new cluster to existing disks and bring up everything on new hardware (simply stated).
Will it work?
Any gotchas - like need to clear disk ids or Sun Cluster panicking? RAC panicking? Any reference docs out there?
Thanks
user12961096

Do we absolutely need that in our new setup or could we forgo that additional layer? Would Sun Cluster give us anything that the OS + RAC doesn't give us?Yes, Oracle Solaris Cluster does make things a lot easier. It looks after your device space and gives you consistent DID devices for CRS/RAC. It gives you the choice to use sQFS, raw metasets, or ASM. It has clprivnet which is a lot easier and performs better than an IPMP solution. The node failure detection time is <= 10 seconds which is quicker than CRS on it's own and it uses SCSI fencing instead of a STONITH approach. Finally, you have all the off the shelf agents that Solaris Cluster offers.
However, if you are only doing RAC and you just want ASM and you don't need the last few seconds of failure detection that OSC gives you and you think STONITH is good enough for your fencing purposes, then CRS on its own is perfect. There are many, many deployments both with and without OSC, it's not a simple yes/no answer.
Having worked for the Solaris Cluster group, I'm still slightly bias to including it rather than going without. Others have the alternate view! :-)
Hope that helps,
Tim
---

Similar Messages

Move / Migrate A Managment Server to New Hardware

I want to move / migrate my existing SCOM 2012 SP1 Management Servers to new hardware running Server 2012 R2. We're going to leave the DBs where they are for now.
It looks like I could just 'add' a new Management Server and then remove the older ones. Is it that simple?
Orange County District Attorney

HI,
1. Install a new Management server in your management group.
2, Move all SCOM agents from old MS to new management server.
3. Move if there is any dependencyes on old MS to new MS (Like Exchange corelation engine serivce on MS for Exchange 2010 MP / Proxying for web application monitoring/ SMTP relay for SCOM email notification etc)
4. properly uninstall Old MS to avoid issues (if not objects will left in resource pools)
Kind Regards,
~Bommi

How to migrate os x server to new hardware

I am looking for the quickest easiest way to migrate OS X server to new hardware that I purchased. I currently have both DHCP and DNS services actively running. I have VPN services running when needed.

Reid,
Thanks for your response. I actually migrated everything that I needed over about an hour after I posted. For DNS I simply copied all of the zone files in /Library/Server/named and restarted the DNS service. DHCP took a little more investigation as I had to find where the configuration file was being stored. I eventually found the configuration in /etc/bootpd.plist file that contains all of the DHCP info and copied it over to the new system. Once I restarted all services everything was working fine.
I took this approach rather than a direct cloning as I wanted a clean install of everything on the target system. Also, as I mentioned before, I didn't have many services running that I needed to have running on the new configuration. The VPN services that I was running had only one test user so recreating it from scratch was a non-issue.
Regards,
André

Mail "unexpectedly quits" after migration from snow leopard to new iMac running Mountain Lion

Mail "unexpectedly quits" after migration from snow leopard time machine files to new iMac running Mountain Lion. I can run connection doctor OK. But the activity window is blank. If you try to open message viewer window then mail program crashes. Would really like to get my old emails back as the old imac is totally dead. Thanks for any help.

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Step 1
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.
Enter the name of the crashed application or process in the Filter text field. Post the messages from the time of the last crash, if any — the text, please, not a screenshot.
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into a message.
Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.
Step 2
Still in the Console window, look under User Diagnostic Reports for crash reports related to the process. The report name starts with the name of the crashed process, and ends with ".crash". Select the most recent report and post the entire contents — again, the text, not a screenshot. In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.) Please don’t post shutdownStall, spin, or hang logs — they're very long and not helpful.

Migrating OS X install to new hardware?

I've just gotten a Mac Pro to replace my Mac Mini. Is there a supported method of moving an OS X installation onto new hardware rather then having to reinstall and reconfigure all my software and settings?

When you turn on your Macbook Pro it will ask you if you own another Mac and it will start the migration either over the network or via FW as the MB Pro still has this port.
If you are already set up then go to your HD>applications>utilities and then migration assistant

Migration of BW system to New Hardware and Upgrade to NW04s

Hi,
I'm not sure this is the forum for this post but here goes...
We have recently started a project to migrate our current BW3.5 system to new hardware (HP Superdome) and then upgrade to NetWeaver 2004s.
To do this, we've taken a copy of our current Dev 3.5 system and moved it to the new hardware and will unicode and upgrade to NW04s. Once this is complete, we plan to install NEW instances of QA and Prod with NW04s. We will TRANSPORT all our configuration and reload all the providers in QA and Prod. This will be a MASSIVE task as we have hundreds of infoproviders. Additionally, I'm concerned we will not pick objects currently in 3.5 Prod system (e.g. custom queries/workbooks, infopkgs, process chains, variables, etc.) but not in current 3.5 Dev system.
My question is this - can we instead take copies of the current QA and Prod (3.5) systems and migrate, unicode, and upgrade in the new Superdome hardware. Per Basis, this is NOT possible due to the size of the current systems - approx 2.5 Terabytes. But maybe half of the database is consumed by old PSA's, unused providers, etc. If we were to clean up our current system and do a database reorg to reduce the database size, is it possible to do a system copy (Dev to Dev, QA to QA, Prod to Prod) --> any help/insight is much appreciated.
Thanks,
Senthil

I had this experience in my previous project and i wanna share a with you. we have migrated our total bw landscape from alfa servers to HP superdome servers.
we took all the copies of all the boxes( dev,QA,PRO) and migrate to superdome and upgrade to NW04. but in your case you are not taking copies QA and PRODUCTION. This is not realistic scenario. you got to move all the objects and configuration from dev to respective systems and load the data in the production.
so you have to take all the copies of all the boxes and migrate to superdome and upgrage to NE04, is the right way of doing.

Migrate (N)AMP server to new hardware

Hi,
I have been looking for documentation on how to move an AMP configuration to
new hardware (practically same OS-install, NW65SP7).
Is there any info around 'cause I wasn't able to find any. And before I
start dumping MySQL databases and Apache virtual hosts, I thought i'd ask
here.
On the origin server, webcontent and SQL db are placed on different volumes
than SYS. I looked at MigrationWizard as well, but my replacement server is
already in the same tree (new name).
Any info, links or directions, appreciated.
Regards,
Marcel

BakxM,
> I have been looking for documentation on how to move an AMP configuration to
> new hardware (practically same OS-install, NW65SP7).
I'd transfer the database and adjust Apache and PHP settings manually.
- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)
Discover the new Novell forums at http://forums.novell.com
Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

Migrating SBS Starter Pack to new hardware

I have searched the entire forum and knowledgebase for an answer to this
and haven't found one. I have a very small business client (2 users)
that is currently using SBS 6.5 Starter Pack. I have convinced them to
upgrade to better hardware from a clone tower. My question is can I
migrate the starter pack server without affecting the activation that is
already in place? Or will I have to reactivate after the move? If
reactivation is necessary, can that even still be done since the starter
pack has been discontinued?

This is NOT a Microsoft Server so you should be
able to just take the Hard disk out of the old box and put in the new box
(done this zillions of times!)
BUT, to play it safe...
Put in a 2nd hard disk and make a dos partition
format with /s and xcopy the dos partition
Load NSSMU and Mirror the sys and data and any other
When complete - You have a COPY to put into the new server !
<[email protected]> wrote in message
news:RlYZg.16355$[email protected]..
>I have searched the entire forum and knowledgebase for an answer to this
> and haven't found one. I have a very small business client (2 users)
> that is currently using SBS 6.5 Starter Pack. I have convinced them to
> upgrade to better hardware from a clone tower. My question is can I
> migrate the starter pack server without affecting the activation that is
> already in place? Or will I have to reactivate after the move? If
> reactivation is necessary, can that even still be done since the starter
> pack has been discontinued?

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

Migrating 10g disco to new linux server(new hardware)

We are planing to migrate 10g discoverer applications to new hardware with same OS,
source os: OEL4.7 and target OS: 4.7(with new hardware), how to make it...?
EBS : 11.5.10.2 with 11g R2 DB .
any references notes or links appreciate it.

any references notes or links appreciate it.10 Cloning Application Server Middle-Tier Instances
http://docs.oracle.com/cd/B14099_19/core.1012/b13995/cloning.htm
Thanks,
Hussein

When deploying a single server on new hardware, do you virtualize it or not?

There are a few questions that I've found on ServerFault that hint around this topic, and while it may be somewhat opinion-based, I think it can fall into that "good subjective" category based on the below:
Constructive subjective questions:
* tend to have long, not short, answers
* have a constructive, fair, and impartial tone
* invite sharing experiences over opinions
* insist that opinion be backed up with facts and references
* are more than just mindless social fun
So that out of the way.
I'm helping out a fellow sysadmin that is replacing an older physical server running Windows 2003 and he's looking to not only replace the hardware but "upgrade" to 2012 R2 in the process.
In our discussions about his replacement hardware, we discussed the possibility of him installing ESXi and then making the 2012 "server" a VM and migrating the old apps/files/roles from the 2003 server to the VM instead of to a non-VM
install on the new hardware.
He doesn't perceive any time in the next few years the need to move anything else to a VM or create additional VMs, so in the end this will either be new hardware running a normal install or new hardware running a single VM on ESXi.
My own experience would lean towards a VM still, there isn't a truly compelling reason to do so other than possibilities that may arise to create additional VMs. But there is the additional overhead and management aspect of the hypervisor now, albeit
I have experienced better management capabilities and reporting capabilities with a VM.
So with the premise of hoping this can stay in the "good subjective" category to help others in the future,what
experiences/facts/references/constructive answers do you have to help support either outcome (virtualizing or not a single "server")?

In the general case, the advantage of putting a standalone server on a hypervisor is future-proofing. It makes future expansion or upgrades much easier, much faster, and as a result, cheaper. The primary drawback is additional complexity and cost (not necessarily
financially, but from a man-hours and time perspective).
So, to come to a decision, I ask myself three questions (and usually prefer to put the server on a hypervisor, for what it's worth).
How big is the added cost of the hypervisor?
Financially, it's usually minimal or non-existent.
Both VMware and Microsoft have licensing options that allow you to run a host and a single guest for free, and this is sufficient for most standalone servers, exceptions generally being servers that are especially resource-intensive.
From a management and resource standpoint, determining cost can be a bit trickier.
You basically double the cost of maintaining the system, because now you have two systems to monitor, manage and keep up-to-date with patches and updates (the guest OS and the host OS).
For most uses, this is not a big deal, as it's not terribly taxing to maintain one server, though for some especially small or especially technically challenged organizations, this can be a real concern.
You also add to the technical skills required. Now, instead of just needing someone who can download updates from Windows Update, you need someone who knows enough to manage and maintain the virtualization environment.
Again, not usually a problem, but sometimes, it's more than an organization can handle.
How big is the benefit from ease-of upgrade or expansion?
This boils down to how likely future expansion is, because obviously, if they don't expand or upgrade their server assets, this benefit is zero.
If this is the type of organization that's just going to stuff the server in a corner and forget about it for 10 years until it needs to be replaced anyway, there's no point.
If they're likely to grow organizationally, or even just technically (by say adding new servers with different roles, instead of just having an all-in-one server), then this provides a fairly substantial benefit.
What's the benefit now?
Virtualization bring benefits beyond future-proofing, and in some use-cases, they can be substantial.
The most obvious one is the ability to create snapshots and trivial-to-restore backups before doing something on the system, so if it goes bad, you can revert in one click.
The ability to experiment with other VMs (and play the "what if" game) is another one I've seen management get excited about. For my money, though, the biggest benefit is the added portability you get from running a production server on a hypervisor. If something
goes really wrong and you get yourself into a disaster-recovery or restore-from-backups situation, it is almost infinitely easier to restore a disk image to a machine running the same hypervisor than trying to do a bare-metal restore.

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

Migrating cluster to new hardware

Does anyone know of any best practices/documentation on migrating an existing RAC cluster to new hardware and operating system? We do not use ASM, but OCFS2.
Thanks!

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.

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

Migrate Sun Cluster (+RACdisks to new hardware running Sun Cluster ( + RAC)

Similar Messages

Maybe you are looking for