If your files are with unique names VERE=1 is equivalent to VERE="no
limit" from policy point of view.
But then all those unique names will be always ACTIVE in TSM unless you
delete them from the filesystem. Only after you delete them, the VERD and
RETO settings apply. RETE/VERE are used only when you have many versions
of same file name.
If your DB2 DBA is keeping the backups to files, say 31 days, and only
then deletes them - 31 days (while the file is "active") + 31 days (retain
only version) = 62 days!
Maybe it would be better to convince the DBA to use "backup to tsm"
command in DB2 instead of dumping to file - DB2 is having built-in agent
for TSM.
Zlatko Krastev
IT Consultant
NSavva AT laiki DOT com
16.10.2003 12:10
To: "Zlatko Krastev" <acit AT attglobal DOT net>
cc:
Subject: Re: Backup copy group definition
Hi,
My Environment is based on a Win2k TSM Server, with AIX Clients and a NAS
Client. NAS server is mainly used for storage from other Windows Servers
using a maped drive scheme.
One of the Windows Server is running SQL (DB2) and when an administrator
is
performing a backup, the backup image is dumped on a mapped drive that
resides on NAS. The filename of the DB2 SQL backup is created based on the
date and time. for example :-
/NODE0000/DB_INCR_BACKUP.20030918202006.1.
The next day i am going to make a backup, another filename will be created
based on date and time. example :-
/NODE0000/DB_INCR_BACKUP.20030919212149.1
So now as an example we have two files with different filename.
My question is :-
"how can i maintain my backups ( incremental for 7 days and selective for
31 days) using backup copy group policies, since TSM policies are always
based on File VERSION?"
Hope I was informative enough.....
Best regards
"Zlatko Krastev"
<acit AT attglobal DOT net> To: "ADSM: Dist
Stor
Manager" <ADSM-L AT VM.MARIST DOT EDU>
16/10/2003 11:57 πμ cc: Nicolas Savva
<NSavva AT LAIKI DOT COM>
bcc:
Subject: Re: Backup
copy group definition
On Day 2 you previous copy will be expired due to "Versions Data Exists"
limited to 1. If you need to keep for N days, you should set VERE="no
limit" VERD="no limit".
Zlatko Krastev
IT Consultant
Nicolas Savva <NSavva AT LAIKI DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
13.10.2003 17:30
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Backup copy group definition
Hi to all
I have a question regarding a backup copy group definition.
Let say that i want my incremental backup to be stored for 7 days and my
selective backup for 31 days
I have the following settings in my TSM for a backup copy group:
1. For incremental backup:
Copy Group Name STANDARD
Versions Data 1
Exists
Versions Data 1
Deleted
Retain Extra 7
Versions
Retain Only Version 7
2. Selective backup
Copy Group Name STANDARD
Versions Data 1
Exists
Versions Data 1
Deleted
Retain Extra 31
Versions
Retain Only Version 31
Do You think the above definitions are correct?
Thanx
************************************************************************************
Privileged/Confidential information may be contained in this message and
may be subject to legal privilege. Access to this e-mail by anyone other
than the intended recipient is unauthorised. If you are not the intended
recipient (or responsible for delivery of the message to such person), you
may not use, copy, distribute or deliver to anyone this message (or any
part of its contents) or take any action in reliance on it. In such case,
you should destroy this message, and notify us immediately.
If you have received this email in error, please notify us immediately by
e-mail or telephone and delete the e-mail from any computer. If you or
your
employer does not consent to internet e-mail messages of this kind, please
notify us immediately.
All reasonable precautions have been taken to ensure no viruses are
present
in this e-mail. As we cannot accept responsibility for any loss or damage
arising from the use of this e-mail or attachments we recommend that you
subject these to your virus checking procedures prior to use.
The views, opinions, conclusions and other information expressed in this
electronic mail are not given or endorsed by Laiki Group unless otherwise
indicated by an authorised representative independent of this message.
************************************************************************************
********************************************************************************************
Privileged/Confidential information may be contained in this message and
may be subject to legal privilege. Access to this e-mail by anyone other
than the intended recipient is unauthorised. If you are not the intended
recipient (or responsible for delivery of the message to such person), you
may not use, copy, distribute or deliver to anyone this message (or any
part of its contents) or take any action in reliance on it. In such case,
you should destroy this message, and notify us immediately.
If you have received this email in error, please notify us immediately by
e-mail or telephone and delete the e-mail from any computer. If you or
your
employer does not consent to internet e-mail messages of this kind, please
notify us immediately.
All reasonable precautions have been taken to ensure no viruses are
present
in this e-mail. As we cannot accept responsibility for any loss or damage
arising from the use of this e-mail or attachments we recommend that you
subject these to your virus checking procedures prior to use.
The views, opinions, conclusions and other information expressed in this
electronic mail are not given or endorsed by Laiki Group unless otherwise
indicated by an authorised representative independent of this message.
********************************************************************************************
|
