Planning the Upgrade - BMC Remedy IT Service Management Suite 8

Planning the Upgrade - BMC Remedy IT Service Management Suite 8
of 6
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Related Documents
  10/15/2014Planning the upgrade - BMC Remedy IT Service Management Suite 8.1 - BMC Documentation Planning the upgrade The following topics will help you to plan your upgrade: Upgrade pathsUpgrade phasesPlanning preupgrade readiness tasksPlanning upgrade tasksUpgrade and overlaysParallel versus in-place upgrade Accelerated versus duplicated staging server Upgrade scenariosUpgrade sequencePlanning postupgrade tasksTools required for upgrade Upgrade paths You will be using one of these upgrade paths to get to the latest version of BMC Remedy ITSM. For each starting version, you must ensure that all components are thecorrect versions.— Upgrade pathDescription Upgrade Path 1: Fromversions earlier than 7.6.04This upgrade path involves the following process:1. Upgrade the BMC Remedy AR System server to the latest version. 2. Create overlays for all of your customizations. You can create customizations by using the Best Practice Conversion Utility (BPCU),which converts all of your customizations into overlays.3. Upgrade other components and applications to the latest versions. Solutions & ServicesProductsPartnersSupportEducationCommunities   BMC Remedy IT Servi …  8.1 Login  Added by Hemant Baliwala , last edited by Hemant Baliwala  on Jul 03, 2014 Note You can upgrade directly to BMC Remedy ITSM 8.1.00 from BMC Remedy ITSM 7.0.03 patch 009, or a later version.If, however, you are upgrading from a version earlier than BMC Remedy 7.0.03 patch 009, perform one of the following actions:Do a fresh installation of BMC Remedy ITSM 8.1.00 and migrate the data.First upgrade to BMC Remedy ITSM 7.0.03 patch 009 and then upgrade to 8.1.00. Search all online product do  10/15/2014Planning the upgrade - BMC Remedy IT Service Management Suite 8.1 - BMC Documentation Upgrade Path 2: Fromversion 7.6.04 or later If you have already created overlays, you can directly upgrade each component to the latest version. The Best Practice Customizationmode of BMC Remedy Developer Studio ensures that all customizations are saved as overlays.Back to top Upgrade phases  At a high level, the upgrade process is split into the following phases for better planning. These phases are valid for both upgrade paths: Upgrade phaseDescription Phase 1: Preupgrade readinessFor this phase, you must plan to ensure that you have prepared the entire environment for a successful upgrade.See Planning preupgrade readiness tasks.Phase 2: UpgradeFor this phase, you must consider the upgrade sequence and upgrade type.See Planning upgrade tasks.Phase 3: PostupgradeFor this phase, you must plan for postupgrade tasks such overlay reconciliation, performance optimization, and sanity testing.See Planning postupgrade tasks.Back to top Planning preupgrade readiness tasks Ensuring preupgrade readiness requires performing of the following tasks: TaskAdditional information Downloading the latest installers from the installation files to upgradeBMC Remedy ITSM Suite components and installersCompleting the upgrade checklistsSee Completing the planning spreadsheet for an upgrade.Ensuring that you meet all minimum version requirementsSee Reviewing the compatibility matrix before upgrading.Executing the BMC Remedy Configuration utility for overall health check beforeupgradeSee BMC Remedy Configuration Check utility.Backing up the operating systems and database (VM Snapshot)You must perform the backup before you install each component.Practicing the upgrade on a test environmentSee Upgrade testing.Freezing production rollouts from any administrative changes—Backing up all of the customizations. You must export the customizations fromDeveloper StudioSee Exporting objects. (This topic will open from the BMC Remedy AR System8.1.00 space).Resolving any known issues before the upgradeSee Known and corrected issues.Performing server configuration adjustments per the documentationSee Preparing your components and applications for an upgrade.Preparing for ITSM CI attribute and multi-tenancy changesSee Update to the multi-tenancy model.For detailed information about preupgrade readiness tasks, see Preparing for upgrade.Back to top Planning upgrade tasks  10/15/2014Planning the upgrade - BMC Remedy IT Service Management Suite 8.1 - BMC Documentation The type of upgrade that you perform depends on which of the following scenarios describes your situation: SituationAdditional information You want to upgrade a single server or server group environment.—You are upgrading with overlays already implemented or you want to implement them.See Upgrade and overlays.You want to do an in-place (without staging server) or a parallel (with staging server) upgrade.Here, you need to decide if you want to use an accelerated staging or duplicated staging environment.See Parallel versus in-place upgrade Accelerated versus duplicated staging environmentBack to top Upgrade and overlays In BMC Remedy Action Request System 7.6.04, the overlays feature was introduced to preserve application customizations during the upgrade process. During anupgrade, the upgrade installers ignore application overlays and change only the objects that were srcinally installed with the application or server. After the upgrade, theapplication or server continues to use the overlays instead of the srcin objects for runtime operations so that the customizations are preserved. For more information,see Upgrading with overlays already present. hen upgrading from a previous release that was customized without overlays, you will need to create overlays for existing customizations, acquire srcin objects, restoresrcin objects on the staging server, and minimize the number of overlays on your system. For more information, see Upgrading without overlays already present.The following terms will help you to understand the overlays implementation:Custom object: A customer-created object that is not distributed by BMC.Origin object: An srcinal, unmodified object that is included with a released BMC product.Overlaid object: An srcin object that has an overlay associated with it.Overlay object: A customized version of an srcin object that is used in place of the srcin object. In this case, the srcin object becomes an overlaid object.For detailed information about the overlays feature, see Customizing applications using overlays and custom objects in the BMC Remedy AR System documentation.Back to top Parallel versus in-place upgrade The following table compares the parallel and in-place upgrade methods. Parallel upgrade (with staging server)In-place upgrade (without staging server) Uses a staging server, which allows you to upgrade your application and create overlays or otherwise addresspre-existing customizations to your BMC Remedy AR System server objects while your production server remains available to users Additional staging hardware is not needed. Additionalload balancer or configuration updates are not needed.The original production environment is preserved, allowing fast fallback.You perform the upgrade in the production environment.Minimal end-user downtimeMinimal overall upgrade time and complexityNeed to perform delta data migrationDelta data migration is not needed. Data validation isnot needed.Upgrade is not confined to a fixed upgrade window. Upgrade can be done over several days or weeks.You can perform the upgrade in stages by initiallyupgrading the BMC Remedy AR System server or BMCRemedy Mid Tier.For server group:Users can be active throughout most of the process.Users can start accessing each secondary server after it is upgraded and added to the Load Balancer.For server group:Users can start working after the primaryadministration server is upgraded.Users can start accessing each secondary server only after it is upgraded.Back to top Accelerated versus duplicated staging server  The following table compares accelerated and duplicated staging servers. Accelerated staging serverDuplicated staging server Note Refer to the end-to-end steps for performing the upgrade that applies to your specific scenario. See Upgrade scenarios.  10/15/2014Planning the upgrade - BMC Remedy IT Service Management Suite 8.1 - BMC Documentation To upgrade using an accelerated staging server (database-only upgrade), you create a copy of theproduction server database in the staging environment only.To create a duplicated staging server, you create an exactduplicate of your production server.The AR System server must be upgraded on the staging server against the copy of the production server database only.You must perform a normal upgrade with file system.BMC out-of-the-box configurations are applied after the upgrade in the staging environment.Configurations of the production environment are retained inthe staging environment.Back to top Upgrade scenarios The following diagram illustrates the upgrade scenarios.Depending on your upgrade scenario, follow the end-to-end steps documented in one of the following topics:Parallel (with staging server) upgrade in a server group with overlays presentParallel (with staging server) upgrade on a single server with overlays presentIn-place upgrade on a single server with overlays presentIn-place upgrade in a server group with overlays presentParallel (with staging server) upgrade in a server group without overlays presentParallel (with staging server) upgrade on a single server without overlays present Back to top  Upgrade sequence You must upgrade the BMC Remedy ITSM suite components in the following sequence:This sequence implies that you must first upgrade the platform, then upgrade your CMDB, then your applications, and finally all clients that reside on your local computer. For information about different installers and the components they install, see BMC Remedy ITSM Suite components and installers.Back to top
Related Search
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks