the dsmc command used above (with the "backup" option) does not incrementally scan a folder to report "missing" files to the ISP server. Check use of "dsmc incr" instead.
So unless there are no there incremental runs on that directory or filespace, old backups will never transition to inactive and will stay forever, unless you issue manual "dsmc delete backup" commands with the BACKDEL option of the accessing node set to YES.
Regards
Ilja
Original Message:
Sent: Thu August 28, 2025 01:56 PM
From: Uwe Schreiber
Subject: Will the Oracle dump file backup be kept in IBM TSM forever?
Hello Wei,
if a file is getting backuped it will be stored as an Active version within the ISP server.
If a new version of a file is getting backuped, the formerly active version will become inactive (and the retention will be handled by the parameters VEREXIST and RETEXTRA) and the new backup will become the new active version.
If the file, which is the active version is getting deleted on the local drive, the ISP B/A client will recognize this deletion and the formerly active version will become inactive.
The retention of inactive versions is handles by the parameters VERDEL and RETONLY.
So if you dump-file is unique by a timestamp within the filename this file will be handled by VERDEL and RETONLY as soon it will be deleted on the local drive.
------------------------------
Uwe Schreiber
System Engineer / Solution Architect
SVA System Vertrieb Alexander
Wiesbaden
Original Message:
Sent: Thu August 28, 2025 11:11 AM
From: Wei Huang
Subject: Will the Oracle dump file backup be kept in IBM TSM forever?
I has a IBM TSM client on an AIX host with Oracle database installed as while.
A script executed by a cron job backs up a Oracle dump file, which runs once a day. part of the zsh script is:
DTTMSTAMP=`date +'%Y%b%d_%k%M'`
export ORA_BACKUP=/drexp
export DIRECTORY=${ORACLE_SID}_dir
DMP_FILE=expdp_${ORACLE_SID}_${DTTMSTAMP}.dmp
# Remove the old export
rm -f /drexp/myora/*.dmp
rm -f /drexp/myora/*.log
$ORACLE_HOME/bin/expdp $USERID full=y exclude=statistics content=all directory=pump_dir dumpfile=$DMP_FILE COMPRESSION=ALL logfile=expdp_${ORACLE_SID}_${DTTMSTAMP}.log
#TSM backup
/usr/bin/dsmc backup -tapep=no "/drexp/myora/*"
the Backup policy in TSM is:
Copy Group
Copy Group Name........: STANDARD
Copy Type..............: Backup
Copy Frequency.........: 0 day(s)
Versions Data Exists...: 30 version(s)
Versions Data Deleted..: 2 version(s)
Retain Extra Versions..: 30 day(s)
Retain Only Version....: 60 day(s)
Copy Serialization.....: Dynamic
Copy Mode..............: Modified
Copy Destination.......: DDVTLPOOL
Lan Free Destination...: NO
Deduplicate Data.......: NO
If the dump files name keeps the same, I know the second day it will be set inactive and will be delete after 30 days(last version will be kept 60 days);
but the dump files name changed with timestamp, does that mean: even they are backed up, each days backup will keep active and will be retained forever? I am confused here.
------------------------------
Wei Huang
------------------------------