Mostly the database is backed up from old system and restored on new system. For delta data which is generated during the upgrade,they use delta data migrater (DDM)
For metadata the upgrade process take care
I worked for many customer, they used different technologies. I am aware about:
Bladelogic Server Automation
Dell Operation Manager
IBM - I am not remeber the extact name of the product.
what do you mean by 'migrate' ?
if you are doing it right you just build a new server/OS, push the app stack, push the configs, hook up to the data and go. shouldn't matter if you are replacing hardware because it's old, failed, etc. w/ the advent of virtualization this is probably becoming less common as only the hypervisor is replaced and that now entails just a network boot to bring it into a vsphere cluster...
Thanks Bill. Just to clarify what I mean by migrate, I am looking to see what people use to take an older system (more than 3-4 years old) and moving it to a newer, higher performance box. I don't need to upgrade the OS, but want more horsepower. In this case, I want to migrate my Windows 2003 server onto another physical server, not virtualized. The application requires a physical server. Backup/restore is too slow for my situation, and I'm looking for a tool that can migrate this server quickly. I also have other SAN-booting servers which require similar functionality.
does your OS even support that ? usually moving the hardware around under windows isn't a good idea...
why is backup/restore too slow for your situation ? how else do you expect to get data from one server to another ?
Just curious, the application requires a physical server or the vendor won't support the app on a VM? It seems to me that there are only a few use cases that actually require physical VMs these days.
With just moving your 2003 server to new hardware you are still looking at 2003 extended support being up next year. I didn't catch what application is in question but I tend to think Bill's recommendation of building a new app server is a good one. Especially with Windows where a server tends to get pretty bloated/grumpy after about 4 years (of course it depends on what is being down with the server). It is even worse with Win 2008 where the winsxs directory continues to grow with patches and service packs. As I understand it this directory can be thinned out but MS doesn't recommend it.
Thanks Jason. Just to clarify, there are some applications which will run under a VM, just not as well as in a stand-alone environment. I have encountered many cases where virtual servers (when sharing system components and horsepower) just don't have enough juice to get the job done in a timely fashion. Case in point is month-end financial processing. Other than month-end, VMs are great for these apps, but when running month-end jobs, migrating them to a physical box provides a significant advantage in completing required reports on time. In this case, we use SanXfer from InQuinox to migrate the server V2P for the month-end processing, then P2V back into the VM when it completes. Having moved to a SAN-boot approach, thereby having both the data and the OS in the SAN, the V2P or P2V migration is completed within a couple of minutes, hardly enough downtime to worry about... (Re)Building a server would take way too long for this type of work. SanXfer makes it happen so quickly and reliably that it will blow you away. I just wasn't sure how often others were using this approach, how frequently, or if anyone was even aware that it could be done this way. There are certainly many other application Use Cases which can be addressed by this server migration approach as well.