Académique Documents
Professionnel Documents
Culture Documents
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
Table of Contents
DXi-Series Configuration and Best Practices Guide for Tivoli Storage Manager . 6
How to Use This Guide ................................................................................................. 6
Shortcuts to Quick Start Activities .............................................................................. 6
Documentation and References................................................................................... 7
Online Documentation for your Quantum product ................................................................... 7
DXi-Series Management Console ...................................................................................................... 7
Virtual Tape Library Setup .................................................................................................................. 7
Network Attached Storage .................................................................................................................. 7
DXi Replication ................................................................................................................................... 7
TSM Documentation ........................................................................................................................... 8
Quantum Corporation
BPG00014-v03
pg. 3
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
Space Reclamation........................................................................................................................... 23
DXi Multiprotocol Guidance - NFS/VTL Scenario ............................................................................. 24
Quantum Corporation
BPG00014-v04
pg. 4
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
DXi VTL
DXi NAS - NFS and/or CIFS
Quantum Corporation
BPG00014-v04
pg. 6
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
DXi Replication
Refer to the following documents for DXi-to-DXi Replication setup:
Quantum Corporation
BPG00014-v03
pg. 7
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
TSM Documentation
TSM Server documentation in PDF format is available at the following web site: TSM Documentation Info
Center It includes Installation, Upgrade and Migration, Administrators Guides and Administrators References for AIX, HP-UX, Linux, Solaris and Windows - Supported Hardware Compatibility List - IBM TSM
Hardware Compatibility List
Quantum Corporation
BPG00014-v04
pg. 8
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
Parameter or Option
Compression
Encryption
Deduplication
TDP Multiplexing
Dynamic Tracking
TSM Tape Reclamation
Trigger
ReUseDelay
TXNBYTELIMIT
Miscellaneous Options
Server Resources
Setting
No
No
No
No
Disabled (applies to AIX only)
50-90% depending upon backup load
(see the TSM Trigger Setting & Cartridge Size section later in this document)
0
25600
2097152 for backup direct to tape
(see The Transaction Byte Limit client option in Appendix A: Additional
TSM Information for detailed information)
Recommendations
Memory Requirements for All Operating Systems:
Server Name
12 GB.
16 GB if you are using deduplication.
At least 32 GB for heavily used servers. Using 32 GB or more of memory
enhances performance of the Tivoli Storage Manager Server database
inventory.
For multiple instances, each instance requires the memory listed for one
server. Multiply the memory for one server by the number of instances
planned for the system.
The server name is an internal name for Tivoli Storage Manager, and is used
for operations that involve communication among multiple Tivoli Storage
Manager servers. Examples include server-to-server communication and
library sharing.
The Server Name is different from the host name. However, the default
server name that is suggested is the same as the host name of the system that
you are using.
Database name
Quantum Corporation
The database name is always TSMDB1, for every server instance. This
name cannot be changed.
BPG00014-v03
pg. 9
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
Quantum Corporation
BPG00014-v04
pg. 10
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
HP LTO-3
HP LTO-4
HP LTO-5
The IBM tape device driver by default uses persistent reservation for IBM tape drives. The IBM Tape Installation and Users Guide describes how to verify and change the reservation type by operating system.
See Technote 1470319 for additional details.
Note:
AIX displays a message that It needs devices.fcp.changer or devices.scsi Fileset, when trying to
use a non-IBM device with Tivoli Storage Manager Server running on AIX. The message is being
generated because the O/S is seeing a device, but does not recognize what it is because there is
no driver for it loaded into the AIX Kernel. The Tivoli Storage Manager device driver does not
load into the AIX Kernel, so you can expect this message for any devices that are being used with
Tivoli Storage Manager that the OS does not already have its own driver for. The message can be
safely ignored and it can be bypassed. When configuring devices on a different SCSI or FSCSI
adapters, run 'cfgmgr' with the '-l' option to restrict it to looking at a single bus, rather than
searching the entire system which it does by default. e.g. cfgmgr -l scsi0
Quantum Corporation
BPG00014-v03
pg. 11
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
1. Create a virtual tape library on the DXi, specifying the emulation type, number of slots, number of
tape drives, and their emulation type. If desired, multiple VTLs can be created to service different
backup servers.
2. Create virtual tape cartridges on the DXi for the VTL specifying the cartridge type, quantity, and
capacity
3. Assign the VTL to a client on the SAN to which the DXi is attached
In the DXi Remote Management Console, under the Configuration tab, the VTL page allows you
to configure a DXi to present its storage capacity as VTL partitions that are compatible with TSM
and other standard backup applications. You may add virtual tape drives and storage slots to
VTL partitions create and work with virtual tape cartridges, and map partitions to hosts.
Partitioning lets you divide the DXi virtual tape drives and storage elements into separate VTLs, usable by
separate host computers. The Partitions page contains a list of assigned tape drives, as well as listing all
user-defined VTL partitions that are currently configured on the system. This page also lets you add, edit,
and delete partitions.
The Summary page displays the maximum number of VTL partitions, the total number of tape drives, and
the number of assigned tape drives. The Summary page also provides a list of configured partitions on
the system. Click the link in the Name column to edit the specific partition.
Caution: You can use a VTL for any virtual tape library only when the following conditions are true:
There is no mixed media involved in the VTL. Only one type and generation of drive and media is
emulated in the library.
Every server and storage agent with access to the VTL has paths that are defined for all drives in
the library.
If either of these conditions is not met, any mount performance advantage from defining a VTL library
to the Tivoli Storage Manager server can be reduced or negated.
Note:
If you are planning to replicate partitions to another DXi system, you must ensure that every partition name and barcode number on the system is unique. You can NOT have duplicate partition
names or barcode numbers on a DXi system or on a system receiving a replicated partition.
The Create Media page allows you to create virtual media for a specific partition. Once created, these
virtual cartridges are available for backing up data. You can configure the media type, capacity, starting
barcode, and initial location on this page.
Note:
It is possible to oversubscribe space on the DXi system. The sum total of capacity for all media
could be more than the capacity of the system. Be careful to ensure that this does not happen.
Quantum Corporation
BPG00014-v04
pg. 12
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
i)
ii)
iii)
iv)
Refer to the section on Sequential Access Storage Pool Volumes in the IBM Tivoli Storage Manager
Administrators Guide for more information on creating storage pools of this type.
Quantum Corporation
BPG00014-v03
pg. 13
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
Ensure that all non-existent tape drives are cleared from the ODM database
If installing TSM on AIX, ensure it is acceptable to reboot the AIX server at least one time during
implementation
Ensure that a device addressed at LUN0 is present and that there are NO gaps in the LUN numbering schema following LUN0. If there is no device at LUN0 device discovery will abort. If there
is a gap in the LUN numbering device discovery will not find devices with LUN numbers beyond
the gap.
Quantum Corporation
BPG00014-v04
pg. 14
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
It is not a good idea to configure the maximum number of virtual tape drives onto a single server and then
perform I/O through all of them concurrently. Better performance can be achieved by defining a subset of
all the virtual tape drives across multiple TSM servers.
Quantum also recommends that backups be staggered so that only a subset of drives is in use at any
given time. Staggering backups is recommended IF you would otherwise exceed the recommended maximum number of concurrently active VTDs. During a backup, the data transfer rate is primarily controlled
by the server because the DXi system does not restrict the ingest data rate. This creates the opportunity
for one or more TSM servers to burst data at a higher rate leaving less bandwidth for the remaining virtual
tape drives.
The recommended maximum number of concurrently active virtual tape drives for various maximum aggregate bandwidths is listed in the table below.
DXi Model
Max VTDs*
DXi4701
64
32
DXi6700
80
80
DXi6701 / DXi6702
256
80
DXi6802
256
80
DXi6902
512
160
DXi8500**
160
160
1,777MB/s (6.4TB/Hr)
DXi8500***
512
160
Quantum Corporation
BPG00014-v03
pg. 15
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
There is virtually no relationship between the configured capacity of a virtual tape cartridge and the tape
drive emulation that has been configured for the partition:
Backup/restore operations will span the number of tapes required, based on the configured capacity.
Vaulting/duplicating operations performed by the backup application will ignore the virtual capacity
when writing to another cartridge, whether virtual or physical. Duplication operations are performed on a set of backup data, not on a per-cartridge basis.
DXi-Series devices limit the maximum capacity permitted by the tape drive emulation; the minimum is 5GB.
The capacity utilization is tracked in COMPRESSED GB, and the data is stored in compressed form. That
is, 100GB of data that is 2:1 compressible will be reported as occupying 50GB of virtual tape cartridge
space.
TSM environments with a very low backup load can have the trigger set lower, inducing more load
on the DXi in order to reduce capacity demand.
TSM environments with a very high backup load might need a higher trigger value, sacrificing capacity in order to make more I/O budget available to achieve a better backup window.
Unless there are overwhelming reasons not to, use a small virtual cartridge size. 100 GB is recommended.
A reason to use a larger cartridge size: Limitations on the number of cartridges per VTL. (i.e. the
end user want a single VTL to manage all backup data).
The reason to use a smaller cartridge: Minimizes the amount of TTR I/O for files that span multiple
cartridges. For example:
o Assume a file spans 3 cartridges occupying part of A, all of B, and part of C. If that file
does not expire but data on A and C expires and triggers TTR, then only A and C will be
rewritten and B will be left as-is. This reduces TTR load.
o If that file had been written to one super-size cartridge, then all that data would have
been transcribed again and again.
Quantum Corporation
BPG00014-v04
pg. 16
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
Reclamation
TSM Reclamation
Backups and archives in TSM are policy-based. These policies govern:
Because TSM is policy-based, backup objects, or versions, are expired rather than the entire backup or
individual piece of media. As backup objects on a tape cartridge expire, the cartridge becomes more and
more logically empty. Eventually the amount of data remaining on the tape drops below a predefined
threshold and needs to be reclaimed. This TSM reclamation process mounts the tape to be reclaimed and
mounts another tape with free space, and copies all the remaining valid data from one tape to another.
The tape cartridge that was the source for the reclamation is now empty and can be reused as a scratch
tape.
This TSM reclamation process occurs automatically and is usually scheduled to occur once per day. Reclamation ensures that data is stored efficiently and that the media is optimized for restoration. If active
data pools are used, reclamation must occur and must run regularly to remove inactive versions from the
active data pool. A version becomes inactive whenever a new version of that object is received from the
client.
Quantum Corporation
BPG00014-v03
pg. 17
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
DXi Reclamation
There is another process, completely internal to the DXi system, known as reclamation. This DXi process has nothing to do with TSM reclamation. DXi reclamation is part of the internal space management
process that occurs on DXi systems. Space reclamation only runs when invoked by schedule or initiated
manually by the user. Space reclamation performs two primary functions:
Reconciliation: The list of expired data is processed in order to reduce the reference count for the
unique data blocks that they referenced.
Deletion: Those unique data blocks that have zero reference counts are deleted from the deduplication pool.
Quantum Corporation
BPG00014-v04
pg. 18
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
CIFS Protocol -The CIFS (Common Internet File System) protocol defines a standard for remote
file access using many computers at a time. This protocol allows users with different platforms to
share files without installing additional software. This protocol is used with Windows networks.
NFS Protocol - The NFS (Network File System) protocol was originally designed by Sun Microsystems and allows all network users to access shared files stored on computers of different
types. NFS provides access to shared files through an interface called the Virtual File System
(VFS) that runs on top of TCP/IP. Users can manipulate shared files as if they were stored locally
on the user's own hard disk. With NFS, computers connected to a network operate as clients while
accessing remote files, and as servers when providing remote users access to local shared files.
This protocol is used with UNIX/Linux networks.
If you are using network segmentation and Microsofts Automated Deployment Services (ADS),
you must use the DXi data segment IP information for ADS management, NOT the DXi management segment. ADS uses the Server Message Block (SMB) data protocol to manage the NAS
shares on your system, which requires that the management traffic use the data segment.
DXi systems allow you to configure your network for separate segment types. The three primary segments are defined by the type of network traffic that can be used on that segment. The three types of
network traffic are:
Replication traffic - This segment is used exclusively for replication data movement.
Data traffic - This segment is used exclusively for NAS data movement.
Management traffic - This segment is used exclusively for remote management (Web page access).
Each network segment has its own network interface (IP address, network mask, and default gateway). In
this way, the segment is separated from other network segment traffic.
Installing and configuring the DXi and TSM for NAS operation consists of the following major steps.
Quantum Corporation
BPG00014-v03
pg. 19
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
During a backup operation, the NFS or CIFS share on the DXi designated as the storage pool volume
receives the backup objects directly from the client/server.
Quantum Corporation
BPG00014-v04
pg. 20
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
Network Considerations
Some network considerations include:
Use a dedicated network for backup data, or use QoS features that guarantee network bandwidth.
Another option would be to use virtual networks (VLANs) to segregate backup from production
network traffic.
Configure network interface cards (NICs) in the server and clients, and set routers to full duplex.
Use multiple DXi Ethernet interfaces when connecting to the network. The more Ethernet interfaces used, the better the total performance capability will be.
Set each switch port connected to the DXi to auto-negotiate/auto-sensing. The DXi Ethernet
network interface cards are preset to auto/auto and cannot be changed.
Quantum Corporation
BPG00014-v03
pg. 21
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
When using a DXi as NAS for a backup-to-disk target, consider the following when you create a backupto-disk folder:
Set the maximum size for backup-to-disk files to an appropriate size. If you create small but numerous files, performance may be slow, since the computer must still process each file. However,
if you create large files, file system limitations can cause memory allocation problems or network
issues. These issues can be a problem if you store files across a network.
Specify fewer backup sets in a backup-to-disk file, to allow TSM to reclaim disk space faster. Fewer backup sets may allow the overwrite protection period to expire sooner.
Enable the Allocate the maximum size for backup-to-disk files option, to reduce disk fragmentation. To ensure that backup data fills each backup-to-disk file to capacity, increase the append
period of the media set that you associate with the backup-to-disk files. The backup data's overwrite protection period may also increase, because the overwrite protection period starts at the
end of the last append job.
Backup performance may be affected when you enable the Allocate the maximum size for
backup-to-disk files option. To find what works best for your environment, enable this option for a
job. Then, compare the performance with a job that does not allocate the maximum size for backup-to-disk files. Experiment with the options for buffered reads and buffered writes. Enabling these
options may increase backup performance.
Quantum Corporation
BPG00014-v04
pg. 22
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
Replication Considerations
For first-time replication setups, it is important to manually replicate the name space once the target system is configured and is online. This facilitates the first replication following the first backup to that
share/partition. The replication is only available to NAS shares with deduplication enabled. The DXi supports user-selectable 128-bit or 256-bit AES encryption for replication. Data is only encrypted while in
transit between the replication source and replication target. Data is decrypted upon arrival at the replication target. Encryption may affect replication performance. You should disable encryption if your WAN is
already secured. For more information, please refer to Quantum DXi-Series Best Practices for Data Replication.
Space Reclamation
Space management involves two processes: data reconciliation and data reclamation. Data reconciliation is used to create a list of what can be removed. It runs automatically every twelve hours, at noon and
midnight, unless data reclamation is running. Data reclamation is the process of deleting the data on the
data reconciliation list. It can be scheduled, or run manually. There is significant overhead associated with
this process and, therefore, it should not be run during periods of high appliance use. In addition, replication, reclamation, and backup stream ingest all consume system resources and should not all be done at
the same time.
Quantum Corporation
BPG00014-v03
pg. 23
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
It is recommended to schedule daily reconciliation and reclamation, to manage the available space. The
scheduled time should be configured to start the data reclamation process after daily backups are complete. The default schedule is weekly, and the default time for the data reclamation is set to 12:00 AM on
Sunday. These parameters are user configurable; you should configure them for your backup window.
Additional notes:
Quantum Corporation
BPG00014-v04
pg. 24
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
OS
MS Windows
Device Type
Driver
Notes
IBM Driver
IBM Driver
Tivoli driver
Tivoli driver
IBM Driver
Tivoli driver
Tivoli driver
Tivoli driver
IBM Driver
Linux
Solaris
HP-UX
Quantum Corporation
BPG00014-v03
pg. 25
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
AIX
Tivoli driver
Not supported
IBM Driver
The range of values is 300KB through 2097152KB (2 GB); the default is 25600. A transaction is the unit
of work exchanged between the client and server. Because the client program can transfer more than one
file or directory between the client and server before it commits the data to server storage, a transaction
can contain more than one file or directory. This is called a transaction group. This option permits you to
control the amount of data sent between the client and server before the server commits the data and
changes to the server database, thus affecting the speed with which the client performs work. The
amount of data sent applies when files are batched together during backup or when receiving files from
the server during a restore procedure. The server administrator can limit the number of files or directories
contained within a group transaction using the TXNGROUPMAX option. The actual size of a transaction
can be less than your limit. Once this number is reached, the client sends the files to the server even if
the transaction byte limit is not reached.
Increasing the amount of data per transaction increases recovery log requirements on the server.
Check log and log pool space to ensure there is enough space. Also note that a larger log might
result in longer server start-up times.
Increasing the amount of data per transaction might result in more data being retransmitted if a retry occurs. This might negatively affect performance.
The benefits of changing this parameter are dependent on configuration and workload characteristics. In particular, this parameter benefits tape storage pool backup more so than disk storage pool
backup, especially if many small files are in the workload.
When setting the size of transactions consider setting a smaller size if you are suffering many resends
due to files changing during backup when using static, shared static, or shared dynamic. This would apply
to static as well as to shared because when the client realizes a file has changed during a backup and
decides to not send it, the file that is, it would still have to re-send the other files in that transaction. To
enhance performance, set TXNBYTELIMIT to the max 2097152, and on the server, raise
Quantum Corporation
BPG00014-v04
pg. 26
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
TXNGROUPMAX to 256. Additionally, for small file workloads, first stage the backups to a disk storage
pool and then migrate to tape.
See this IBM web page for this (TXNBYTELIMIT) information and other client performance tuning information.
RELABELSCRATCH Information
The RELABELSCRATCH parameter allows you to automatically relabel volumes when they are returned
to scratch. Support for this parameter is available in Fix Pack 5.5.1 and later levels.
Virtual Tape Libraries (VTLs) maintain volume space allocation after Tivoli Storage Manager has deleted
a volume and returned it to a scratch state. The VTL has no knowledge that the volume was deleted and
it keeps the full size of the volume allocated. This can be extremely large depending on the devices being
emulated. As a result of multiple volumes that return to scratch, the VTL can maintain their allocation size
and run out of storage space.
The only way for the VTL to realize that a volume has been deleted and its space can be reallocated is to
write to the beginning of the newly returned scratch volume. The VTL will then see the volume as available. Tivoli Storage Manager can relabel volumes that have just been returned to scratch if the
RELABELSCRATCH parameter is specified.
This optional parameter has been added to the DEFINE and UPDATE LIBRARY commands and is intended for use with VTLs. See the following link for additional information from the IBM website:
RELABELSCRATCH parameter supported for DEFINE and UPDATE library commands (for Virtual Tape
Libraries)
General Virtual Tape Library Considerations For Tivoli Storage Manager Servers
The following text is from IBM website:
http://www-01.ibm.com/support/docview.wss?rs=663&uid=swg21425849
Abstract
Summarization of considerations that should be taken while using Tivoli Storage Manager servers to
manage virtual tape libraries (VTL).
Content
In general, a virtual tape library (VTL) is a component that emulates physical tape drives, libraries, and
volumes, and that utilizes disk as the underlying storage hardware. Because VTLs emulate all the SCSI
capabilities of tape hardware, VTL usage is not apparent to Tivoli Storage Manager servers, regardless of
the server level or platform.
Because the underlying disk storage hardware is disk and because "drives" and "volumes" in a VTL environment are logical entities that are modified for particular environments, The differences between VTLs
and physical tape libraries has significant side-effects for Tivoli Storage Manager servers in the following
key areas:
Quantum Corporation
BPG00014-v03
pg. 27
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
Library capacity: The concept of "capacity" in VTLs is different than "capacity" in physical tape libraries.
In a physical tape library, each volume has a defined capacity, and the library's capacity is defined in
terms of the total number of volumes residing in the library. The capacity of a VTL, alternatively, is defined
in terms of total available disk space. Furthermore, the number and size of volumes on disk can be increased or decreased by the user.
This variability affects what it means to "run out of space" in a VTL. For example, a volume in a VTL can
run out of space before reaching its assigned capacity if the total underlying disk runs out of space. In this
situation, the server can receive an abrupt end-of-volume message without any warning, resulting in
backup failures.
When out-of-space errors and backup failures occur; however, there is usually disk space available in the
VTL. It is "hidden" in volumes that are not currently in use. For example, volumes that are logically deleted or returned to scratch in the Tivoli Storage Manager server are only deleted in the server database.
The VTL is not notified, and the VTL maintains the full size of the volume as allocated in its capacity considerations.
To help prevent out-of-space errors, you can use the RELABELSCRATCH parameter on the DEFINE
LIBRARY and UPDATE LIBRARY commands. The RELABELSCRATCH option enables the server to
overwrite the label for any volume that is deleted and to return the volume to scratch status in the library.
During this operation, volumes are checked out of the library and then checked back in with an immediate
LABEL LIBVOLUME command. As part of this command, OVERWRITE=YES is specified for the volume
that was deleted and returned to scratch.
Remember: The RELABELSCRATCH option was introduced in V5.5.1. Later fixes enhanced the original
functionality. To take full advantage of this option, use the following server levels:
Storage pool selection: The number of user-defined volumes in a VTL tends to be very large compared
to the number of volumes in physical tape libraries. Furthermore, the capacity of VTL volumes is often
logically modified to be smaller than the capacity of physical tape volumes. These characteristics do not
cause any general backup or restore problems. However, they can create some undesired side effects for
performance in environments that combine VTL storage pools and physical tape storage pools.
When selecting storage pools to restore or to retrieve data, the server evaluates the number of volumes
required for the operation and selects the storage pool with the fewest volumes. A VTL that is set up with
small logical volumes often has data that is spread out over more volumes than the data in a physical
tape library. As a result, the server selects the physical tape storage pool, which has fewer volumes, rather than the faster VTL storage pool.
To force the server to ignore the number of volumes when selecting a storage pool to restore or to retrieve data, use the IGNORENUMVOLSCHECK option.
The IGNORENUMVOLSCHECK option is available with the following server levels:
Quantum Corporation
BPG00014-v04
pg. 28
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
Drive selection performance: Drive configuration in a VTL, like volume configuration in a VTL, is variable.
Most VTL environments attempt to utilize as many drives as possible to maximize the number of concurrent tape operations. A single tape mount in a VTL environment is typically significantly faster than a
physical tape mount. However, using a large number of drives increases the amount of time that Tivoli
Storage Manager servers require to select a drive for the requested mount operation. The selection process takes longer as the number of drives defined in a single library object in the Tivoli Storage Manager
server increases. Virtual tape mounts can take as long as or longer than physical tape mounts depending
on the number of drives in the VTL.
APAR IC66116 improved server drive-selection performance by roughly doubling the optimal number of
drives in a VTL. Prior to IC66116, the general recommendation was to create libraries with about 80 - 120
drives. Some environments required more drives, but this tended to increase the overhead involved in
server drive selection. If more drives were required, the recommendation was to logically partition the VTL
into multiple libraries and assign each library 80 - 120 drives.
With APAR IC66116, the recommended maximum number of drives is 150 - 250 for each library. This
recommendation is based on benchmark testing at V6.1 and V6.2. The changes from this APAR apply to
the V5.5.5.0, V6.1.4.0, and V6.2.1.0 servers.
The V6.3 Tivoli Storage Manager server introduced a new library type, called VTL that increases mount
performance with large numbers of drives. When using this library type, there can be no mixed media
within the library and a path must be defined for all the drives to all of the servers or storage agents that
use the library. Given these two assumptions, the server can dramatically improve drive selection performance; such that the recommended maximum number of drives would be 300 - 500 drives per library. If
the assumptions made for VTL libraries are not true, the drive selection performance will degrade to the
levels of a SCSI library type as stated in the previous paragraph (128 - 256 drives). For example, a mixture of different drive types (3592 + LTO) or drive generations (LTO2 + LTO3) within the same VTL library
would degrade performance. Likewise, if paths are not defined between all drives and a storage agent
that used the library, drive selection performance would also degrade. For more information on the new
VTL library type see Managing virtual tape libraries in the V6.3 Tivoli Storage Manager Information Center.
Notes:
Server version 6 and later benefits more from the changes in APAR IC66116 than server version 5 because some of the changes in the APAR relate specifically to DB2 performance.
The drive recommendations above are highly dependent on the environment. For example, a large number of drives can overload the bandwidth capabilities of the fibre cards in the VTL or the HBA on the host.
Environmental constraints can reduce the effective number of drives that should be defined within a single library to a lower value than the recommended maximums.
Quantum Corporation
BPG00014-v03
pg. 29
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
help
query log
query status
query request
query session
/*show sessions*/
query schedule
/*show schedules*/
query association
query admin
query occupancy
query db
query log
query vol
query libvol
query dbvol
query logvol
Quantum Corporation
BPG00014-v04
pg. 30
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
disable events nteventlog error /*dont log general errors*/
enable events nteventlog anr2578
query enabled nteventlog
query library
query drive
query devclass
query mount
query process
query spacetrigger db
Quantum Corporation
BPG00014-v03
pg. 31
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
Backup Database
CLI %>backup db devclass=lto type=full scratch=yes wait=no
(This must be done before a file backup can occur).
Local Backup
CLI %> update stgpool diskpool highmig=0 lowmig=0
(this will cause all the files to be written to tape as soon as each is written to the diskpool.)
Edit /usr/tivoli/tsm/client/ba/bin/dsm.opt.smp remove * in front of servername and overwrite
words to the right with TSM server name, (set in Starting TSM section above). Save as dsm.opt
Edit /usr/tivoli/tsm/client/ba/bin/dsm.sys.smp change server_a to the same name used in above
step. Overwrite node.domain.company.COM with the name of your server, (examplesvtaix2.adic.com). Save as dsm.sys
>/usr/tivoli/tsm/client/ba/bin/dsmj (This starts the client backup gui)
Quantum Corporation
BPG00014-v04
pg. 32
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
Quantum Corporation
BPG00014-v03
pg. 33
DXi-Series Configuration and Best Practices Guide For Tivoli Storage Manager
Helpful Resources
The following is a list of documents, references, and links where you can find additional information regarding specific activities and products.
Retired Best Practice Guides superseded by this document:
From Quantum Best Practice Guide Tivoli Storage Manager with DXi-Series
http://www.quantum.com
StorageCare Guardian Web Site
http://www.quantum.com/ServiceandSupport/Services/GuardianInformation/index.aspx
StorageCare Vision Web Site Reference
http://www.quantum.com/Products/Software/Storagecarevision/Index.aspx
Quantum Service Web Site
http://www.quantum.com/ServiceandSupport/Index.aspx
Call Center Americas:
To contact Quantums world-class support representatives, please refer to the information below:
http://www.quantum.com/ServiceandSupport/ServiceLevelAgreement/Index.aspx
Quantum Corporation
BPG00014-v04
pg. 34