- 论坛徽章:
- 0
|
配置服务器和客户机
ID Name: client
Password: client
即可以按图形方式进行备份测试。
启动管理员客户端命令行界面：
#dsmadmc
ID Name: admin
Password: admin
tsm: TSM>
可以选择性的启动Console方式管理员客户端命令行界面：
#dsmadmc -consolemode
ID Name: admin
Password: admin
会有类似如下信息：
Session established with server TSM: AIX-RS/6000...
......
随后所有的log信息将同时显示在该窗口中。
启动Web方式管理界面：在浏览器URL栏输入如下地址http://tsmserv:1580
Registering Licenses
tsm: TSM>register license file=mgsyslan.lic number=10
tsm: TSM>register license file=mgsyssan.lic number=10
tsm: TSM>register license file=oracle.lic number=10
tsm: TSM>register license file=library.lic number=1
tsm: TSM>register license file=libshare.lic number=1
Increasing Database and Recovery Log Sizes
Format and define a 500MB database volume and a 25MB recovery log volume
and extend the database and recovery log, by entering:
tsm: TSM>define dbvolume db01.dsm formatsize=500
tsm: TSM>define logvolume log01.dsm formatsize=25
tsm: TSM>extend db 500
tsm: TSM>extend log 25
Increasing Disk Storage Pool Sizes
For example, to create a 100MB volume named sbkup01.dsm in BACKUPPOOL, do the following:
tsm: TSM> define volume backuppool backup01.dsm formatsize=100
Adding Backup-Archive Clients
For example, register a node named MERCEDES with the password MONTANA.
tsm: TSM> register node mercedes montana userid=none
tsm: TSM>
Excluding System Files
For UNIX, we recommend that you have the following minimum include-exclude
list in your include-exclude options file:
exclude /unix/
exclude.dir /unix/
exclude /.../core
exclude.fs /usr/tivoli
Automating Client Operations
You can schedule the following on most clients:
l TSM backup, archive, restore, and retrieve operations
l Operating system commands
l Macros (files that can contain operating system and TSM commands)
1. Schedule an incremental backup and associate the schedule with the clients.
a. Expand Automation.
b. Select Client Schedules.
c. From Operations, select Define Schedule.
d. Enter the schedule information and Finish.
e. Return to Client Schedules.
f. Select the desired schedule.
g. From Operations, select Define Associations.
h. Enter the association information and Finish.
2. Start the client scheduler. For the schedules to become active for a workstation,a user must start the scheduler from the node.
启动客户机调度程序
To start the client scheduler on your client node and connect to the server
schedule, change to the Tivoli Storage Manager installation directory and enter the following command:
dsmc schedule（启动客户机调度程序）
When you start the client scheduler, it runs continuously until you close the window, end the process, or log off your system.
To run the schedule command in the background and to keep the client scheduler
running, even if you log off your system, enter the following:
nohup dsmc schedule >/dev/null 2>&1 （后台启动客户机调度程序）
If a Tivoli Storage Manager password is required for your workstation and you want to run the schedule command in the background, enter the password with the command.
Root User: To start the client scheduler automatically, ensure that the
passwordaccess option is set to generate in your client system options file
(dsm.sys), then , add the following entry to the /etc/inittab file:
tsm: nce:/usr/bin/dsmc sched > /dev/null 2>&1 # TSM scheduler（开机自动启动客户机调度程序）
Note: You must include the redirection to /dev/null in the command.
Adding an Automated Tape Library to the Server
1. Define an automated tape library and its two internal drives.
tsm:TSM> define library autolib libtype=scsi
tsm:TSM> define path tsm autolib srctype=server desttype=library device=/dev/smc0 online=yes
tsm:TSM> define drive autolib drive01 element=82
tsm:TSM> define path tsm drive01 srctype=server desttype=drive library=autolib device=/dev/rmt1 online=yes
tsm:TSM> define drive autolib drive02 element=83
tsm:TSM> define path tsm drive02 srctype=server desttype=drive library=autolib device=/dev/rmt2 online=yes
2. Classify the drives in the library by device type. It is helpful to choose a device class name that identifies the type of device for which it is intended (in this example, AUTOCLASS).
tsm:TSM> define devclass autoclass devtype=8mm format=8500 library=autolib
3. Define a storage pool named AUTOPOOL for the device class.
tsm:TSM> define stgpool autopool autoclass maxscratch=20
Displaying Information About Your Devices
To query the libraries:
tsm:TSM> query library
To query the drives:
tsm:TSM> query drive
To query the paths:
tsm:TSM> query path
To query the device classes:
tsm:TSM> query devclass format=detailed
To query the storage pools:
tsm:TSM> query stgpool
Preparing Tape Volumes with an Automated Library
1. Use the LABEL LIBVOLUME command to label and check in the volumes. From an administrative client command line, begin a search of an automated library named AUTOLIB for unlabeled volumes and label them based on their barcodes:
tsm:TSM> label libvolume autolib search=yes labelsource=barcode
checkin=scratch
2. Define any volumes that are to be used as private volumes.
tsm:TSM> define volume autopool dsm001
Including Tape in the Storage Hierarchy
You can now configure the server so that client data can be migrated to tape. To migrate from BACKUPPOOL to AUTOPOOL and from ARCHIVEPOOL to TAPEPOOL do the following:
tsm:TSM> update stgpool backuppool nextstgpool=autopool
tsm:TSM> update stgpool archivepool nextstgpool=tapepool
Migrating Data from Disk to Tape
Trigger migration from a disk storage pool (BACKUPPOOL, for example) by setting the high and low migration thresholds to 0:
tsm:TSM> update stgpool backuppool highmig=0 lowmig=0
After migration occurs, reset the thresholds to their original settings:
tsm:TSM> update stgpool backuppool highmig=90 lowmig=70
Invoking Expiration Processing
Expired files are not deleted from server storage until expiration processing occurs. You can invoke expiration processing in a number of ways:
The expiration interval server option can specify that processing be invoked at a set interval from the time the server is started. The default is a 24 hour interval.
· You can issue the EXPIRE INVENTORY command manually whenever you wish (see the following example).
· You can schedule the EXPIRE INVENTORY command to be issued regularly at a specific time (see “Automating Administrative Commands” on page 61). If you schedule expiration processing, set the expiration interval server option to 0.(edit dsmserv.sys)
for example:
tsm:TSM> expire inventory quiet=yes wait=no
Automating Administrative Commands
You can automate TSM administrative tasks by scheduling administrative commands. For example, you can automate commands that need to be run regularly or that require significant processing or other system resources. In this section, you define a schedule to run expiration processing.
1. Define a schedule named EXPPROC that invokes expiration processing every night at 2:00 a.m.
This schedule calls for a schedule window that:
· Begins on the date the schedule is defined (the default) at 2:00 a.m.
· Lasts for 1 hour (the default)
· Is repeated every day
· Takes effect immediately
· Stays in effect indefinitely (the default)
tsm:TSM> define schedule expproc type=administrative - cmd='expire inventory' active=yes starttime=02:00 |
|
免费注册
发表于 2005-11-23 11:03
PATH