Hi Andy and others!
Thank you all for your help!
This would be the easiest way then:
SELECT volume_name FROM libvolumes WHERE status='Private' AND volume_name NOT
IN (SELECT volume_name FROM volumes) and volume_name not in (select volume_name
from volhistory where type like 'BACKUP%')
You
The issue was that I needed a way to recreate the actual files in the dbdirs.
It is fixed now.
Original Message
From: Erwann Simon
Sent: Mon, Nov 24, 2014 12:42 AM
To: ADSM: Dist Stor Manager ; Dury, John C.
CC:
Subject: Re: [ADSM-L] recovering a DB from full backup when one of
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
We had the same problem on TSM 6.3.4 on Windows, never found out why.
Stopped using archive overflow because of it.
Once the DB backup is done, just delete the extra files.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Roger
Deschner
Sent:
