Sei sulla pagina 1di 4

Infrastructure and Backup Requirement

The following hardware and software components required for TSM server

Tape Library IBM LTO Ultrium TS3500 with 4 LTO4 Tape Drives
IBM x3650 series Red hat Linux 6.1 for TSM server
Backup Software - IBM Tivoli Storage Manager 7.1

Details about TSM server related requirements and infrastructure

TSM server

REDHAT LINUX 6.1 / TSM 7.1

Tape library

IBM LTO4 TS3500


4 x LTO4 drives SAN attached
256 slots, 10 entry/exit slots
100 LTO4 tapes
1 cleaning cartridge - barcoded (library autocleaning feature used)
50 GB database space + 140 GB log space

Tapes
TSM database and
recovery log
Data (tape) duplication

Offsite Tape vaulting

2 sets of data:
one set of tapes always in the Tape Library library (multiple primary stogage
pools)
one set of tapes (one copy pool) in Tape Library
Daily to Tape Library

TSM Server Component


TSM server component consists of the following elements which are part of the
design and implementation:
TSM server software,
TSM database,
TSM tape library and storage pools,
TSM backup policies,
Central scheduling,
TSM administrative client,
Monitoring and reporting,
IBM Tivoli Disaster Recovery Manager for off-site tape vaulting.

TSM Server Software

TSM server software has to be installed on Red hat Linux 6.1. TCP/IP is used as a TSM communication
protocol in this implementation.

Starting and stopping TSM server

TSM server operates as a service.


TSM server can be started:
manually as a service : TSM Server1
TSM server can be stopped:
from TSM administrative Command Line Interface (root access):
#dsmadmc
(Enter TSM admin ID and password)
Check if there are any processes or sessions running if there are any cancel
them:
TSM> q session
TSM > cancel session <ID> - for all sessions of the type Node
TSM> q process

TSM> cancel proc <ID> - for all processes


Check if there are any tapes in the tape drives if there are any dismount them
manually:
TSM> q mount
TSM > dismount volume <label> - for all mounted tape volumes
TSM> halt
Answer yes to confirm halt of TSM server process.

TSM server options


TSM has two types of options:
set up in the option file dsmserv.opt and require restart of TSM server process to take effect
set up in the TSM server database using command set <option> <value> they dont require restart
of TSM server process.

TSM Database and Recovery Log


Details about the TSM database and recovery log volumes TSM instance:
Database
Recovery Log
Total Size
50 GB
160 GB
Directory
where
\ActiveLog
volumes are located
\ActiveLogMirror
\ArchiveLog
\ArchiveLogFailover
Database
everyday - Scheduled full backup to
backup
LTOCLASS4
- Scheduled full backup to TSMBKP
device class

Tape library configuration


In this implementation TSM server utilizes the IBM Ultrium Tape Library TS3310 with
2x LTO4 tape drives connected to two SAN switches, equipped with the barcode
reader, 36 cartridge slots and I/O slot for 6 cartridges.
Each LTO Gen4 tape can store 800GB of uncompressed data and on average approx.
1600GB compressed (if compression ratio 2:1).
For TSM server to access a SCSI library, the tape library should be set to the
appropriate mode - called random mode.
The TSM configuration of tape devices consists of four components: TSM libraries,
drives, paths and device classes.
A Library and drive correspond to physical tape library/autochanger and to a tape
drive,
A path provides access to a destination (device) from a source (machine). The types
of relationships that can be defined include:
Between a server (including the SAN agent) and a drive, disk, or a library
Between a NAS data mover and a library (not used in this implementation)
A device class represents a device type that can be used by TSM. The server uses
device class definitions to determine which types of devices and volumes to use to:
Store backup, archive, or space-managed data in primary storage pools
Store copies of primary storage pool data in copy storage pools
Store database backups
Export or import TSM data

Store the backupsets


One device class can be associated with multiple storage pools, but each storage
pool is associated with only one device class.

Tape library configuration


The configuration of the LTO TS3500 tape library:
Library name
Library type
Device Alias Name
Autolabel
S/N
Device Driver

TS3310
SCSI
Changer0
No
0000078247660401

The configuration of the paths in the TSM is the following:


Destination

Destination
type

Source

Source type

Device

TS3500
DRIVE1
DRIVE2
DRIVE3
DRIVE4

Library
Drive
Drive
Drive
Drive

MOHTSM01
MOHTSM01
MOHTSM01
MOHTSM01
MOHTSM01

Server
Server
Server
Server
Server

lb0.1.0.2
mt0.0.0.1
mt0.0.0.2
mt0.0.0.3
mt0.0.0.4

Remarks

The configuration of the device classes in the TSM is the following:


Device class name
Library name
Device type
FORMAT
Mount Wait time
Mount Retention time
Mount Limit
Directory
Max volume (file) size

LTOCLASS4
TS3500
LTO
Drive
60 min
60 min
DRIVES
N/A
N/A

TSMBKP
N/A
FILE
Drive
10
/DRM\/TSMBKP
51200M

1.1 Host Connections


Out of 40 ports on each switch there are 24 GBICs fiber interface modules installed and active, and 14 are used so far
for connection to hosts. Below are charts of connections of particular host HBAs (host bus adapters) to respective SAN
switch ports:
Top switch: M/T 2498-B40, S/N 107329F

Bottom switch:

M/T 2498-B40, S/N 107329G

Labels - aliases example description:


p750 C1P1_T2
IBM Power 750 server, M/T 8233 E8B, S/N 0624DEP, HBA PCI card slot C1, port 1,
port in VIOS - T2
x3650 E20 C1P1

IBM xSeries model 3650, M/T 7947-52G, location in rack EIA20, HBA PCI card slot C1, port 1

Lib3584 TAP1

IBM Tape Library M/T 3584-L53, LTO Tape drive n. 1

DS8700 C1P0

IBM Storage DS8700, M/T 2423-941, host interface card slot C1, port 0

Potrebbero piacerti anche