Upgrading Data Protection for SAP

Edit online

Upgrade Data Protection for SAP from an earlier version.

Before you begin

If you are upgrading IBM Storage Protect™ for Enterprise Resource Planning on a busy SAP system where the software continuously starts log archives, it might be difficult to find a maintenance gap without any active log archiving processes. To alleviate this situation, you can stop the prole daemon. Each operating system has a different method to stop the prole daemon as follows.
  • AIX® As a root user, run the following command: rmitab pd64
  • RHEL 7 and later, SLES 12 and later As root user, run the following command: systemctl stop prole_db2
  • Older Linux® versions and other Unix operating systems As root user, comment out the line with prole in /etc/inittab and run command init q
  • Windows™ As a user with Administrator privileges, either run command net stop prole, or use the Services control panel to stop the prole service.
Tip: When you stop the prole daemon, redo log archive operations will not work. Typically, this is not an issue because the next archive run would pick up all the redo logs that previously failed to archive. But, if the system is generating a large amount of redo logs, the file system might run out of space.

About this task

The format of the configuration file (.bki) was changed with version 5.4. The software accepts the previous format and converts it automatically. If it is necessary to use a version earlier than 5.4, the old format can be recovered by overwriting the new file with the empty file. The previous version provides the empty file. The file must then be initialized by setting the IBM Storage Protect password. However, the information about the current backup number is lost. As a result, more backup versions must be retained for a longer time than is specified by the MAX_VERSIONS parameter.

Procedure

  1. Verify that the Data Protection for SAP package is complete. The installation packages are provided on a disc or disc image (downloadable from Passport Advantage®), or the IBM® FTP server. See the release notes file in the IBM Storage Protect Knowledge Center for the most current release information.
  2. Check the readme files and release notes for incompatibilities between the installed version and the new version. Make sure that data backed up with an older version of IBM Storage Protect for Enterprise Resource Planning can still be restored with the version to be installed.
  3. Make sure that the requirements for the new version of Data Protection for SAP are met as described in .
  4. Make sure that planning information is available as described in the Prerequisites topic.
  5. A full backup of the SAP database must be performed before you upgrade to the new version.
  6. Uninstall the old version as described in the Uninstalling older versions topics.
  7. Install the new version of Data Protection for SAP as described in the Prerequisites topic.
  8. Update the Data Protection for SAP profile as described in the Migrate the Data Protection for SAP profile topic.
  9. Create the configuration file or files as described in the Creating the configuration files topic.
  10. Perform the necessary configuration tasks as described in the Configure the IBM Storage Protect client options topic.
  11. Verify the installation as described in the Verifying the installation topic.
  12. Verify the installation as described in the Verify the installation or upgrade topic.
  13. A full backup must be performed after you upgrade to the new version.
  14. Following an upgrade and subsequent RMAN setup on Windows, start (or restart) service OracleServiceSID to activate the new Data Protection for SAP environment.