Re: Archive Log Overflow never empties

2015-01-05 Thread BEYERS Kurt
Good morning,

Regarding the bug in TSM 7.1.1, it is a known apar (IT05164) that is fixed in 
TSM 7.1.1.100, see http://www-01.ibm.com/support/docview.wss?uid=swg1IT05164 
for more details.

Regards,
Kurt

-Oorspronkelijk bericht-
Van: BEYERS Kurt
Verzonden: woensdag 3 december 2014 14:22
Aan: ADSM: Dist Stor Manager
Onderwerp: RE: Archive Log Overflow never empties

Hi everybody,

We are seeing the same behavior on TSM 7.1 on AIX. It occurred once that the 
archive log directory was filled up 80% spawning automated database backups, in 
order to free up the archive log dir, ... until no more scratch tapes were 
available.

It looks like a bug for which an APAR should be raised. I did not find the time 
yet for the latter and just clean up old archive logs by a simple cron script.

regards,
Kurt

Van: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] namens Rhodes, Richard L. 
[rrho...@firstenergycorp.com]
Verzonden: dinsdag 25 november 2014 13:39
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: Re: [ADSM-L] Archive Log Overflow never empties

We are also on 6.2.5 and had this happen once.
I agree, the archive log overflow area does not seem to work as advertised.
I finally just deleted the archive logs in the overflow area after several 
backup.

Rick

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Roger 
Deschner
Sent: Monday, November 24, 2014 8:27 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Archive Log Overflow never empties

We have four instances of TSM Server 6.2.5 on AIX, which basically behave 
pretty well. But on all of them, we occasionally get a little bit of data 
overflowing into the Archive Overflow Log filesystem. I don't know why, because 
as far as I can tell the Archive Log filesystem has never been allowed to fill 
up. But anyway, it never empties out. Full database backups reliably free space 
in the Archive Log filesystem, but the Archive Overflow Log just gradually 
fills up. One of them is up to 20%, over a period of a year. I saw somewhere 
that it takes two full database backups, but there have been many dozens of 
full backups.

Any idea how I can get the Archive Overflow Log to empty out?

Roger Deschner  University of Illinois at Chicago rog...@uic.edu
== You will finish your project ahead of schedule. === 
= (Best fortune-cookie fortune ever.) ==


-

The information contained in this message is intended only for the personal and 
confidential use of the recipient(s) named above. If the reader of this message 
is not the intended recipient or an agent responsible for delivering it to the 
intended recipient, you are hereby notified that you have received this 
document in error and that any review, dissemination, distribution, or copying 
of this message is strictly prohibited. If you have received this communication 
in error, please notify us immediately, and delete the original message.
*** Disclaimer ***
Vlaamse Radio- en Televisieomroeporganisatie
Auguste Reyerslaan 52, 1043 Brussel

nv van publiek recht
BTW BE 0244.142.664
RPR Brussel
http://www.vrt.be/gebruiksvoorwaarden


Re: checkin libv command

2015-01-05 Thread David Ehresman
Here is a script that I picked up at SHARE years ago that lists PRIVATE tapes 
that are not in fact in use:

tsm: ULTSMq script q_lost_tapes f=l

Name   Line   Command
   Number
-- -- 
Q_LOST_TA- 10 select volume_name as Private Tapes NOT in Use -
 PES
   20 from libvolumes -
   30 where status='Private' -
   40 and libvolumes.volume_name not in -
   50 (select volume_name from volumes) -
   60 and libvolumes.volume_name not in -
   80 (select volume_name from volhistory -
   90 where type in ('BACKUPFULL', -
   100'BACKUPINCR', -
   110'DBSNAPSHOT', -
   120'EXPORT'))



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Jeanne 
Bruno
Sent: Tuesday, December 23, 2014 1:28 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] checkin libv command

Hello.  Yes I have one tape as described below.
Private with no last use.  And does not show up with a q drm.

What's the command to re-label the tape?


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Huebner, Andy
Sent: Tuesday, December 23, 2014 12:02 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] checkin libv command

