IBM E16RMLL-I - Tivoli Storage Manager, Руководство по внедрению

Страница: 730 / 828

700
IBM Tivoli Storage Manager Implementation Guide
22.2.5 Enabling production mode
If your upgraded server instance seems to be in order, you may take the server
out of idle state by following these steps:
1. Remove the nomigrrecl and disablescheds options and change expinterval to
the desired value, in the dsmserv.opt file.
2. Raise the migration thresholds of your storage pools to the desired value.
3. Restart your server instance.
4. Run client tests. Try backing up and restoring an object or file space.
Following these outlined recommendations should made your upgrade
procedure uncomplicated and safer, since you have your database along with
other supporting files backed up. Should an upgrade procedure fail, you are able
to bring your server instance back to the original level using these backed
components.
We will now show some sample server upgrade procedures.
22.3 Performing server upgrades
In this section we discuss specific steps for upgrading the Tivoli Storage
Manager V5.2 server running on Windows 2003 and AIX 5.3 to the latest version
available at the time of writing this book, which is 5.3.2.2. For more information,
refer to the IBM Tivoli Storage Manager Installation Guide manual for your server
platform.
Bear in mind that whenever you are about to upgrade your Tivoli Storage
Manager server, prior to migration you need to back up the following items:
򐂰 The IBM Tivoli Storage Manager database ( backup db )
򐂰 The volume history file ( backup volhist )
򐂰 The device configuration file ( backup devconfig )
򐂰 The dsmserv.opt file
򐂰 The dsmserv.dsk file
You should also consider that the later versions contain more features and might
therefore require additional database space. We recommend that you increase
your database size by 5% prior to migration and reduce it after the migration
when the database space has stabilized.