You state Data Protection for SQL is the "tdp" you are referring to.
Data Protection for SQL backups are automatically managed.
You do not need to manually manage them.
If you run a full backup, it will expire all previous full, log,
and differential backups. At that point, according to your
settin
Anyone out there solved how to install the lin_tape padckage on redhat
enterprise linux 6?
Apparently, "rebuild" is not supported in their implementation of rpm.
I've been looking at the rpm man page, but the light hasn't come on yet.
Any pointers at this time would be helpful.
Gary Lee
Senior
We have three storage pools, the primary pool is a devtype FILE
and the two copy pools are devtype LTO3. The offsite copy pools gets
transferred offsite via DRM.
Whenever I run a reclamation on the offsite copy pool the
system grabs a scratch tape and then copies
About the only way I can think of to do this is to mark the onsite copy pool
volumes as unavailable. This would force data to be pulled from the primary
file pool.
The reason it does this for the offsite pool, is that offsite volumes are
presumed to be unavailable, thus data must be pulled fro
Or just mark them offsite, even though they are still in the library.
You could create a script that does "update vol * wherestgpool=onsitecopy
access=offsite" before you start reclamation, then reverse it when reclamation
finishes.
W
-Original Message-
From: ADSM: Dist Stor Manager [ma
As the previous 2 mentioned, if the tape is available, TSM will use it. If it's
offsite, TSM will try to collect the data from primary volumes. So your issue
is that the copypool tapes are actually available. It's kinda weird you get
them reclaimed though, they should have been moved offsite lon
Which version are you running? You should have full support from 1.49.
-"ADSM: Dist Stor Manager" skrev: -
Till: ADSM-L@VM.MARIST.EDU
Från: "Lee, Gary D."
Sänt av: "ADSM: Dist Stor Manager"
Datum: 04/11/2011 18:58
Ärende: Trying to install lin_tape
Anyone out there solved how to ins
A more draconian method (not recommended) is to perform a Delete Volume for the
copy storage pool volumes you would reclaim, where their former content would
be freshly written to tape in the next Backup Stgpool. That leaves you with
one less copy of the data, of course, so not the best approac
This is close to what we do, but we add "stat=full" to narrow it down better.
At 01:38 PM 4/11/2011, Prather, Wanda wrote:
>Or just mark them offsite, even though they are still in the library.
>You could create a script that does "update vol * wherestgpool=onsitecopy
>access=offsite" before you
I ran into an odd issue, and it took me a while to figure out the
cause. I'm posting this because I found very few hits about
lvmread.c, and none matched. Most gave info about memory consumption,
which is no factor here.
If you have to replace the OS on your TSM server, and you're not using
AD,
10 matches
Mail list logo
