1. Performing a platform only upgrade
BMC Remedy IT Service Management
Version 8.1.xx
The information included in this documentation, including BMC product screen shots, is the proprietary and confidential information of BMC Software, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and conditions of the applicable End User License agreement for the product, to the proprietary and restricted rights notices included in the product documentation, and to the confidentiality and non-disclosure obligations to which you have agreed.
© Copyright 2014 – 12/12/2014 BMC Software, Inc

2. In this video… Scope of platform upgrade BMC Remedy AR System I
BMC Atrium Core
Go live
Existing
Staging
Existing
In-place upgrade
Parallel upgrade

3. In this video… Scope of platform upgrade Upgrade methods
BMC Remedy AR System I
BMC Atrium Core
Upgrade methods
Go live
Existing
Staging
Existing
In-place upgrade
Parallel upgrade

4. In this video… Scope of platform upgrade Upgrade methods
BMC Remedy AR System I
BMC Atrium Core
Upgrade methods
End-to-end steps
Go live
Existing
Staging
Existing
In-place upgrade
Parallel upgrade

5. Upgrade scope

6. Upgrade scope BMC Remedy AR System BMC Remedy AR System server
BMC Remedy Mid Tier
BMC Remedy AR System clients
BMC Remedy Encryption Security upgrade

7. Upgrade scope BMC Remedy AR System BMC Atrium Core BMC Atrium CMDB
BMC Atrium Web services
BMC Atrium Integrator
BMC Remedy AR System server
BMC Remedy Mid Tier
BMC Remedy AR System clients
BMC Remedy Encryption Security upgrade

8. Upgrade methods

9. Upgrade methods
In-place upgrade
Parallel upgrade

10. Upgrade methods In-place upgrade Parallel upgrade
Current production server
Go live
User
You perform the upgrade on the production server.
Production environment is down during the entire upgrade process.
Takes less time.
Not recommended if you have to adjust customizations.

11. Upgrade methods In-place upgrade Parallel upgrade
Current production server
Go live
User
Staging server
Current production server
Go live
Reference server
User
You perform the upgrade on the production server.
Production environment is down during the entire upgrade process.
Takes less time.
Not recommended if you have to adjust customizations.
You perform the upgrade on a staging server and go live with it.
Production environment is down only during the last stage of the upgrade.
Recommended if you need more time for user acceptance testing

12. Staging environment

13. Staging environment
Accelerated
Duplicated

14. Staging environment Accelerated Duplicated
Create a copy of the production server database in the staging environment.
Staging
Production

15. Staging environment Accelerated Duplicated
Create a copy of the production server database in the staging environment.
Staging
Production
You are upgrading all of the products installed on your server.
You do not have BMC Service Impact Manager, Integration for BMC Remedy Service Desk, or BMC ProactiveNet Performance Management installed on your production system.
Running the installer in Install mode.

16. Create an exact duplicate of your production server.
Staging environment
Accelerated
Duplicated
Create a copy of the production server database in the staging environment.
Create an exact duplicate of your production server. =
Staging
Production
Staging
Production
You are upgrading all of the products installed on your server.
You do not have BMC Service Impact Manager, Integration for BMC Remedy Service Desk, or BMC ProactiveNet Performance Management installed on your production system.
Running the installer in Install mode.

17. Create an exact duplicate of your production server.
Staging environment
Accelerated
Duplicated
Create a copy of the production server database in the staging environment.
Create an exact duplicate of your production server. =
Staging
Production
Staging
Production
You are upgrading all of the products installed on your server.
You do not have BMC Service Impact Manager, Integration for BMC Remedy Service Desk, or BMC ProactiveNet Performance Management installed on your production system.
Running the installer in Install mode.
You can test your system after each upgrade step, because you have a working system at the end of each stage.
Run the installer in Upgrade mode.

18. In-place upgrade steps

19. Production Environment
In-place upgrade
1. Prepare and plan
Review the system requirements
Download the installation files
Obtain the BMC Remedy license keys
Prepare your database
Prepare the base platform
Perform the Pre-upgrade checks and Configuration checks
Complete the planning spreadsheet
Mid Tier
User
Start Here 1
Prepare and plan
Production Environment
Go Live
Primary Server
Secondary Server
Production Database

