If your tapes have been marked UNAVAILABLE because they were temporarily
unavailable to TSM for whatever reason, but are otherwise undamaged and
available, you could use SET VOLUME ... ACCESS=READWRITE to get them back. -
Margaret
-Original Message-
From: ADSM: Dist Stor Manager
As one data point: we always set TDP client passwords to never expire. -
Margaret Clark
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Tuesday, April 30, 2013 8:00 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Client
We saw RC=1819 when the scheduler was started using the local system account,
and the local system account did not have access to the Exchange system.
- Margaret
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bill
Boyer
Sent: Tuesday, January
, remember that the account used for the scheduler has to be a member of
the Exchange Security Group Organization Management, which in our case is a
security group in our root domain.
~Rick
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Clark
We run snapdiff backups using 6.2.4 client, 6.2.3.1 server, Ontap 7.3.3, and
exclude and exclude.dir work as expected. - Margaret
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Monday, December 03, 2012 10:38 PM
To:
We have been using NetApp storage for TSM primary disk pools for about a year
now.
The only problem we experienced was when we first configured the storage, and
it did not mount automatically after a reboot. (It does now.)
It isn't obviously slower than the attached storage, but since we must
Well, since you asked for any suggestions...
It seems to me you could get this report using a command like
select archive_date,filespace_name from archives a,file_name from contents c
where archive_date = current_timestamp - 1 days and a.node_name = c.node_name
and a.filespace_name =
[mailto:r...@bu.edu]
Sent: Thursday, July 12, 2012 11:00 AM
To: Clark, Margaret
Subject: Re: Select or Query help
On Jul 12, 2012, at 1:41 PM, Clark, Margaret wrote:
...
P.S. HL_NAME and LL_NAME are not what you need... those are the IP address
and port number for a client.
Hi, Margaret
Using TSM server 6.2.3.1, the following SQL command no longer works:
select node_name from nodes where node_name not in (select node_name from
filespaces)
It still works correctly if you take out the not.
Any ideas?
- Margaret
of the word NOT could be construed as an unexpected
result. You might retry using the AS keyword. This particular problem is
listed as fixed in 6.2.4.0.
Alex
On 6/21/2012 9:55 AM, Clark, Margaret wrote:
Using TSM server 6.2.3.1, the following SQL command no longer works:
select node_name from
What you show here is not a log of files being backed up, but being expired.
If you had just modified the options file to add the exclusion, you'd see a log
like this.
If that's the case, then check the log again tomorrow.
- Margaret
-Original Message-
From: ADSM: Dist Stor Manager
We had this back in February, when a reorg deadlocked with a migration.
Get help right away, and while you're waiting, check APAR: IC81261
- Margaret
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Vandeventer, Harold [BS]
Sent: Monday, April
Yes, we are. We use a VM to run the TIP (administration center) and the old
Operational Reporting. No problems. - Margaret
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Vandeventer, Harold [BS]
Sent: Friday, April 06, 2012 11:18 AM
To:
We have applied a similar fix, and it not only speeds up the database backups,
but inventory expiration as well.
- Margaret
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Lamb,
Charles P.
Sent: Tuesday, March 20, 2012 7:58 AM
To:
While we were running 6.2.2.0, we had one unpleasant occasion when the tape
drives started dropping offline one by one, and then I was unable to connect to
the server to log in.
The Linux admins said the error message indicated that the AIX box had run
itself out of memory, and recommended that
A few additional comments (things we found out the hard way):
For Data Protection for Exchange to work, the TSM Client Agent must be
installed.
The *TDP clients need to be set up using USERID=NONE, after which we set the
proxy access using server commands like this:
register admin
This works on 6.2.3.1:
select volume_name,stgpool_name,access,pct_utilized,est_capacity_mb,
cast(day(current_timestamp-last_write_date) as decimal) as Days,
status,access,last_write_date,substr(char(last_write_date),1,19) as Last
Write from volumes
where status='FILLING' and
We upgraded to server 6.2.3.1 in January, and database backup times got a lot
worse; half-hour DB backups increased to a minimum of 40 minutes, with one in
four taking 3-4 hours or more.
When we upgraded, we took the default REORGBEGINTIME 6, REORGDURATION 24.
We subsequently reduced the
Should have mentioned: we upgraded to AIX 6.1 TL 7.1 at the same time as the
upgrade to TSM server 6.2.3.1.
We upgraded to AIX 6.1 TL 7.0 on Jan 12th, and of eleven database backups
before adding the 7.1 patches, two were exceptionally long - unprecedentedly
long at that time, between 5 and 6
performed the AIX migration from V5.3.12.3 to V6.1.7.3.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Clark,
Margaret
Sent: Thursday, March 01, 2012 2:09 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Slow TSM DB Backup
Should have mentioned: we
Do the backups actually fail? We used to get messages like this (before
upgrading to 6.2.3.1 server) but not on successive nights, and no backups
failed.
It's a warning, not an error message; when we had them, it looked to me as if
the warning was given whenever the password had to be updated.
Check the account that is used to run the client acceptor (or scheduler if the
client acceptor service is not used). It that account does not have the
appropriate privileges, you will see this behavior.
- Margaret
-Original Message-
From: ADSM: Dist Stor Manager
It would be helpful if snapdiff backups updated the BACKUP_START field, even if
we have to resign ourselves to nothing recorded as BACKUP_END.
Is there a reason why that can't be done?
- Margaret Clark
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On
The reason we use snapdiff is to avoid walking the file system. Running a
periodic 'createnewbase' is just not going to happen. We're just stuck with no
time stamp. - Margaret Clark
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Paul
You doubtless checked the DNSLOOKUP option, and set it the same way on all your
servers.
Is it possible that the DNS for the problem client is also the only DNS that is
also behind the firewall? - Margaret
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU]
Hi, Carol. I had hoped to be able to tell you today whether or not our problem
of TSM snapshots being left behind had been fixed by the 6.2.4 client.
Unfortunately the FAS administrator was out yesterday, so the leftover
snapshots were not cleared before last night's backup.
He has cleaned up
How about this?
DELete VOLHistory TODate=TODAY-8 Type=REMOTE VOLUME=TE0105 FORCE=YES
- Margaret
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Roger
Deschner
Sent: Thursday, October 06, 2011 2:37 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L]
I have observed that for primary storage pools where the tape volumes have been
DEFINEd to belong to that pool, MOVE DATA to consolidate tapes belonging to the
same collocation group has unexpected results. The database reliably selects
the volume copied FROM as the primary candidate for the
Back in March, I watched a recorded presentation about DB2 reorgs within TSM
server 6.2.2.0, and discovered that OnTap will only allow snapdiff backups to
work correctly with releases 7.3.3 and 8.1, NOT 8.0. Apparently OnTap 7.3.3
and 8.1 contain the File Access Protocol (FAP), but 8.0 does
We had a somewhat similar problem almost a year ago, which was caused by
Windows 2008 TSM clients older than the 6.2 release:
IC66810: 6.1.2 AND 6.1.3 TSM WINDOWS CLIENTS WITH DEFAULT SYSTEM STATE WRITERS
ON WIN 7 AND 2008 R2 MAY GET FULL SYSTEM STATE BACKUPS
The problem went away when the
@VM.MARIST.EDU] On Behalf Of
Clark, Margaret
Sent: Wednesday, March 16, 2011 6:03 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Scripts Doubling up
Not on our 6.2.2.0 server, it doesn't! - Margaret
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf
Syscat columns doesn't show a STATUS in the PROCESSES table any more. -
Margaret Clark
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Howard
Coles
Sent: Tuesday, March 15, 2011 6:51 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Scripts
, a select * from processes does show a STATUS field.
David
Clark, Margaret mcl...@sddpc.org 3/16/2011 2:52 PM
Syscat columns doesn't show a STATUS in the PROCESSES table any more.
- Margaret Clark
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf
We have been on TSM server 6.n since August 21st 2009, currently at 6.2.2.0.
Our oldest clients are at 5.1.5.0; we have several clients at 5.3.2.0 and
5.3.4.0.
None of them has had a problem.
- Margaret Clark
-Original Message-
From: ADSM: Dist Stor Manager
When we started using snapdiff backups, the documentation said it was
compatible with any release of OnTap above 7.2.
We committed to using snapdiff with our OnTap 7.3.3 FAS, and by using the
arcane options TESTFLAG SNAPDIFFONTAPFAP and
TESTFLAG SNAPDIFFNAMEFILTEROFF, it mostly worked. We
backup with the option createnewbase set to yes.
-
Cameron Hanover
chano...@umich.edu
Necessity is the plea for every infringement of human freedom. It is the
argument of tyrants; it is the creed of slaves.
--William Pitt, House of Commons, 11/18/1783
On Dec 14, 2010, at 10:40 AM, Clark
.
Frank Ramke
TSM Development
From: Clark, Margaret mcl...@sddpc.org
To: ADSM-L@vm.marist.edu
Date: 12/14/2010 10:39 AM
Subject:Snapdiff with 6.2.2.0 client
Sent by:ADSM: Dist Stor Manager ADSM-L@vm.marist.edu
When we started using snapdiff backups
No idea about ANR4724E, but has the client's network connection been set to
auto-negotiate? That would account for the extended execution time.
- Margaret Clark
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nick
Andrelli
Sent: Thursday,
I bet you've got a lot of little files on at least one of the drives. The
three hours is used comparing all those little darlings with the TSM server's
idea of things, before anything gets backed up at all. - Margaret Clark
-Original Message-
From: ADSM: Dist Stor Manager
A bit late, but I don't recall any previous responses to this... It will do no
good to cancel a running expiration process. When you start again, expiration
picks up exactly where it left off. Trying to cancel it just prolongs the
agony.
No idea about the retries, sorry.
- Margaret Clark
It's not very clear, is it? You need Administrative Schedules on the Server
Properties page. - Margaret
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Timothy Hughes
Sent: Wednesday, June 02, 2010 8:38 AM
To: ADSM-L@VM.MARIST.EDU
Subject:
I have seen this in the past, when the server was very busy and did not respond
to Operational Reporting queries in a timely fashion.
The Operational Report would run successfully if submitted manually a little
later.
- Margaret Clark
Systems Programmer
San Diego Data Processing Corporation
Policy domains view policy domains modify policy domain client node
schedules modify schedule client nodes associate client node
- Margaret Clark
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Timothy Hughes
Sent: Wednesday, May 19,
5.4.0.2 was the last release that could be installed on Windows 2000. It
works. - Margaret
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of ADSM-L
Sent: Tuesday, May 18, 2010 6:35 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Windows 2000
Thomas Denier wrote: We have always been able to clean this up by removing
and recreating the service. We did not need to deinstall the client software or
manually remove registry keys.
That's fine as long as the client releases are relatively recent. Somewhere in
the client history, TSM
Did that package ever get refreshed? The FTP site shows nothing later than 8th
March. - Margaret Clark
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Andrew
Raibeck
Sent: Wednesday, March 10, 2010 5:16 PM
To: ADSM-L@VM.MARIST.EDU
Subject:
Fixing the dsm.opt may not be enough. When Windows nodes are cloned with the
TSM client in place, the registry will cause this interesting behavior even
after the dsm.opt is updated.
I've found I have to deinstall the TSM client and then delete the ADSM subkey
.
From:
Clark, Margaret mcl...@sddpc.org
To:
ADSM-L@VM.MARIST.EDU
Date:
10/26/2009 05:00 PM
Subject:
Re: [ADSM-L] Problems with new install of V6.1.0.2 client on Windows 2008
x64 system
Sent by:
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
I've seen the same thing, when the client had an old version
client versions.
From:
Clark, Margaret mcl...@sddpc.org
To:
ADSM-L@VM.MARIST.EDU
Date:
10/26/2009 05:00 PM
Subject:
Re: [ADSM-L] Problems with new install of V6.1.0.2 client on Windows 2008
x64 system
Sent by:
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
I've seen the same thing, when the client
I've seen the same thing, when the client had an old version of Java loaded.
- Margaret Clark
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Zoltan
Forray/AC/VCU
Sent: Monday, October 26, 2009 6:30 AM
To: ADSM-L@VM.MARIST.EDU
Subject:
So do tell, Richard: what do we do to change the date and time format now?
I've been hunting for the instructions without success. - Margaret Clark
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard Sims
Sent: Monday, October 12, 2009
I suppose you've tried DELETE VOLUME T00015 DISCARDDATA=YES ?
- Margaret Clark
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Allen
S. Rout
Sent: Tuesday, September 15, 2009 11:34 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] rarely, tapes
Did you try deleting by FSID? Laborious, but it works when other methods
fail... e.g. (for filespace 1): DELETE FILESPACE KL10143J 1 NAMETYPE=FSID
- Margaret Clark
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Loon,
EJ van - SPLXM
You could try replacing date(backup_end) = current_date -2 days with
cast((current_timestamp-backup_end)days as decimal)2 - Margaret Clark
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Moyer,
Joni M
Sent: Wednesday, August 05, 2009 6:27 AM
Carol Trible wrote: It seems that long term customers tend to stick to the
command line, but new customers who start with the Administration Center like
it, so I would reccomend giving it a try.
I started administering TSM in 2006, and my first task was to install the
Administration Center for
If there's nothing in the filespace that you need to keep, you can try this:
delete filespace WHQ_FILESERV_1 2 nametype=FSID
I've also been unable to delete filespaces using the filespace name, or indeed
display them using the Admin Center, but I've been successful using the FSID.
- Margaret
Richard Sims pointed out the discrepancy between midnight and noon in your
apparent scheduled start times, which is certainly worrying.
I also notice that your scheduler is not starting up until almost 25 minutes
after the scheduled start time. Why is that?
If your startup window is short (say,
I hope it works for you. We recently upgraded to 5.5.1 server on a z/OS
platform, after which most of our scheduled backups failed, apparently because
of some perceived discrepancy found by reverse lookup.
We added the DNSLOOKUP NO parameter as suggested by IBM support (it is
undocumented for
We are using 5.4.1 server and have twenty-five clients at the 5.1.5 level or
worse that are doing just fine.
- Margaret Clark, San Diego Data Processing Corporation
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Paul
Zarnowski
Sent: Thursday,
My favorite is the customer who believes their every backup is on their own
private tape, and will we just send it to them?
- Margaret Clark, San Diego Data Processing
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Curtis
Preston
Sent: Monday,
60 matches
Mail list logo
