Bug 1236119

Summary:	General overview about major and minor migration
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	wfink
Component:	Documentation	Assignee:	sgilda
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.4.0	CC:	eap-docs, jawilson, lthon, wfink
Target Milestone:	post-GA	Keywords:	Documentation
Target Release:	EAP 6.4.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	Build Name: 22929, Migration Guide-6.4 Build Date: 29-05-2015 13:37:27 Topic ID: 7668-591800 [Specified]
Last Closed:	2015-10-20 12:51:05 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description wfink 2015-06-26 15:08:42 UTC

Title: Prepare for Migration

Describe the issue:
There should be a clear statement what a major/minor and micro migration means.

In general  (EAP6 onwards)
- a micro migration will not have issues as the configuration files and data should be simple picked up from the newer version.
- a minor migration should be compatible for the stored content and data but remove temporary directories
- a major migration need to be described as there can be many differences

see https://access.redhat.com/solutions/1311784 for details


For a major migration there is often no way to copy the configuration, especially for EAP4/EAP5 => EAP6.
(Maybe EAP6->EAP7 will be different)

A Minor migration from i.e. EAP 6.2 => 6.3 can be done by copy the folders of domain or standalone.
But there are some pitfalls.

The domain or standalone might include managed deployments which are stored in .../data/content. This folder need to be copied. Otherwise the start will fail as the content is missed.

The transaction directory (data/tx-object-store) should be deleted, open transactions should be handled before the migration starts.

The persistent timers data/timer-service-data need to be checked whether it is compatible, the different timers will have a file below with the deployment- and bean name, so it can be simple checked before the migration which timers are still in use.

Comment 1 wfink 2015-06-26 15:19:32 UTC

We should also include a statement that the configuration can be copied in case of a minor migration, but after starting the new server the configuration files might be updated and it is not possible to use it with an older version

see https://access.redhat.com/solutions/1295743


Next is how to do a rolling domain upgrade, see https://access.redhat.com/solutions/392423 for detailed information

Comment 15 Ladislav Thon 2015-08-07 06:51:31 UTC

Verified with Revision 6.4.0-37.