I am using next scripts for TDP for databases:
delete script B1_Oracle_Backups
define script B1_Oracle_Backups description="<Oracle Node> <SID> List of Oracle
database backups"
update script B1_Oracle_Backups \
"Select A.node_name, A.filespace_name, A.ll_name as File_Name, A.backup_date,
A.state, A.class_name, A.object_id \
from backups A, nodes B \
where A.node_name = upper('\$1') and A.filespace_name like '%\$2%' and
A.node_name = B.node_name and B.platform_name like 'TDP Oracle%' \
order by A.backup_date"
delete script B2_MSSQL_Backups
define script B2_MSSQL_Backups description="<MSSQL Node> List of MSSQL database
backups"
update script B2_MSSQL_Backups \
"Select A.node_name, A.filespace_name, A.hl_name as Directory_Name, A.ll_name
as Backup_Type, A.backup_date, \
A.State, A.class_name, A.object_id \
from backups A, nodes B \
where A.node_name = upper('\$1') and A.node_name = B.node_name \
order by A.filespace_name, A.backup_date"
delete script B3_Exchange_Backups
define script B3_Exchange_Backups description="<Exchange Node> List of Exchange
database backups"
update script B3_Exchange_Backups \
"Select node_name, filespace_name, hl_name as Directory_Name, ll_name as
Backup_Type, backup_date, \
State, class_name, object_id \
from backups \
where node_name = upper('\$1') \
order by filespace_name, backup_date"
If run these scripts in Table mode of TSMExplorer Console
(free download from www.s-iberia.com/download.html)
response is shown to very useful format.
Grigori G. Solonovitch
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Dwight Cook
Sent: Wednesday, April 06, 2011 6:56 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TDp and retention settings question
>From the tsm server use
Q file <tdp_node_name>
Then
Show version <tdp_node_name> <fsid> nametype=fsid
To see the actual file names that TSM is saving your tdp data under...
If varies across tdp products but typically the name used in tsm in a unique
name each backup.
Dwight
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
js1000
Sent: Wednesday, April 06, 2011 9:26 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TDp and retention settings question
I'm trying to find the missing link in what i see setup versus what i can
see out of the tdp gui in terms of inactive/active versions listed.
the copygroup policy settings for this tdp node as a such:
Versions Data Exists: No Limit
Versions Data Deleted: No Limit
Retain Extra Versions: 14
Retain Only Version: 30
tdp is set to backup full daily.
When firing up the tdp gui on the node, i see 26 inactive and 1 active full
backups ready for restore.
my question is the relationship between the settings and the number of
backups i see. in my thinking, i'm considering the daily fulls as the same
object or file to tsm. in this case, we would be grabbing different versions
of the same file, wouldnt the 14 day version setting kick in and i should
only see 14 inactives and 1 active full?
but i see nearly 30 inactives with different object ids. so is the process
that tsm considers each full backup a different object/file? Seems to be
true given the differing object ids. if that is the case, is the link i'm
missing is that TDP in the process of backing up the nightly full, deletes
the prior day's full. This sends the file to inactive state in tsm and then
subject to the retain only version setting?
other posts have suggested matching the extra versions and only versions
settings. what's the implication in doing so?
Thanks!
+----------------------------------------------------------------------
|This was sent by jonathan.shen AT osumc DOT edu via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
Please consider the environment before printing this Email.
CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail
message and any attachments hereto may be legally privileged and confidential.
The information is intended only for the recipient(s) named in this message. If
you are not the intended recipient you are notified that any use, disclosure,
copying or distribution is prohibited. If you have received this in error
please contact the sender and delete this message and any attachments from your
computer system. We do not guarantee that this message or any attachment to it
is secure or free from errors, computer viruses or other conditions that may
damage or interfere with data, hardware or software.
|
