IBM TotalStorage DR550 SMB Version 1.0 ------ 27 May 2005 Page 38
IBM Storage Systems Copyright © 2005 by International Business Machines Corporation
FC 4674 Install J1A in Rack 1
FC 4812
Right Drive Cradle in Rack 1
FC 6025
25 Meter LC/LC Fibre Channel Cable 2
FC 9200
Open System Device Drivers 1
FC 9590
No Data Cartridge 1
FC 9600
pSeries AIX Attachment 1
The 3592s can be placed inside of the 3584 or 3494 tape libraries or you can mount them in a separate
rack. Please discuss the required library features with your local IBM sales team or business partner.
The required software for 3592 attachment is already installed in the DR550. This includes updated
device drivers and a new version of Tivoli Storage Manager (5.2.3). You will need to make sure that the
firmware on the 3592 is updated to the latest version if you are using existing machines. If you have
purchased new 3592s, the firmware for WORM support will already be installed.
Data Migration
When using tape with the DR550 SMB, you should review the appropriate Tivoli Storage Manager
parameters involved with data migration. TSM has the ability to migrate data from one media to another
(from the disk in the DR550 SMB to a WORM cartridge in the 3592 as an example) as determined by the
parameters. These parameters are documented in the TSM publications and are also included in the
DR550 redbook. Two of the parameters that should be reviewed include:
MIGDelay
Specifies the minimum number of days that a file must remain in a storage pool before the file
becomes eligible for migration from the storage pool. The server counts the number of days
from the day that the file was stored in the storage pool or retrieved by a client, whichever is
more recent. This parameter is optional. You can specify an integer from 0 to 9999. The
default is 0, which means that you do not want to delay migration.
If you want the server to count the number of days based only on when a file was stored and not
when it was retrieved, use the NORETRIEVEDATE server option.
MIGContinue
Specifies whether you all the server to migrate files that do not satisfy the migration delay time.
This parameter is optional. The default is YES>
Because you can require that the files remain in the storage pool for a minimum number of days,
the server may migrate all eligible files to the next storage pool yet not meet the low migration
threshold. This parameter allows you to specify whether the server is allowed to continue the
migration process by migrating files that do not satisfy the migration delay time.
Possible values are:
Yes
Specifies that, when necessary to meet the low migration threshold, the server continues
to migrate files that do not satisfy the migration delay time.
If you allow more than one migration process for the storage pool, some files that do not
satisfy the migration delay time may be migrated unnecessarily. As one process
migrates files that satisfy the migration delay time, a second process could begin
migrating files that do not satisfy the migration delay time to meet the low migration
threshold. The first process that is still migrating files that satisfy the migration delay
time might have, by itself, cause the low migration threshold to be met.
No
