-How long have you been at 6.3.4.0? I've seen this on slightly older servers
-when Windows 2008 Server clients (and similar era Windows desktop, from what I
-hear) back up their system states. You get huge numbers of small objects, and
-expiration takes a long, long time to process those with no ob
How long have you been at 6.3.4.0? I've seen this on slightly older servers
when Windows 2008 Server clients (and similar era Windows desktop, from what I
hear) back up their system states. You get huge numbers of small objects, and
expiration takes a long, long time to process those with no obv
I saw a similar behavior on my 6.3.3.100 on Windows earlier this week.
Expiration appeared to be stuck for a couple of hours having processed only 10
or 15 nodes of 200.
Do you have a duration specified to limit time? That might explain your 462 of
595.
I had also tried to cancel, and also di
I have an AIX server with TSM 6.3.4.0. Expiration is set to run at 2am and
seems to get so far and then hangs. But what's odd is that is also seems to
only process some of the nodes but not all. For example, I have it running now
and it seems to be stuck:
1 Expiration Processed
Ich bin bis 08/26/2013 abwesend.
Vielen Dank für Ihre Nachricht.
Ankommende E-Mails werden während meiner Abwesenheit nicht weitergeleitet,
ich versuche Sie jedoch möglichst rasch nach meiner Rückkehr zu
beantworten.
In dringenden Fällen wenden Sie sich bitte an Ihren zuständigen
Vertriebsbeauftra
Hi Harold,
you can have a look here:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli+Storage+Manager/page/Guidelines+for+node+replication
Harold
On 8/8/2013 23:24, Vandeventer, Harold [BS] wrote:
Any info from the community about the "amount of data to be replicate