20. Production Environment
In-place upgrade 2.
Restrict changes
Suspend all administrative operations on the primary server until the upgrade is complete.
Do not create or modify any objects, including:
Forms
Workflow
Fields
Classes
Federation sources
Contracts
Agreements
You must not perform such activities on the primary server until you reach the Go Live stage.
Mid Tier
User
Start Here 1
Prepare and plan
Production Environment
Go Live
Primary Server
Secondary Server 2
Restrict changes
Production Database

21. Production Environment
In-place upgrade
3. Freeze user activity
At this stage the actual downtime begins.
Put your production URL under maintenance mode.
Perform the cut-over activities.
Mid Tier
User
Start Here 3
Freeze user activity 1
Prepare and plan
Production Environment
Go Live
Primary Server
Secondary Server 2
Restrict changes
Production Database

22. Production Environment
In-place upgrade
4. DB backup
Perform a backup of the database in the production environment
Perform source server related adjustments. Leave the configuration as they are until you complete the delta data migration (DDM). You must revert these changes during the Go Live stage.
Mid Tier
User
Start Here 3
Freeze user activity 1
Prepare and plan
Production Environment
Go Live
Primary Server
Secondary Server 2
Restrict changes
Production Database
DB backup and server adjustments 4

23. Production Environment
In-place upgrade
7. Upgrade platform
Upgrade:
BMC Remedy Mid Tier
BMC Remedy AR System
BMC Atrium Core
Follow the sequence provided in the documentation.
Mid Tier
User
Start Here 5
Perform upgrade 3
Freeze user activity 1
Prepare and plan
Production Environment
Go Live
Primary Server
Secondary Server 2
Restrict changes 5
Upgrade platform
Production Database
DB backup and server adjustments 4

24. Production Environment
In-place upgrade
10. Post-upgrade procedures
Perform feature and functionality validation and performance testing.
Take backup.
Refer to the documentation for detailed list of activities.
Mid Tier
User
Start Here 5
Perform upgrade 3
Freeze user activity 1
Prepare and plan
Production Environment
Go Live
Primary Server
Secondary Server 2
Restrict changes 5
Upgrade platform
Production Database 6
Post-upgrade steps
DB backup and server adjustments 4

25. Production Environment
In-place upgrade
11. Upgrade secondary
It is recommended, that you use the copy of the upgraded primary BMC Remedy AR system server and BMC Remedy mid tier to create secondary servers.
You could also use the installers to upgrade the secondary.
During upgrade, you must point the secondary server to the new production (staging server) database.
Mid Tier
User
Start Here 5
Perform upgrade 3
Freeze user activity 1
Prepare and plan
Production Environment
Go Live
Primary Server
Secondary Server 2
Restrict changes 7
Perform upgrade 5
Upgrade platform
Production Database 6
Post-upgrade steps
DB backup and server adjustments 4

26. Production Environment
In-place upgrade
16. Go Live
Perform the Go live activities and remove the production URL from the maintenance mode.
Mid Tier
User
Start Here 5
Perform upgrade 3
Freeze user activity 1
Prepare and plan
Production Environment 8
Go Live
Primary Server
Secondary Server 2
Restrict changes 7
Perform upgrade 5
Upgrade platform
Production Database 6
Post-upgrade steps
DB backup and server adjustments 4

27. Parallel upgrade steps

28. Production Environment
Parallel upgrade 2.
Prepare staging
User
Start Here 14
Go Live
Prepare your staging server using the accelerated or duplicated method.
At this stage you must also decide your staging development server, staging QA server, and the staging production server. 12
Freeze user activity 1
Prepare and plan 2
Prepare staging environment
Delta Data
Migration (DDM)
Mid Tier
Staging Environment 10
Run DDM 6
Perform upgrade
Staging Dev Server 13
Run DDM (Final run) 6
Upgrade platform
Production Environment 8
Post-upgrade procedures
Primary Server
Secondary Server 3
Restrict changes 9
Perform upgrade 11
UAT
Staging Database
Production Database
DB restore and destination server adjustments
DB backup and source server adjustments 5 4 7
Restore DB on other staging servers
*Valid on if you are upgrading from a non-overlay version (older than )

