Hi Zoltan!
The ACCEPT DATE command should do the trick.
Kind regards,
Eric van Loon
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Zoltan Forray
Sent: maandag 23 juli 2012 16:33
To: ADSM-L@VM.MARIST.EDU
Subject: Changing server time
We accident
Maybe the upgrade will take as long as unloading/loading but you're in a
better position than staying on 5.5.
Groetjes,
Oscar
Butterfly Software Limited
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Loon, EJ van - SPLXO
Sent: 27 June 2012 1
Hi Rick!
Thanks for your reply! Here are my answers, please bear in mind that I'm
not an AIX expert.
Is AIX waiting on disk I/O? (I/O wait state)
Vmstat shows wa=9
Is AIX CPU running hard?
According to topas dsmserv is top user with an average below 3%...
What does iostat s
Hi TSM-ers!
My TSM databases are running for quite a while (since 4.1) and they are
becoming rather fragmented, one of them more that 25%! It becomes
noticeable too, expiration is running longer and longer.
Our TSM servers are all running in AIX 5.3 on a P-series 570, SAN
attached to a VMAX (OS, DB
ttachments and notify the sender immediately
>
> -----Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf
Of
Loon, EJ van - SPLXO
> Sent: Thursday, March 29, 2012 3:31 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: RFE 17805
>
> Hi Remco!
ny
attachments and notify the sender immediately
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf
Of
Loon, EJ van - SPLXO
> Sent: Thursday, March 29, 2012 3:31 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: RFE 17805
>
> Hi Remco!
&
Hi Remco!
I totally agree!
In our shop we had to create a dedicated server to enable backups in
case of a disaster. It contains a standby primary pool with 500 tapes,
just sitting there, costing money. This pool is located on the remote
location and is readonly. When the primary pool is lost, we ha
61 30 NORRTÄLJE
-"ADSM: Dist Stor Manager" skrev: -
Till: ADSM-L@VM.MARIST.EDU
Från: "Loon, EJ van - SPLXO"
Sänt av: "ADSM: Dist Stor Manager"
Datum: 02/16/2012 16:19
Ärende: Re: Expiration performance TSM 5.5 (request)
Hi Daniel!
Been there, done that...
a)
ist Stor Manager" skrev: -----
Till: ADSM-L@VM.MARIST.EDU
Från: "Loon, EJ van - SPLXO"
Sänt av: "ADSM: Dist Stor Manager"
Datum: 02/16/2012 15:02
Ärende: Expiration performance TSM 5.5 (request)
Hi TSM-ers!
I'm struggling with the performance of our expiration process.
phone: 765-285-1310
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Loon, EJ van - SPLXO
Sent: Thursday, February 16, 2012 9:02 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Expiration performance TSM 5.5 (request)
Hi TSM-ers!
I'm strugglin
Hi TSM-ers!
I'm struggling with the performance of our expiration process. I can't
get it any faster than 100 object/second max. We tried everything, like
using more or less database volumes, multiple volumes per filesystem,
mirroring, unmirroring, but nothing seems to have any positive effect.
We
Hi Geoff!
Welcome back! I hope you will find a suitable TSM job soon!
Kind regards,
Eric van Loon
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Geoff
Gill
Sent: woensdag 14 december 2011 15:51
To: ADSM-L@VM.MARIST.EDU
Subject: Old friends and
Hi Sascha!
Indeed this sounds strange. I can imagine that the delete filespace pins
the log, which causes the log to grow, but as soon as you cancel the
delete filespace, the pinning should be gone and thus the log
utilization should be back to 0.
This only proves my point: I have a PMR open for mo
That Eric is me!
Just kidding, a long time ago someone from IBM told me Eric was the name
of the son of one of the first ADSM developers.
Kind regards,
Eric van Loon
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Allen S. Rout
Sent: woensdag 2 n
be contacting you to work the PMR.
Dave Canan
IBM ATS TSM Performance
ddcananATUSDOTIBMDOTCOM
916-723-2410
On Thu, May 12, 2011 at 7:53 AM, Loon, EJ van - SPLXO
wrote:
> Hi Rick!
> You are running in normal mode. In this mode the recovery log only
> contains uncommited transactions. Don&
e contacting you to work the PMR.
Dave Canan
IBM ATS TSM Performance
ddcananATUSDOTIBMDOTCOM
916-723-2410
On Thu, May 12, 2011 at 7:53 AM, Loon, EJ van - SPLXO
wrote:
> Hi Rick!
> You are running in normal mode. In this mode the recovery log only
> contains uncommited transactions. Don
as
one of the many indications that we needed more instances. It's also
why
we have a daily report of slow and long running backups so we can
identify
these problem servers.
Rick
From: "Loon, EJ van - SPLXO"
To: ADSM-L@VM.MARIST.EDU
Date: 05/12/2011 10:54 AM
Su
TSM v6 then its time for you to start planning your move to something
else. Support for TSM 5 will be dropped sometime and I suspect the move
from TSM to something else will take some planning.
David
>>> "Loon, EJ van - SPLXO" 5/12/2011 8:56 AM
>>>
Hi Steve!
If it w
ut the obvious here, but if you really can't afford to move
> to TSM v6 then its time for you to start planning your move to
something
> else. Support for TSM 5 will be dropped sometime and I suspect the
move
> from TSM to something else will take some planning.
>
> David
>
>
_
Van: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] namens Loon, EJ van
-
SPLXO [eric-van.l...@klm.com]
Verzonden: donderdag 12 mei 2011 11:11
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
Hi Paul!
We are already r
rver and restart in order to get
>> things
>> back to normal.
>>
>> IBM recognized this as an issue and recommended going to any 5.5.5.0
>> level
>> of code, where the problem was supposed to be fixed. I installed
>> 5.5.5.2,
>> and the problem has in
d a backup piece size (I believe it's called MAXPIECESIZE if I
remember correctly) in RMAN.
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: Steve Roder [mailto:s...@buffalo.edu]
Sent: donderdag 12 mei 2011 13:53
To: Dist Stor Manager
Cc: Loon, EJ van - SP
low sessions will be completed till log utilization reaches
95%?
Grigori G. Solonovitch
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Loon, EJ van - SPLXO
Sent: Thursday, May 12, 2011 12:11 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Rec
supposed to be fixed at
5.5.5.0, though perhaps they didn't quite get it done at that code level
as
they hoped? I'd try installing 5.5.5.2 and see what happens
regards,
Paul
On Wed, May 11, 2011 at 9:03 AM, Loon, EJ van - SPLXO
wrote:
> Hi Robert!
> Thanks you very much for
an hour.
Asking the users of SQL LiteSpeed to make some changes was enough to
rememdy this problem, although we continue to fight with the logs
getting
full.
Thanks,
[RC]
From: "Loon, EJ van - SPLXO"
To: ADSM-L@VM.MARIST.EDU
Date: 05/11/2011 02:05 AM
Subject:Re
Hi TSM-ers!
Here is a small follow up on my PMR about the recovery log utilization.
I'm at TSM level 2, still trying to convince them that there is
something broken in the TSM server code. To convince them, I have
changed the logmode to normal on one of my servers. I created a graph
(through TSMMan
. When it happens, It's usually caused
by
a slow
running backup of a large object. In other words, a single transaction
that runs a long time. We have monitoring scripts running that issue
a "show login cancel" if our log reaches 90%.
Rick
From: "Loon, EJ van - SPLXO&
rity number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html
<http://infosecurity.vcu.edu/phishing.html>
From:
"Loon, EJ van - SPLXO"
To:
ADSM-L@VM.MARIST.EDU
Date:
04/20/2011 11:39 AM
Subject:
Re: [ADSM-L] TSM Recovery log is
e 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
<http://infosecurity.vcu.edu/phishing.html>
From:
"Loon, EJ van - SPLXO"
To:
ADSM-L@VM.MARIST.ED
mors
Enterprise Systems
HealthNow, NY
716-887-7979
From:
"Loon, EJ van - SPLXO"
To:
ADSM-L@VM.MARIST.EDU
Date:
04/20/2011 04:50 AM
Subject:
Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code
Sent by:
"ADSM: Dist Stor Manager"
Hi TSM-ers!
I too upgraded m
Hi TSM-ers!
I too upgraded my servers to 5.5.5.2 and the log is still filling up to
fast. During last nights backup window, three incrementals were
triggered by the db backup trigger. My log is set to 12Gb with the
trigger at 75%.
I will open a PMR too for this and again, I urge everybody else too
Oh my god!
I really thought I was the only one fighting the logpinning issue! My
database is filled up to 80% or more at least 20 times a day and all the
triggered incrementals have made me running out of scratches multiple
times. This very weekend our standby was called again because the
r
mirroring? Not sure if you are using AIX or
something else.
Thanks.
..Paul
At 05:00 AM 11/29/2010, Loon, EJ van - SPLXO wrote:
>Hi TSM-ers!
>Just to let you all know, I have found several things to speed up the
>auditdb. We have turned of logical volume mirroring on the LV
containing
&g
Hi Keith!
Been there, done that! During that run the auditdb finds errors and
fixes them, but as soon as you start a second run, the audit finds the
exact same errors. So although TSM says it fixes the errors, it doesn't.
When I run a full audit and a second run afterwards, the second one no
longer
day one and the auditdb on day two.
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Loon, EJ van - SPLXO
Sent: Thursday, November 18, 2010 5:44 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L
Hi TSM-ers!
On several larger SQL Servers the full backup fails every now and then
with the following error:
ACO5436E A failure occurred on stripe number (0), rc = 418
ANS1017E (RC-50) Session rejected: TCP/IP connection failure
The server log shows no additional information.
The only thing I ca
now where to find me ;-)
Regards,
Maurice van 't Loo
2010/11/18 Loon, EJ van - SPLXO :
> Hi TSM-ers!
> We're having orphaned database entries, caused by a very old bug, fixed
> some server releases ago, but only recently discovered. I'm currently
> trying to find a way
Hi TSM-ers!
We're having orphaned database entries, caused by a very old bug, fixed
some server releases ago, but only recently discovered. I'm currently
trying to find a way to speed-up the auditdb performance.
What I'm planning to do is this:
1) backup the database on our production server
2) sto
Hi Bill!
Just out of curiosity, why do you exclude large files from dedup? When
for example a large PST file changes, probably only a small portion of
the file changes, so the rest of the file should be 'deduplicatable',
right?
Kind regards,
Eric van Loon
-Original Message-
From: ADSM: Dis
ed-platforms
____
Från: Loon, EJ van - SPLXO [eric-van.l...@klm.com]
Skickat: den 5 oktober 2010 15:19
Till: ADSM-L@VM.MARIST.EDU
Ämne: Backing up Debian 5.0 client
Hi TSM-ers!
I know the Linux client is only supported on SLES and Redhat, but one of
my customers has
Hi TSM-ers!
I know the Linux client is only supported on SLES and Redhat, but one of
my customers has a Debian 5.0 server he would like to backup to TSM. Is
this at all possible?
Thanks in advance for any reply, help and/or tips!
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines
Hi Richard!
I read somewhere that this is on the future features list. I'm currently
sticking to TSMOR for this reason.
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard van Denzel
Sent:
ice 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://infosecuri
Hi TSM-ers!
This is my TSM shop:
3 TSM 5.5.4 servers, running on a AIX 5.3 cluster.
Server 1 is receiving about 3 Tb of backup data daily, contains 458
client nodes, DB size is 58 Gb, logsize is 12 Gb.
Server 2 is receiving about 3.5 Tb of backup data daily, contains 781
client nodes, DB size is 9
44 matches
Mail list logo
