Jan-Albert,
Thank you for the feedback. I considered going the direction that you went, but that really won't work for me. The steps that I outlined are high level. I left out things like shutting down SW, and changing DNS entry. (The IP address has to change going from VM world to physical world). I also have a proxy server in the mix, so that means that firewall rules have to be changed. Not looking forward to that either. Networking isn't to receptive about changing firewall rules. :-( <snip> And you might want to clean up archived actions to make database backup / restore a bit quicker </snip> I'm not really sure how to do this. I did a little research and I found this example: * archive_cleanup_command = 'pg_archivecleanup /mnt/server/archivedir %r' I don't really think that this is what I need, or is it? Thank you, and thank you for the feedback. Daryl ________________________________ From: [email protected] <[email protected]> on behalf of Ree, Jan-Albert van <[email protected]> Sent: Tuesday, November 15, 2016 1:50 AM To: [email protected] Subject: Re: [Spacewalk-list] Migrating to a physical We did something similar earlier this year. However to prevent issues and allow for testing we did things a bit different : - We installed a new server on which we created all the content we needed (we used a new FQDN so we didn't have to do anything to allow for 2 servers in the same network) - Then I wrote a migration script which installed the new certificate package and re-registered the machine to the new SW server This allowed for more control as we did migration per server group and we would never be left with unmanaged machines in the event the migration went wrong. Your plan to me looks solid otherwise, although before step 1 I'd shut down the spacewalk services to make sure nothing in the database gets changed. And you might want to clean up archived actions to make database backup / restore a bit quicker Good luck -- Jan-Albert Jan-Albert van Ree | Linux System Administrator | MARIN Support Group MARIN | T +31 317 49 35 48 | [email protected]<mailto:[email protected]> | www.marin.nl<http://www.marin.nl> [LinkedIn]<https://www.linkedin.com/company/marin> [YouTube] <http://www.youtube.com/marinmultimedia> [Twitter] <https://twitter.com/MARIN_nieuws> [Facebook] <https://www.facebook.com/marin.wageningen> MARIN news: Winaars Speurspel open dag<http://www.marin.nl/web/News/News-items/Winaars-Speurspel-open-dag.htm> ________________________________ From: [email protected] <[email protected]> on behalf of Daryl Rose <[email protected]> Sent: Monday, November 14, 2016 20:29 To: [email protected] Subject: [Spacewalk-list] Migrating to a physical I'm migrating my SW environment from a VM to a physical. I have the physical built, but before I move forward, I need to make sure that I'll have my steps down. Please review my steps, and let me know if I missed anything. 1. Rename current SW to temporary name. 2. Rename physical from temporary name to actual FQDN. 3. Install latest version of SW (current installation was recently upgraded to 2.5). 4. rsync following directories: * /etc/jabberd * /etc/rhn * /etc/sysconfig/rhn * /root/ssl * /var/www/html/pub * /var/satellite 5. Backup Postgres DB from VM 6. Restore Postgres DB to physical One additional comment, I am using signed cert, so I need to make sure that names and certificates are all correct, so I don't end up having issues with my current connections. If I'm missing something, or I have something wrong, please let me know. Thank you. Daryl
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
