Best Options for Post-i 6.1.1 Upgrade Backups

We’re performing an i/OS 6.1.1 upgrade this weekend. My boss wants to perform a full system backup after we get done. However, full system backups take six-hours to run in my shop. I have a very tight upgrade window, and the machine can only be down for 18 hours. What’s my best option for backing up a newly upgraded operating system?

–Wil

There are two overriding goals in tight operating system upgrade scenarios: 1) Protect your work so that you don’t have to perform an i 6.1.1 upgrade a second time if the machine crashes; and 2) Get the machine up and running again as quickly as possible. These goals are not incompatible.

If you’re time constrained after an upgrade, your best bet is to perform a post-upgrade licensed code and QSYS library backup by using the Save System (SAVSYS) command. Run SAVSYS in lieu of a full system backup. A SAVSYS backup performs the following backup functions.

• Backs up your updated i/OS 6.1.1 licensed internal code and operating system objects in the QSYS library.
• Backs up system security data, including user profiles, authorization lists, and authority holders. SAVSYS uses the i/OS Save Security Data (SAVSECDTA) command to save security data.
• Backs up system configuration and system resource management data. SAVSYS invokes the Save Configuration (SAVCFG) command to save objects such as line, controller, and device descriptions, configuration lists, and hardware resource data.

With a SAVSYS backup, you can quickly save your new operating system objects immediately after the upgrade. You can then perform a Save While Active backup for the rest of your system, including non-QSYS IBM libraries, user data libraries, DLO folders, and the AS/400 Integrated File System (AS/400 IFS). Using these two backups together, you will perform the equivalent of a full system backup with minimum downtime. For more information on save while active backups, see this on article programming a simple save while active program.

One major point to remember is that while performing a SAVSYS backup, you must backup the objects to a device that can be used as an alternate IPL device. If you don’t backup to an IPL device, you won’t be able to restore the system from the SAVSYS media, if necessary. You must also put your system in restricted state to run this command, but don’t worry. SAVSYS backups run quickly.

For timing issues, another consideration is to deal with any potential upgrade speed bumps before the upgrade starts. Here are some things you can do to minimize upgrade slowdowns.

• Get two sets of upgrade and PTF media: a source set and a backup set–If one set of media is damaged, you can use the backup set without imperiling the upgrade.
• Consider upgrading from an image catalog rather than from media–With an image catalog, you load your installation media and PTFs to your iSeries, System i, or Power i partition and install from disk. See this article on image catalogs for more information. Image catalogs provide for quicker upgrades without worrying about damaged media.
• If using DVDs, ensure that your optical device is set up as an alternate IPL device–If your partition is only set up to IPL from tape, it will take more time to get technical help to reconfigure your system on the fly to use the optical drive as an IPL device. Identify your alternate IPL devices ahead of time.
• Make sure your tape drive is working correctly–Clean your tape heads and test to make sure the drive can perform the necessary backups.
• Check to make sure that you don’t have any IBM licensed programs that are incompatible with i 6.1.1–Many shops have been upgrading their systems since OS/400 V4RxMx. You may still have old non-supported licensed programs on the system. IBM won’t be able to upgrade those packages to i 6.1.1 and you may need to remove them before running the upgrade. Type in GO LICPGM and take option 10: Display Installed Licensed Programs. Press F11: Display Release, to view the installed release of all licensed programs on your system. Look for any IBM programs that are earlier than V5R4Mx and consult with IBM or your business partner as to how to handle these packages before the upgrade.

HTH

–Joe

RELATED STORIES

Image Catalogs: Another Timesaving Method for Upgrades or Installs

A Simple Save While Active Program

                     Post this story to del.icio.us
               Post this story to Digg
    Post this story to Slashdot