TSM client steps for scheduling

Once the schedule has been defined on the TSM server, and the schedule has been associated with the nodename, the only thing left to do is set up a scheduler service.

We want to use a different scheduler service for the TDP for Oracle backups to make it easier to check whether the commands executed. In our Windows environment, we chose scheduling mode client polling.

If you have more than one scheduler service on a machine and you are using server prompted scheduling mode, you MUST specify the TCPCLIENTPORT option in one of the scheduler service’s to be different from the default.

Otherwise, both services will try to listen on the same port.

The TSM backup archive client provides a wizard to assist with installing a scheduler service. We chose to use the command line utility dsmcutil.exe located in the ...\baclient directory. In order to keep this service separate from the backup client scheduler service, you must specify options for NAME, NODE, PASSWORD, OPTFILE, SCHEDLOG, and ERROR.LOG.

If you do not use different values for SCHEDLOG and ERROR.LOG, both scheduler services will write to the same log files:

tsm: BRAZIL>define schedule api_domain backup_offline action=command object="c:\oracle\admin\scripts\autorman.cmd backup_offline_beach"

ANR2500I Schedule BACKUP_OFFLINE defined in policy domain API_DOMAIN.

tsm: BRAZIL>define association api_domain backup_offline jamaica_oracle ANR2510I Node JAMAICA_ORACLE associated with schedule BACKUP_OFFLINE in policy domain API_DOMAIN.

C:\Program Files\Tivoli\TSM\baclient>dsmcutil install /name:"TSM Scheduler Oracle"

/node:"jamaica_oracle" /password:"jamaica_oracle"

/optfile:"c:\progra~1\tivoli\tsm\agentoba\dsm.opt"

/schedlog:"c:\progra~1\tivoli\tsm\agentoba\dsmsched.log"

/errorlog:"c:\progra~1\tivoli\tsm\agentoba\dsmerror.log"

After running that command, a number of messages are sent to the console.

This will let you know if there are any errors. The most important ones to see are the following:

If you make a mistake, you can easily remove the scheduler service by specifying dsmcutil remove /name:”Name of Scheduler Service”.

You can check which scheduler services are installed with dsmcutil list:

To verify the settings and configuration of our scheduler, we used the command, dsmcutil query /name:”Name of Scheduler Service”.

The service was successfully installed.

Starting the 'TSM Scheduler Oracle' service ...

The service was successfully started.

C:\Program Files\Tivoli\TSM\baclient>dsmcutil list

Installed TSM Client Services:

1. TSM BAClient Scheduler 2. TSM Scheduler Oracle

C:\Program Files\Tivoli\TSM\baclient>dsmcutil query /name:"TSM Scheduler Oracle"

Service Name : TSM Scheduler Oracle Logon Account : LocalSystem

Start Type : Demand Current Status : Started

TSM Client Service Registry Settings:

Client Service Type = Client Scheduler Service

Client Directory = "C:\Program Files\Tivoli\TSM\baclient\dsmcsvc.exe"

Options file = c:\progra~1\tivoli\tsm\agentoba\dsm.opt Event Logging = YES

TSM Client Node = JAMAICA_ORACLE

Comm Protocol = (value not currently set) Server = (value not currently set) Server Port = (value not currently set)

Schedule Log = c:\progra~1\tivoli\tsm\agentoba\dsmsched.log Error Log = c:\progra~1\tivoli\tsm\agentoba\dsmerror.log MSCS Enabled Node = (value not currently set)

Cluster name = (value not currently set)

Chapter 11. Day-to-day monitoring on Windows 2000 175 Upon successful installation of the scheduler service, the scheduler service will automatically start and connect to the TSM server to retrieve any

associated schedules. The dsmsched.log for the scheduler service will show whether a schedule was retrieved from the TSM server. Our dsmsched.log shows that the c:\oracle\admin\scripts\autorman backup_offline_beach will be executed in 2 minutes.

We checked the dsmsched.log and it said that the command failed. We checked the backup_offline_beach.log file and it gave us this message:

That message would lead you to believe that the password in the AUTORMAN.CMD file was incorrect. However, we had previously run it manually and it was successful. The most common cause of a scheduled action failing when the manual action works in Windows is that the scheduler service is running as an account that does not have sufficient rights. We stopped the scheduler service:

net stop “TSM Scheduler Oracle”

Then, using Administrative Tools -> Services, we changed the logon type for the scheduler service from system account to the Administrator account. You should be able to use any account that is successful in running the command manually.

04/05/2001 23:06:09 Querying server for next scheduled event.

04/05/2001 23:06:09 Node Name: JAMAICA_ORACLE

04/05/2001 23:06:09 Session established with server BRAZIL: AIX-RS/6000 04/05/2001 23:06:09 Server Version 4, Release 1, Level 2.0

04/05/2001 23:06:09 Server date/time: 04/05/2001 21:07:36 Last access: 04/05/

2001 21:05:30

04/05/2001 23:06:09 --- SCHEDULEREC QUERY BEGIN 04/05/2001 23:06:09 --- SCHEDULEREC QUERY END 04/05/2001 23:06:09 Next operation scheduled:

04/05/2001 23:06:09 Server Window Start: 21:06:13 on 04/05/2001

04/05/2001 23:06:09 ---04/05/2001 23:06:09 Command will be executed in 2 minutes.

RMAN-00554: initialization of internal recovery manager package failed RMAN-04005: error from target database: ORA-01017:

invalid username/password; logon denied

Figure 55. Changing the scheduler service to use a different account

We then updated the TSM schedule backup_offline_beach so that it would run again:

update schedule api_domain backup_offline_beach starttime=now

Then we started the scheduler service:

net start “TSM Scheduler Oracle”

Once again, the dsmsched.log said that the command would execute in 2 minutes.

So, 2 minutes later, we checked the dsmsched.log again and saw that this time it successfully executed the command.

Chapter 11. Day-to-day monitoring on Windows 2000 177

11.3 RMAN report, list, and crosscheck utilities

RMAN can generate reports about backups and images copies with the report, list and crosscheck commands

The report command can produce the following types of information from the recovery catalog:

• The database schema

• Which data files require a backup

• Backup files that are obsolete and can be deleted • Data files that are not recoverable

The list command queries the recovery catalog and produces information such as:

• List of backup sets containing a backup of a specific data file • List of backup sets containing backups for a specific tablespace • List of backup sets containing backups for the whole database The crosscheck command queries the recovery catalog and verifies, whether backup sets marked available or expired are available.

• For objects stored on disk (type disk): the command determines whether the header of the backup piece is valid

• For TSM objects (type sbt_tape): the command simply check that the backups exist

You would want to use this utility regularly to verify if your backup is still available.

Below are examples of how you can use these utilities to perform day-to-day monitoring. For the complete syntax of these utilities, please refer to the Oracle 8i Recovery Manager User’s Guide and Reference, A76990-01.

04/05/2001 23:15:46

Executing Operating System command or script:

c:\oracle\admin\scripts\autorman backup_offline_beach 04/05/2001 23:21:14 Finished command. Return code is:

0

04/05/2001 23:21:14 Scheduled event 'BACKUP_OFFLINE_BEACH' completed successfully.

04/05/2001 23:21:14 Sending results for scheduled event 'BACKUP_OFFLINE_BEACH'.

04/05/2001 23:21:14 Results sent to server for scheduled event 'BACKUP_OFFLINE_BEACH'.

11.3.1 Report utility

The ^report utility provides analysis of your backup and recovery situation.

Below are examples of the ^report utility.