IBM E16RMLL-I - Tivoli Storage Manager, Implementation Manual, Page: 237 / 828

Chapter 5. Database and recovery log
207
84 Recovery Log Copy Volume C:\TSMDATA\RLM\LGM_01.DSM - 256
Synchronization megabytes of 512
tsm: LOCHNESS_SERVER1>query logvol
Volume Name Copy Volume Name Copy Volume Name Copy
(Copy 1) Status (Copy 2) Status (Copy 3) Status
---------------- ------ ---------------- ------ --------------- ------
C:\TSMDATA\SERV- Sync'd Undef- Undef-
ER1\LOG1.DSM ined ined
D:\TSMDATA\RLP\- Sync'd C:\TSMDATA\RLM- Sync'd Undef-
LOG_01.DSM LGM_01.DSM ined
As with the database volume mirror, after the log copy volume is created, a
background process synchronizes the data in the primary volume to the mirror.
The output of
query logvol
now shows the two mirror volumes and the status of
each copy. The status should always be
Sync’d
.
We can see there is still the previous database volume present,
C:\TSMDATA\SERVER1\LOG1.DSM, which is not mirrored. We address this in
5.7.2, “Removing the default recovery log volume” on page 209.
5.7 Removing default volumes
During installation on UNIX/Linux platforms, default database and recovery log
volumes are created, usually in the server installation directory
(/usr/tivoli/tsm/server/bin on AIX, for example). On Windows, the install process
does not create any database or log volumes. You initialize the server with a
wizard that allows you to specify where your first database and log volumes are
located.
We recommend removing the initial default database and recovery log volumes.
Removing them gives you complete control over the new database and recovery
log distribution. If your Tivoli Storage Manager server is running on a Windows
platform, and you wish to remove the first database and log volumes that you
created in favor of better placement, you can also follow the examples.
5.7.1 Removing the default database volume
To remove a database volume, you must first have enough free space existing in
the database to reduce its size by the amount of the volume’s size. The Tivoli
Storage Manager server will automatically move any active pages in the volume
that you are removing to other volumes. The
query db command in the Maximum
Reduction (MB) column shows the amount by which the database can be