Search:

Quick follow up...

Can I do the same with UNC paths? For example,

domain "\\servername.uchicago.edu\main-path"
exclude.dir "\\servername.uchicago.edu\main-path\subdir1"
exclude.dir...

All,

I am backing up a NAS share via a proxy node. The problem I'm having is that the primary share has 140 directories. They only want to back up 20 of these directories. The only way I see is...

Yea, just caught that... Did get the following:

tsm: TSMZWEI>select schedule_name cast(SUBSTR(CHAR(actual_start),12,8) as char(8)) AS START,node_name, cast(status as char(10)) as "STATUS", case...

What are the red smily faces supposed to be? :-)

Problem is the list is HUGE. The only other way I thought of was either splitting into separate schedules within the same domain.

For example, I can run a select to show me a list of nodes that have a common contact:

select node_name from nodes where contact like 'Windows_Group%'

But then I want to run a query event log...

q sess is fine. Says three sessions (matching the maxnump), it's more watching the console go by and the session numbers incrementing by 1 300 times. Seems to only happen on TDP for database nodes

Node Name: PINATUBO-DB
Platform: TDPO Linux86-64
Client OS Level: 2.6.18-308.8.1.el5
Client Version: Version 6, release 3, level 0.0

They start, and immediately end, repeat, repeat, etc... about 300 times. In example,

06/27/2012 16:14:36 ANR0403I Session 1660 ended for node PINATUBO-DB (TDPO
...

All,

I have a TDP node that logs about 200 sessions for 4 databases on one node. The maxnump=3 and the keepmount=no. Is this normal?

Can someone show me a SQL statement to show the ll_name that is greater than 200GB in size?

Thanks Chad ! Worked like a charm. Do you know of a more detailed website than Lascon for pre-defined scripts for TSM 6.2.3 reporting? Or, better yet, has anyone used TCR?

I need a select statement that shows me a list of node_name from nodes that have NOT backed up in 30+ days. The script I had that was functional for TSM 5.5.52 does not work for TSM 6.2.3. I looked...

All,

I thought this would be a basic restore, but it appears more complex than I thought. And since I don't know TSM as well as I thought, I hope to get some help. We have a large filesystem...