DongDong,
I see two possible reasons:
1. Your retention policy expires the version before the maximum count
versions data exists is reached. If the retain-extra value is set to
a low number (like 4 days) and you change the file every 3 days, this
behaviour would be as expected.
2. You forgot to
Hot Diggety! Dan Foster was rumored to have written:
My DBAs and I are completely baffled. How do I get TDPO to send
controlfiles to SBT_TAPE instead of DISK?
Eventually resolved: needed to get *every* single config file on BOTH
hosts to match for a restore to the DR host, AND to disable
Dear Michael:
Thank you for your help~! I forget to activate the policy set ~! Thank
you very much .
DongDong YU
DongDong,
I see two possible reasons:
1. Your retention policy expires the version before the maximum count
versions data exists is reached. If the retain-extra
oh yeah, this happened to my instructor on Tivoli Storage Manager
Foundation College in Bruxelles :-)
i had to remind him :-)
2008/4/23 Yu Dong Dong (ITD) [EMAIL PROTECTED]:
Dear Michael:
Thank you for your help~! I forget to activate the policy set ~!
Thank you very much .
Hello,
What is the normal time for keeping volhist? Not indefinitely ?
Thanks,
Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860)862-8164
(cell) (860)961-6976
Avy Wong wrote:
Hello,
What is the normal time for keeping volhist? Not indefinitely ?
I usually keep db backup volumes about 5 days, for other volhist entries
I'd say that 30-60 days is about the maximum usefull time.
Thanks,
Avy Wong
Business Continuity Administrator
Mohegan Sun
1
Thanks Remco, it gives me some idea.
Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860)862-8164
(cell) (860)961-6976
Remco Post
[EMAIL PROTECTED]
Sent by: ADSM:
On Thu, Apr 10, 2008 at 3:26 PM, Dan Foster [EMAIL PROTECTED] wrote:
My setup:
TSM server (Enterprise) 5.5 on AIX 5.2.
TDPO 5.4.1 on Solaris 10/SPARC and Oracle 10gR2.
Do you really have TSM 5.5 running on AIX 5.2? I wondered if that
would work, and kind of thought it would, but Tivoli
Hot Diggety! Steve Stackwick was rumored to have written:
On Thu, Apr 10, 2008 at 3:26 PM, Dan Foster [EMAIL PROTECTED] wrote:
My setup:
TSM server (Enterprise) 5.5 on AIX 5.2.
TDPO 5.4.1 on Solaris 10/SPARC and Oracle 10gR2.
Do you really have TSM 5.5 running on AIX 5.2? I
If you are talking about the actual volhist.out backup file, I'd keep
one for every dbbackup.
If you are talking about volume entries in the volhist, I'd go with
Remco's post.
Not that DBBackups are expired by setting the proper options under DRM
so you don't have to run a del volhist type=dbb or
We may be going to LTO 3 or 4 in the near future.
How long does it take to reclaim a LTO3 tape at 50% full,
and how long for a LTO4?
Doug Thorneycroft
Senior Systems Analyst
Computer Technology Section
County Sanitation Districts of Los Angeles County
1955 Workman Mill Road
Whittier, CA 90601
For STGNEW, STGDELETE, STGREUSE entries, there is no use for them once your
oldest DB backup has expired, but it's OK to keep them around longer.
Be careful though, clearing out the VOLHIST, if you occasionally create
BACKUPSET or EXPORT tapes - if you delete those VOLHIST entries, the volumes
We have reclamation set up to 70 using our LTO3 drives which only hold
Oracle data and usually consists of largeish files. They usually reclaim
faster due to higher transfer rates etc then LTO2 and LTO. It is one of
those how long is a piece of string questions depends on the variables
including
I have a customer planning a DR test.
They run TSM 5.5 server on AIX 5.3.
They will be taking a mksysb tape to the DR site to reload AIX.
So the TSM code will be reloaded with the mksysb, but the TSM DB log are
not in the root volume group.
Thus we will need to initialize an empty DB Log to
14 matches
Mail list logo
