Yes, I just configured the DBbackup expire date(DRMDBBACKUPEXPIREDAYS) and yes,
I have lots to read :)
Thanks
>>>
From: Richard Sims
To:
Date: 1/9/2009 2:05 PM
Subject: Re: [ADSM-L] Scratch volumes - TAPE - DB
Before you do anything, review how you set up your DB backups. If
they were throu
Thank you. It worked perfectly! :)
>>>
From: "Gee, Norman"
To:
Date: 1/9/2009 1:19 PM
Subject: Re: [ADSM-L] Scratch volumes - TAPE - DB
Delete Volhistory Todate=Today-n Type=DBBackup
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Ramiro Ruiz
Before you do anything, review how you set up your DB backups. If
they were through DRM, you should be employing DRM regimens to expire
them, rather than interfere with Delete Volhistory. And your DB
backup retention needs to mesh with all server recovery elements,
particularly Reusedelay. Keep
Delete Volhistory Todate=Today-n Type=DBBackup
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Ramiro Ruiz
Sent: Friday, January 09, 2009 10:15 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Scratch volumes - TAPE - DB
Hello,
We setup TSM 5.5.1 a few m
On Jan 24, 2007, at 5:42 PM, Avy Wong wrote:
I am constantly running out of scratch volumes. Everyday many
times I
have to reclaim space back manually by looking through what is less
than
20%
using this ...QUERY VOLUME stg=3584tapepool status=filling
then I do a move data on those volumes.
Avy,
Your collocation is set to node for the stg pool 3584tapepool. This will
increase the tape usage of course.
If it is not required (backup of different nodes can be on the same
tape), set it to none.
Best regards,
Kurt
> -Oorspronkelijk bericht-
> Van: ADSM: Dist Stor Manager [mailt
On 12 Dec 2003, at 19:32, rh wrote:
Sorry, forgot to mention the volumes are on site and
physicall exist in the 3494 with scratch category.
'upd vol acc=readw' or something with 'move drmedia' if you are
using drm...
RH
--- James Choate <[EMAIL PROTECTED]> wrote:
bring the volume back onsite.
up
Sorry, forgot to mention the volumes are on site and
physicall exist in the 3494 with scratch category.
RH
--- James Choate <[EMAIL PROTECTED]> wrote:
> bring the volume back onsite.
> update the access mode to readw.
>
>
> -Original Message-
> From: rh [mailto:[EMAIL PROTECTED]
> Sent: Fr
bring the volume back onsite.
update the access mode to readw.
-Original Message-
From: rh [mailto:[EMAIL PROTECTED]
Sent: Friday, December 12, 2003 10:49 AM
To: [EMAIL PROTECTED]
Subject: Scratch volumes not used
Hi ITSM'ers
I'm running TSM 4.2 with a 3494 library. During TSM
start up
See below for my replies...
>In your experience is restore actually faster with collocation?
That depends (I hate saying that!) The data will not be transferred
faster, if that's what you mean. If you're comparing a restore from a
non-collocated storage pool that contains 50 nodes, vs. a res
On Thu, 26 Jul 2001, Robin Sharpe wrote:
> So collocation, in general will use more scratch tapes, and will have more
> tapes FILLING, than the same nodes in a non-collocated pool. The payback
> of collocation is supposed to be faster restores due to not having to wade
> through other nodes' dat
>>I understand this - it's the effect of collocation.
>I am not sure this statement is correct.
>Collocation attempts to keep data for a particular node either all in one
>tape or all data for one file space in one tape. This is not directly
>related to how many scratch tapes are used.
Sure it i
> TSM grabs the scratch tapes for the tape pools even though there are
> lots of tapes only partially full.
Watch out for Filling tapes frozen in that state by virtue of their
Access mode being other than Readwrite (because of tape I/O errors
or other causes).
On Wed, 25 Jul 2001, Richard L. Rhodes wrote:
> We have TSM setup with several tape pools in our 3494. The tape
> pools are collocated. When we add scratch volumes to the library,
> TSM grabs the scratch tapes for the tape pools even though there are
> lots of tapes only partially full.
Look a
Hi,
i am using STORAGE TEK 9710 , which contains 500DLT's
i am issuing the command corectlly.
checkin libvol stk9710 status=scratch seracch=yes .
does TSM takes scratch volumes automatically in copypool or tapepool or do we
need to define them
manully .?
i am worrying , abot even if they are use
What kind of tape library are you using? I check things in using
checkin libv tapelib 123456 status=scr
which checks them in as scratch and then each of my storage pools I have set
the number of max scratch to something like 99 or 9,999 that way whenever it
needs a scratch tape it pulls it in.
-
16 matches
Mail list logo
