24.12.2012 Views

Backing Up Oracle - Computing at Cornell

Backing Up Oracle - Computing at Cornell

Backing Up Oracle - Computing at Cornell

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

We then edited the dsm.opt client options file using Notepad (Figure 46).<br />

We specified values for COMMMETHOD, TCPSERVERADDRESS,<br />

TCPPORT, NODENAME, and PASSWORDACCESS.<br />

Our TSM server is on an RS/6000 AIX machine with a TCP/IP address of<br />

193.1.1.11 and is listening for client connections on port 1500. Therefore, we<br />

chose TCPIP as our communic<strong>at</strong>ion method, 193.1.1.11 as our TCP server<br />

address, and 1500 as our TCP port.<br />

We used the nodename of JAMAICA th<strong>at</strong> we registered in Section 9.7.1.<br />

We had a choice to set PASSWORDACCESS to PROMPT or to GENERATE.<br />

For ease of management, we chose GENERATE.<br />

Figure 46. Editing the client options file using notepad.exe<br />

Once the dsm.opt client options file has been saved, we can now use the<br />

TSM backup-archive client command line or GUI to perform backups and<br />

archives.<br />

In order to use the TSM scheduling, additional steps are still required. For<br />

scheduling RMAN backups, see Section 11.2.1, “Scheduling TDP for <strong>Oracle</strong><br />

backups” on page 172.<br />

Chapter 9. Install<strong>at</strong>ion of TSM software on Windows 2000 151

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!