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

Similar Messages

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é

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

Migrating ZFH Server to new hardware.

I need to migrate our ZFH server to a new box. Its currently on a box that
is slowly dying. I can re-install ZFH on a new box with the same name and
IP address but how do I migrate the database and GUID info. Currently this
ZFH server has collected over 3000 handhelds from over 120 schools with
1000's of PC's running zfhproxy. Re-installing the proxy is not an option
at this point. Please help.

Is ZfH using MS SQL, or the build-in database ???
Best Regards
Tommy Mikkelsen
IT Quality A/S
Denmark
Novell Support Forums SYSOP
Please Report back any success or failure, That way we all learn
Sorry, but no support through email
"I hate bugs".......Tommy Lee Jones, MIB
Be a GroupWiseR, go http://www.groupwiser.net

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.

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

Move existing Exchange 2010 server to new hardware and reinstalling Exchange 2010

Hi so as the title states I need to Install Exchange 2010 on a brand new 2008R2 Server and transfer everything from the old Exchange Server.
Couple things though.
Existing 2008R2 Server w/ Exchange 2010 is also a Domain Controller.
Exchange needs to be uninstalled completely once Exchange is setup and going on new hardware.
Existing 2008R2 Server needs to stay up and stay a domain controller.
Questions are how do I go about this step by step?
Am I going to have problems uninstalling Exchange from the Domain Controller? Will this mess up anything with the Schema?
Any how to guides would be great. New Server will of course have a different name than existing Domain Controller server.
Any questions let me know.
Thanks!

Hi,
Here are the steps about moving the Exchange server to a new server which isn't a domain controller:
1.Install Exchange Server on a different computer.
2.Use Move Mailbox in the Exchange Task Wizard to move any existing mailboxes from the domain controller to the new Exchange server.
3.Rehome any public folders and roles held by the old Exchange Server computer to the new Exchange Server computer.
4.Uninstall Exchange Server from the domain controller.
http://technet.microsoft.com/en-us/library/aa997407(v=exchg.80).aspx
http://technet.microsoft.com/en-us/library/aa997060(EXCHG.80).aspx
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

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 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
---

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?

Migrating Share point server to new vm

Hi Techs,
We are having two instance of SharePoint server 2010, one is in production and one is test. we need to migrate both and SQL server 2008 r2 to new AD site in same domain.
Production server i having SQL server instance on separate VM.
What would be the best practice to migrate all 3 to new VMs and different site.
Thanks for your advise.
Amrit

There are several steps involved in migrating SharePoint servers from one domain to another, including converting/migrating user accounts to work in the new domain.
Here is a good guide that outlines the process involved in conducting such a migration: http://blogs.technet.com/b/sushrao/archive/2011/12/02/sharepoint-migrating-sharepoint-server-from-one-domain-to-another.aspx
I trust that answers your question...
Thanks
C
|
RSS |
http://crayveon.com/blog |
SharePoint Scripts | Twitter |
Google+ | LinkedIn |
Facebook | Quix Utilities for SharePoint

Migration of old server to new server...how??

Hi all...
I am here to discuss about some information to how migrate a server from old machine to a new server??
can someone provide some good links??
i did searched on google but didnt quite understood the whole thing.
Currently server is sql 2005 and in new server also i want the same .

hi
Refer this kb article for moving databases from one server to another server
http://support.microsoft.com/default.aspx/kb/314546
There are 4 ways to move/copy a database from one server to another server using SQL Server Tools.
i) Detach the database from the old server and attach it in the new server. This is purely offline operation and it moves the database instead of copying it.
Refer http://msdn.microsoft.com/en-us/library/ms190209.aspx : how to use attach/detach database in SQL Server Management Studio(SSMS)
ii) Back up the database in the old server and restore it in the destination server. This can be performed during online and it creates a new database in the destination server.
Refer http://msdn.microsoft.com/en-us/library/ms187048.aspx for more information.
iii) Using copy database wizard in SQL Server Management Studio.
Select the database in the source server in SSMS
Right click ->Tasks->Copy Database Wizard to launch the copy database wizard.
Enter the source and destination credentials and select either attach/detach or SMO type
click next and you can schedule or run immediately
Click finish to execute it
Refer http://msdn.microsoft.com/en-us/library/ms188664.aspx for more information.
iv) The last type is to generate the create script using Generate Script Wizard (SSMS) and execute it in the destination server.
Select the database in the source server in SSMS
Right click ->Tasks->Generate Scripts Wizard to launch the wizard.
Select the various scripting options needed and select the objects needed to generate the scripts for them. Make sure script data = true in the scripting option to generate script for data as well (INSERT statements)
click next ->next and finish to generate the script (new query window or clip board or file)
connect to the destination server and create the new database in it.
Click new query window and paste the script generated using GSW above and execute them with the destination database context.
Refer http://msdn.microsoft.com/en-us/library/ms181421.aspx for more information
v) Using Transfer Object in SMO
Sample code:
ScriptingOptions so = new ScriptingOptions();
so.ScriptData = true;
Transfer t = new Transfer(db);
t.CopyAllObjets = true;
t.options = so;
t.TransferData();
Note: Transfer class is available in Microsoft.SqlServer.SmoExtendedClass.dll (SQL Server 2008)
or Microsoft.SqlServer.Smo.dll (SQL Server 2005)
There are various member variables to be configurable. Also ScriptingOptions class object can be created and assigned to the transfer object as well.
set ScriptData = true in order to transfer data also. It copies the destination instead of moving the database
Refer http://msdn.microsoft.com/en-us/library/microsoft.sqlserver.management.smo.transfer.aspx for more information.
Does this helped?
Thanks
Sreekar

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

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

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 (N)AMP server to new hardware

Similar Messages

Maybe you are looking for