29. Production Environment
Parallel upgrade
5. DB restore
User
Start Here 14
Go Live
Restore the production database in the staging environment. Steps for restoring are different for the accelerated staging server and the duplicated staging server.
Complete the destination server adjustments.
Leave the configuration as they are until you complete the DDM. You must revert these changes during the Go Live stage. 12
Freeze user activity 1
Prepare and plan 2
Prepare staging environment
Delta Data
Migration (DDM)
Mid Tier
Staging Environment 10
Run DDM 6
Perform upgrade
Staging Dev Server 13
Run DDM (Final run) 6
Upgrade platform
Production Environment 8
Post-upgrade procedures
Primary Server
Secondary Server 3
Restrict changes 9
Perform upgrade 11
UAT
Staging Database
Production Database 5
DB restore and destination server adjustments
DB backup and source server adjustments 4 7
Restore DB on other staging servers

30. Production Environment
Parallel upgrade
7. Restore DB on other servers
User
Start Here 14
Go Live
You must restore the upgraded database on all the other staging servers in the environment. For example, if you have performed the upgrade in the staging development server, you must restore the upgraded database on the staging QA and staging production.
This activity ensures that all your staging environments are at the same level for you to proceed with post upgrade procedures and delta data migration. 12
Freeze user activity 1
Prepare and plan 2
Prepare staging environment
Delta Data
Migration (DDM)
Mid Tier
Staging Environment 10
Run DDM 6
Perform upgrade
Staging Dev Server 13
Run DDM (Final run) 6
Upgrade platform
Production Environment 8
Post-upgrade procedures
Primary Server
Secondary Server 3
Restrict changes 9
Perform upgrade 11
UAT
Staging Database
Production Database 5
DB restore and destination server adjustments
DB backup and source server adjustments 4 7
Restore DB on other staging servers

31. Production Environment
Parallel upgrade
10. Delta Data Migration
User
Start Here 14
Go Live
You can run the Delta Data Migration (DDM) Tool one time or multiple times. BMC recommends that you run the tool at least twice — before you start your production outage, and again after the production outage begins.
Ensure that you complete the postmigration activities before you proceed with the next step. 12
Freeze user activity 1
Prepare and plan 2
Prepare staging environment
Delta Data
Migration (DDM)
Mid Tier
Staging Environment 10
Run DDM 6
Perform upgrade
Staging Dev Server 13
Run DDM (Final run) 6
Upgrade platform
Production Environment 8
Post-upgrade procedures
Primary Server
Secondary Server 3
Restrict changes 9
Perform upgrade 11
UAT
Staging Database
Production Database 5
DB restore and destination server adjustments
DB backup and source server adjustments 4 7
Restore DB on other staging servers

32. Production Environment
Parallel upgrade
11. User Acceptance Testing
User
After you complete the testing and applying all the fixes, you must create a UAT-Verified-Clean backup.
After the upgrade is validated on the staging server, restore the system to a UAT-Verified-Clean backup. This ensures that any testing data used during the validation is removed and that the staging server is in a clean state for the final delta data migration.
Start Here 14
Go Live 12
Freeze user activity 1
Prepare and plan 2
Prepare staging environment
Delta Data
Migration (DDM)
Mid Tier
Staging Environment 10
Run DDM 6
Perform upgrade
Staging Dev Server 13
Run DDM (Final run) 6
Upgrade platform
Production Environment 8
Post-upgrade procedures
Primary Server
Secondary Server 3
Restrict changes 9
Perform upgrade 11
UAT
Staging Database
Production Database 5
DB restore and destination server adjustments
DB backup and source server adjustments 4 7
Restore DB on other staging servers

33. Production Environment
Parallel upgrade
12. Freeze user activity
User
Start Here 14
Go Live
At this stage the actual downtime begins.
Put your production URL under maintenance mode.
Perform the cut-over activities. 12
Freeze user activity 1
Prepare and plan 2
Prepare staging environment
Delta Data
Migration (DDM)
Mid Tier
Staging Environment 10
Run DDM 6
Perform upgrade
Staging Dev Server 13
Run DDM (Final run) 6
Upgrade platform
Production Environment 8
Post-upgrade procedures
Primary Server
Secondary Server 3
Restrict changes 9
Perform upgrade 11
UAT
Staging Database
Production Database 5
DB restore and destination server adjustments
DB backup and source server adjustments 4 7
Restore DB on other staging servers

34. References
docs.bmc.com

35. BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other BMC trademarks, service marks, and logos may be registered or pending registration in the U.S. or in other countries. All other trademarks or registered trademarks are the property of their respective owners.