Planning for the migration to Tivoli® Storage Manager V7.1 is important because, in addition to installing the new software, you must move the contents of the V5 server database into the V7.1 server database.
About this task
- IBM® Tivoli Storage Manager Server-Client Compatibility and Upgrade Considerations
- (http://www.ibm.com/support/docview.wss?uid=swg21053218)
- Storage-agent and library-client compatibility with the IBM Tivoli Storage Manager server
- (http://www.ibm.com/support/docview.wss?uid=swg21302789)
When you move data from a V5 server database to a V7.1 database, a large amount of system processing capacity is used. The move also requires a large amount of I/O activity.
In your planning, consider testing the migration process on nonproduction systems. Testing provides information about how long the migration of the server database takes, which will help you to plan for the time that the server will be unavailable. Some databases might take much longer than others to migrate.
Testing also gives you more information about the size of the new database compared to the original, giving you more precise information about database storage needs.
If you have multiple servers, consider migrating one server first, to determine how the migration process will work for your data. Use the results of the first migration process to plan for migrating the remaining servers.
Hardware and software requirements for the V5 and V7.1 servers
Before you start the migration process, ensure that the system meets hardware and software requirements for the V5 server and the V7.1 server.- Compatibility with other components and versions
You can install other products that deploy and use DB2® products on the same system as the Tivoli Storage Manager Version 7.1 server running on AIX or Linux on System z. - Estimating database and recovery log requirements
Estimate the space requirements for the migration process, and the space requirements for the server databases and recovery log for the V7.1 server. The space requirements for a cross-platform migration from V5 to V7 are similar to the space requirements for an upgrade from V5 to V7 on the same operating system. - Planning data movement from FILE and DISK devices
The V7.1 server cannot access data that is stored by using DISK or FILE devices on the z/OS server. This restriction means that data that is stored on DISK or FILE devices must be backed up to tape before the migration begins. - Estimating storage and device requirements
Estimate the amount of space that will be required for data storage in the new Tivoli Storage Manager V7.1 system. Plan the devices to be used for storage. - Estimating the time required for migration
The V5 server is not available for use during migration operations. To help plan for the amount of time that the server will be unavailable, estimate the migration time. The time that is required to complete the migration of a V5 server depends on multiple factors. - Planning for upgrading multiple servers and components
If your environment includes multiple servers and storage agents, evaluate the compatibility of the versions being run with an upgraded V7.1 server. Plan to upgrade one server first in a test environment. Then stage the upgrade of additional servers and storage agents. - Planning for changes to storage agents
To connect to a V7.1 server in a system that uses the z/OS media server, storage agents must be at Version 7.1. - Preparing for operational changes
As you migrate your system from V5 to V7.1, the method for backing up and monitoring the server database changes. - Reference information for planning
Information about updated commands and server options, and the migration of device classes and library attributes, can help you plan the migration process.