![]() |
![]() |
Figure 18. Initial Configuration - Completed
After the Initial Configuration completes, you are prompted to verify your configuration. If you have installed a local backup-archive client, click Yes to immediately start the client. Click No if you have not installed the client code locally, or if you plan to verify your configuration by backing up remotely installed clients. See Chapter 5, Verifying the Initial Configuration for verification instructions.
You can use the TSM Console to perform a variety of administrative tasks, including issuing commands and monitoring server processes. You can also access the individual wizards you used during the initial configuration process from this interface. Additional wizards are also available. Refer to TSM Interfaces for information about the TSM Console and other administrative interfaces.
For detailed information about managing your TSM environment, refer to the Administrator's Guide (See TSM Documentation to access this publication.)
The TSM configuration wizards simplify the setup process by hiding some of the detail. For the ongoing management of your TSM system, it can be helpful to understand what has been created for you.
Table 13 lists the default TSM data management policy objects.
Refer to Data Management Policy for an introduction to these objects. For more
information, refer to the chapter on implementing policies for client data in
the Administrator's Guide.
Table 13. Default Data Management Policy Objects
TSM Object | Name | Details |
---|---|---|
Policy Domain | STANDARD | By default, any clients or schedules you created were added to this domain. The domain contains one policy set. |
Policy Set | STANDARD | This policy set is ACTIVE. It contains one management class. |
Management Class | STANDARD | This management class contains a backup copy group and an archive copy group. |
Copy Group (Backup) | STANDARD | This copy group stores one active and one inactive version of existing
files. The inactive version will be kept for 30 days.
Stores one inactive version of deleted files for 60 days. Points to BACKUPPOOL. |
Copy Group (Archive) | STANDARD | This copy group stores one active and one inactive version of existing
files. The inactive version will be kept for 30 days.
Stores one inactive version of deleted files for 60 days. Points to ARCHIVEPOOL. |
Table 14 lists the default TSM storage device and media policy
objects. Refer to Storage Device and Media Management for an introduction to these objects. For more
information, refer to the chapter on managing storage pools and volumes in the
Administrator's Guide.
Table 14. Default Storage Device and Media Policy Objects
TSM Object | Name | Details |
---|---|---|
Storage Pool (Backup) | BACKUPPOOL | This storage pool points to DISKPOOL. No volumes are defined, so
data will migrate immediately.
You might have used the Client Node Configuration Wizard to point BACKUPPOOL directly at a removable media device. |
Storage Pool (Archive) | ARCHIVEPOOL | This storage pool points to DISKPOOL. No volumes are defined, so data will migrate immediately. |
Storage Pool (Disk) | DISKPOOL
(Initial volume is named disk1.dsm) | This storage pool consists of a 4MB volume created in the
tsmdata directory.
You might have used the Client Node Configuration Wizard to point DISKPOOL directly at a removable media device. If so, data will begin to migrate from DISKPOOL to the device when DISKPOOL reaches 90% of capacity. Migration will continue until DISKPOOL reaches 70% of capacity. |
TSM library, drive, storage pool, and path objects will have been created for any storage libraries or drives you defined using the Device Configuration Wizard. TSM volumes will have been created for any media you labeled using the Media Labeling Wizard. If you used the Client Node Configuration Wizard to associate a TSM client with SAN-attached disk, a TSM disk object was also created.
Table 15 lists the default TSM server components. Refer to TSM Server Overview for an introduction to these
components. For more information, refer to the chapters on maintaining
the server and managing the database and recovery log in the
Administrator's Guide.
Table 15. Default Server Components
TSM Object | Name | Details |
---|---|---|
TSM Server | Server1 | By default, the server runs in background mode as a Windows service. The service is set to start automatically when Windows boots. |
TSM Server Database | Initial volume is named db1.dsm. | The server database consists of one 13MB volume (12MB usable space)
created in the ..\tsmdata\server1 directory.
The SPACETRIGGER is set at 80% and EXPANSION at 100%, so when the volume reaches 80% of capacity, a new volume of the same size will be automatically created in the same directory. There is no maximum size specified for the database. The default maximum size is 500GB. There is no backup trigger set for the database. |
TSM Server Recovery Log | Initial volume is named log1.dsm. | The server recovery log consists of one 9MB volume (8MB usable space)
created in the ..\tsmdata\server1 directory.
The SPACETRIGGER is set at 80% and EXPANSION at 100%, so when the volume reaches 80% of capacity, a new volume of the same size will be automatically created in the same directory. There is no maximum size specified for the recovery log. The default maximum size is 5.5GB. |
Table 16 lists the default TSM client components. Refer to TSM Client Overview for an introduction to these
components. For more information, refer to the chapters on managing and
scheduling client operations in the Administrator's
Guide.
Table 16. Default Client Components
TSM Object | Name | Details |
---|---|---|
TSM Client (Local Administrative) | ADMIN | This client is registered with the TSM server by default. It
provides access to the administrative Web interface and server command-line
interface. The default password is ADMIN. To ensure system
security, it is recommended that you change the password.
During the standard configuration process, you are also prompted to create at least one local backup-archive client with the same name as the local machine. |
Client Schedule (Daily) | DAILY_INCR | This schedule is defined in the STANDARD policy domain, so only clients
associated with that domain can use it. You can use the Scheduling
Wizard to associate clients with this schedule. You must also install
and start the client scheduler service on each client node.
The schedule runs a daily incremental backup at the same time you initially configured TSM. The schedule has a window of 2 hours, and a priority of 5. |
Client Schedule (Weekly) | WEEKLY_INCR | This schedule is defined in the STANDARD policy domain, so only clients
associated with that domain can use it. You can use the Scheduling
Wizard to associate clients with this schedule. You must also install
and start the client scheduler service on each client node.
The schedule runs a weekly incremental backup every Friday at the same time you initially configured TSM. The schedule has a window of 1 hour, and a priority of 2. |
Your environment might differ somewhat from the one described in this section, depending on the choices you made during the initial configuration process. All of these default settings can be modified, and new policy objects can be created. Refer to Chapter 6, Getting Started with Administrative Tasks and the Administrator's Guide for detailed instructions.