q libv LIBRARY
will show all of the tapes in the library.  If your tape pools use tapes from 
scratch then look for a tape that is private with no last use.  These are 
sometimes orphaned tapes.  You can verify if they are orphaned by q vol and 
searching q drm for the tape.
When I find an orphan I re-label the tape, but be careful, an error can delete 
data.


Andy Huebner


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Jeanne 
Bruno
Sent: Tuesday, December 23, 2014 10:37 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] checkin libv command

Hello.  hhmmm.  I tried status=private.  Results were the same.

I tried:
label libv xx search=yes checkin=scratch labels=b volr=A00560L5,A00561L5 
same results.

Also, the maxscr on all our copy pools are fine. (difference of allowed and 
used is plenty)

I have tried status=bulk in the past, on a tape I had issues with earlier in 
the year, but that tape is just sitting in the library and no backup process 
has ever used it.  So I'm hesitant to use 'bulk'.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Huebner, Andy
Sent: Tuesday, December 23, 2014 10:37 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] checkin libv command

Below is the command I use on my virtual L180 libraries which are SCSI 
libraries.
I think the difference is the volume range.

I do not know the library you have, but some libraries are partitioned and you 
have to make sure the tapes are assigned to the correct partition.

label libv vlibTSM_4 checkin=scr labelsource=barcode volr=s4,s4 search=y

Andy Huebner

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Jeanne 
Bruno
Sent: Tuesday, December 23, 2014 8:39 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] checkin libv command

Hello.  We are using TSM manager 6.3.3.0.
Tape Library is a DS3512.
I'm trying to check in some brand new tapes (LTO Ultrium 1.5TB).
On the DS3512, I choos the library and insert the tape into the machine.
On the command line I use this command:

label libv xx search=yes checkin=scratch labels=b overwrite=y

My output is this:

ANR2017I Administrator ADMIN issued command: LABEL LIBVOLUME  search=yes 
checkin=scratch labels=b overwrite=y ANR0984I Process 120 for LABEL LIBVOLUME 
started in the BACKGROUND at 09:29:14.
ANR8799I LABEL LIBVOLUME: Operation for library XX started as process 120.
ANR8801I LABEL LIBVOLUME process 120 for library XX completed; 0 volume(s) 
labeled, 0 volume(s) checked-in.
ANR0985I Process 120 for LABEL LIBVOLUME running in the BACKGROUND completed 
with completion state SUCCESS at 09:29:19.

0 volumes, but finished successfully and when I query the library XX, the 
new tape does not show in the list.

I have also tried this command:
CHECKIN LIBVOLUME xx SEARCH=YES CHECKLABEL=YES status=scratch WAITTIME=0 
VOLLIST=A00L5.
Results are the same.

I have also tried putting the tapes on the door of the machine and not doing 
the 'insert media'...again results on the same.
We just received 30 new tapes last week and I've tried about 10 of them so far.
I have used the cleaning tape and did the clean process and also rebooted the 
DS3512.same results afterwards.

Any help, suggestions would be greatly appreciated.




Jeannie Bruno
Senior Systems Analyst
jbr...@cenhud.commailto:jbr...@cenhud.com
Central Hudson Gas  Electric
(845) 486-5780


6.3.5.1 TSM server brings new annoyances

2015-01-05 Thread Zoltan Forray
Recently updated all of my TSM Linux servers to 6.3.5.1 and am seeing
2-issues.

The first is related to a RedHat Kernel issue. Originally thought to be
RHEL 6.6  / 2.6 kernel problem but now seems to go back to 6.5 (per the IBM
person I am working with).  The doc is here:

http://www-01.ibm.com/support/docview.wss?uid=swg21691823

The second issue I am seeing is there messages popping up on most if not
all servers.

1/5/2015 2:38:09 PM ANR3497W Reorganization is required on excluded table
BACKUP_OBJECTS. The reason code is 2.

What is the recommended way to resolve this?  I have read some docs and
they talk about doing offline reorgs (no, I do not want to do this).  We
are not doing dedup and all servers are beefy with 48GB+ of memory - most
at 96GB so that should not be an issue.

Suggestions?
--
*Zoltan Forray*
TSM Software  Hardware Administrator
BigBro / Hobbit / Xymon Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html