Skip to content

Commit

Permalink
Restructure migration section
Browse files Browse the repository at this point in the history
The current structure of the migration section makes it a little difficult to navigate.
Based on the feedback, the following changes are being made:
- Split the migration section into two, so that it is more readable.
- Push cloning to the top, as this is one of the easier methods.

JIRA: https://issues.redhat.com/browse/SAT-29194
  • Loading branch information
Akshay Gadhave committed Jan 13, 2025
1 parent 8975474 commit 3257fbf
Show file tree
Hide file tree
Showing 4 changed files with 32 additions and 16 deletions.
6 changes: 4 additions & 2 deletions guides/common/assembly_upgrading-to-rhel9.adoc
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
include::modules/con_upgrading-el-on-project-or-proxy.adoc[]

include::modules/proc_upgrading-project-or-proxy-in-place-using-leapp.adoc[leveloffset=+1]
include::modules/proc_migrating-project-or-smartproxy-using-clone.adoc[leveloffset=+1]

include::modules/proc_migrating-project-or-smartproxy-using-backup-restore.adoc[leveloffset=+1]

include::modules/proc_migrating-project-or-smartproxy-using-backup.adoc[leveloffset=+1]
include::modules/proc_upgrading-project-or-proxy-in-place-using-leapp.adoc[leveloffset=+1]
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,9 @@
{Project} and {SmartProxy} are supported on both {EL} 8 and {EL} 9.
You can use the following methods to upgrade your {Project} and {SmartProxy} operating system from {EL} 8 to {EL} 9:

* Leapp in-place upgrade
* Migration by using backup and restore
* Migration by using cloning
* Migration by using backup and restore
* Leapp in-place upgrade

With Leapp, you can upgrade your {Project} or {SmartProxy} in place therefore it is faster but imposes a downtime on the services.
With migration, you can move your {Project} or {SmartProxy} to a fresh {EL} 9 system.
Expand Down
Original file line number Diff line number Diff line change
@@ -1,13 +1,9 @@
[id="migrating-{project-context}-or-proxy-using-backup_{context}"]
= Migrating {Project} or {SmartProxy} to {EL-abbr}{nbsp}9
[id="migrating-{project-context}-or-proxy-using-backup-restore_{context}"]
= Migrating {Project} or {SmartProxy} to {EL-abbr}{nbsp}9 using backup and restore

You can migrate your existing {ProjectServer} and {SmartProxyServer} from {EL}{nbsp}8 to a freshly installed {EL}{nbsp}9 system.
ifdef::satellite[]
The migration involves creating a backup of the existing {ProjectServer} and {SmartProxyServer}, which you then restore or clone on the new {EL}{nbsp}9 system.
[NOTE]
====
You can use cloning for {ProjectServer} backups but not for {SmartProxyServer} backups.
====
The migration involves creating a backup of the existing {ProjectServer} and {SmartProxyServer}, which you then restore on the new {EL}{nbsp}9 system.
endif::[]
ifndef::satellite[]
The migration involves creating a backup of the existing {ProjectServer} and {SmartProxyServer}, which you then restore on the new {EL}{nbsp}9 system.
Expand All @@ -20,13 +16,9 @@ For more information, see {AdministeringDocURL}backing-up-{project-context}-serv
. Deploy a system with {EL}{nbsp}9 and the same hostname and configuration as the source server.
This is the target server.
ifdef::satellite[]
. Restore the {ProjectServer} backup by following one of these options:
** Restore the backup.
. Restore the backup.
Restore does not significantly alter the target system and requires additional configuration.
For more information, see {AdministeringDocURL}restoring-{project-context}-server-or-{smart-proxy-context}-from-a-backup_admin[Restoring {ProjectServer} or {SmartProxyServer} from a backup] in _{AdministeringDocTitle}_.
** Clone the server.
Clone configures hostname for the target server and you can test it before retiring the source server.
For more information, see {AdministeringDocURL}sec-Cloning_to_Target[Cloning to the target server] in _{AdministeringDocTitle}_.
. Restore the {SmartProxyServer} backup.
For more information, see {AdministeringDocURL}restoring-{project-context}-server-or-{smart-proxy-context}-from-a-backup_admin[Restoring {ProjectServer} or {SmartProxyServer} from a backup] in _{AdministeringDocTitle}_.
endif::[]
Expand Down
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
[id="migrating-{project-context}-or-proxy-using-clone_{context}"]
= Migrating {Project} or {SmartProxy} to {EL-abbr}{nbsp}9 using clone

You can clone your existing {ProjectServer} and {SmartProxyServer} from {EL}{nbsp}8 to a freshly installed {EL}{nbsp}9 system.
ifdef::satellite[]
Create a backup of the existing {ProjectServer} and {SmartProxyServer}, which you then clone on the new {EL}{nbsp}9 system.
[NOTE]
====
You can use cloning for {ProjectServer} backups but not for {SmartProxyServer} backups.
====
endif::[]

.Procedure
. Perform a full backup of your {ProjectServer} or {SmartProxy}.
This is the source {EL}{nbsp}8 server that you are migrating.
For more information, see {AdministeringDocURL}backing-up-{project-context}-server-and-{smart-proxy-context}_admin#Performing_a_Full_Backup_admin[Performing a full backup of {ProjectServer} or {SmartProxyServer}] in _{AdministeringDocTitle}_.
. Deploy a system with {EL}{nbsp}9 and the same hostname and configuration as the source server.
This is the target server.
ifdef::satellite[]
. Clone the server.
Clone configures hostname for the target server and you can test it before retiring the source server.
For more information, see {AdministeringDocURL}sec-Cloning_to_Target[Cloning to the target server] in _{AdministeringDocTitle}_endif::[]

0 comments on commit 3257fbf

Please sign in to comment.