Re: Determing how much of a tsm server's data is active

with a side-note that this figure includes data that may be excluded from backup. As long as you don't exclude too much, that would be ok. If you have many databases, and/or long exclude lists YMMV. On 18 jul 2011, at 20:42, Richard Sims wrote: > If your clients are doing unfettered incremental

Re: Scalar 50 support TSM 6.2?

http://www-01.ibm.com/software/sysmgmt/products/support/IBM_TSM_Supported_Devices_for_AIXHPSUNWIN.html and more specifically: https://www-304.ibm.com/support/docview.wss?rs=663&uid=swg21273206 On Mon, Jul 18, 2011 at 9:59 PM, lavan wrote: > Hi all > > Scalar 50 tape drives is supported for T

Scalar 50 support TSM 6.2?

Hi all Scalar 50 tape drives is supported for TSM 6.2 ? thanks in advance, velavan +-- |This was sent by rvela...@gmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-

Re: Filespaces appearing for nodes that have never backed up

No Storage Agents. Not doing LAN-free. The PERSIMMON server is a Windoz box. The IP address shown is part of a block of reserved addresses not in use. We don't set HLA/LLA when defining nodes. The other server (WALNUT) whose Domino/TDP backups it is listing, IP address is 128.172.14.87 - whole

Re: Determing how much of a tsm server's data is active

If your clients are doing unfettered incremental backups of file systems, then the following would yield a MB approximation, very quickly: SELECT SUM(CAPACITY*PCT_UTIL/100) FROM FILESPACES which is based upon TSM's information about the file system as gotten from the last client operation.

Re: Filespaces appearing for nodes that have never backed up

On Jul 18, 2011, at 1:21 PM, Zoltan Forray/AC/VCU wrote: > ... >High-level Address: 128.172.184.1 > Low-level Address: 1501 > ... > Note that almost everything is blank, as it should be. However, the > "High-level Address" is not a valid IP address/not assigned to anything

Re: Filespaces appearing for nodes that have never backed up

I believe I've seen similar when the node was renamed. At least in a Windows environment. The filespaces were ID'd with the former name. Maybe a backup did run? Harold Vandeventer Systems Programmer State of Kansas - DISC harold.vandeven...@da.k

Determing how much of a tsm server's data is active

Tsm server 5.5.4. running on Suse linux sles9. I am being asked for how much of my server's data is active data. I have seen the type=allactive and preview=yes in the export node command. Is there a better way? Maybe something like A query to sum file_size in contents for each active object? No

Filespaces appearing for nodes that have never backed up

Recently, I was asked to delete 2-nodes that were accidentally defined and never used. When I tried to remove the node, it said "filespaces exist" When I do a "q filespace", it returns info for a completely different node: 1:12:27 PM SUN : q filespace persimmon.vcu.edu Node Name Filespac

Re: Reporting and BIRT in TSM 6.2

Thanks Christian.. I solved 24 hours in arrears by adjusting the collection and warehouse intervals to more frequent occurrence. Collecting at 15 minutes and warehousing at 1 hour. Your suggestion to go directly to the TSM db2 is good, ALL of the data is there and timely. We sometimes use the

Re: snapdiff advice

We're running 8.0.1P3 on an n6210 gateway, in front of an SVC. The error we get is: >tsm> incr -snapdiff Y: > >Incremental by snapshot difference of volume 'Y:' >ANS2840E Incremental backup using snapshot difference is not supported for Data >ONTAP file server version '0.0.0'. Upgrade the file se

Re: How to script commands at startup

>> On Mon, 18 Jul 2011 11:16:18 -0400, "Pagnotta, Pam (CONTR)" >> said: > Does anyone know how to write a script, or can point me to something > that will issue TSM commands from an administrator session shortly > after the server is restarted? There are several possibilities, none of them par

How to script commands at startup

Hello, We are running version 6.2.2.3(0) on an AIX 6.1 server. We are experiencing issues as described in https://www-304.ibm.com/support/entdocview.wss?uid=swg1IC76984 and have been given three commands that need to be issued right after the TSM server is restarted (they are only good for the

Re: Backup specific folder only

Correction to my previous message - I asked if you really have that many directories in the Oracle dir, when I meant to say do you really have that many other directories on the E: drive? Paul On Mon, Jul 18, 2011 at 8:54 AM, Paul Fielding wrote: > Indeed just using the EXCLUDE as I specified

Re: Backup specific folder only

Indeed just using the EXCLUDE as I specified will grab the directory tree still. It's a longer story, but the Reader's Digest version is that doing so ensure's the TSM BA client GUI can drill down to any given directory to find files you may have backed up. You can't use EXCLUDE.DIR on the "E:\" d

Re: Backup specific folder only

Another solution is to use a customized schedule for this node that targets the desired directory: DEFINE SCHEDULE domain schedname OBJECTS=E:\Oracle\ OPTIONS=-SUBDIR=YES And keep the INCLUDE statement in dsm.opt: Include "E:\Oracle\...\*" 3mth_grp2_MC Best regards, Andy Raibeck IBM Software G

Re: Backup specific folder only

Try the following. Add Exclude.dir e:\dir1 Exclude.dir e:\dir2 . . . For each major tree on the e: drive. This will keep tsm from traversing the trees at all. More administration, but the only thing I can think of. Exclude.dir is processed before standard excludes, therefore you cannot excl