Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
We have a production Apache Server running on SLES 10 SP4 and we wish to migrate it onto new hardware.
For this , we wish to use the operating system as it is i.e. SLES 10 SP4. Is there any way by which we can make sure that when we install SLES 10 SP4 onto new machine , the exact RPMs
will be installed during installation process as there are on the existing system? I do not wish to clone the existing system as some of the properties will be changed to match the new
hardware setup, e.g. in the new system the hard disk is much bigger so likewise we will setup the partitioning. We only wish to make sure that the Package repository is same.
One thought would be to create the software repository of the existing system and feed it to the new installation. But this might create lot of RPM dependencies problems.
Any pointers in this regard will be helpful.
Everyone in your shoes would welcome the chance to upgrade to the newest SLES, I have hard time understanding the rationale behind keeping an outdated OS. Besides, it may even not have support for newer hardware.
Actually, http://www.mondorescue.org/ is good for this kind of thing. I've used it myself for copying to the SAME HW. For new hw you're going to need the right drivers/kernel modules etc installed, so (TBH) a fresh install of the OS then add on top (eg rsync), or as suggested, just go with the latest SLES as part of this move anyway.
NB: you're going to have to do regression testing anyway, so you might as well go with the latest & greatest.
Here is my explanation to the golden question as to why we wish to retain the old OS. Is simply because our customer want to continue with the old custom software which only runs on certain OS. ie Sles 10 SP4. No variations allowed!!!
Mondo is a good option perhaps as I have myself used it in past for building a complete clone system. But here the requirement is little bit different as I wish to only migrate the Packages in questions. But I would certainly go back and check if Mondo provides such a way out.
Thanks once again. And if any questions please go ahead n ask.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.