Frank,
I'm not really sure I understand your problem : why would you remove
those volumes from DRM ? What do you mean by "virtual" volumes in the
3583 library. Could you give us an extract of what "q drm" shows, and
for some volumes appearing in this list, do a "q vol xxxxxxx f=d" and
show us the output.
I have the feeling that DRM was configured properly 2 years ago (with
primary and copy pools associated with DRM), until someone broke those
associations, and now DRM still shows those old records that never went
updated afterwards.
What is sure is that DRM can't work properly without knowing which
storage pool to handle ...
Give us some clarifications please ...
Arnaud
************************************************************************
******
Panalpina Management Ltd., Basle, Switzerland, CIT Department
Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: arnaud.brion AT panalpina DOT com
************************************************************************
******
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Frank Mueller
Sent: Wednesday, 08 September, 2004 16:42
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Antwort: Re: q drmedia question [Virus checked]
Hi,
I don't understand this. Isn't it possible to remove this volumes? I see
that we have virtuell volumes in the second library with a timestamp
from
2002 and they allocate space.....
Best regards,
Frank
PAC Brion Arnaud
<Arnaud.Brion@PAN An:
ADSM-L AT VM.MARIST DOT EDU
ALPINA.COM> Kopie:
Gesendet von: Thema: Re: q drmedia
question [Virus checked]
"ADSM: Dist Stor
Manager"
<[email protected]
.EDU>
08.09.2004 16:03
Bitte antworten
an "ADSM: Dist
Stor Manager"
Hi Frank,
>But when I show the options, it shows o.k.
Surely not ! If you want the DRM to handle your volumes properly, you
should associate all your primary pools with "Primary Storage Pools:"
entry, and the same for copy pools !
That time being, your recovery plan will be of no help for rebuilding
storage pools in case of a disaster, simply why it does not know them !
Furthermore, "DB Backup series expiration days" value should be the same
as "Recovery Plan File Expiration Days", because you'll need the DB
backup volume to use the recovery plan.
Cheers.
Arnaud
************************************************************************
******
Panalpina Management Ltd., Basle, Switzerland, CIT Department
Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: arnaud.brion AT panalpina DOT com
************************************************************************
******
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Frank Mueller
Sent: Wednesday, 08 September, 2004 14:58
To: ADSM-L AT VM.MARIST DOT EDU
Subject: q drmedia question [Virus checked]
Hi,
we have 2 x TSM-Server with TSM Version 5.1.8.0 on AIX 5.2_ML02. The
first server has a 3494 library and the second server a 3583 library.
When I start the command
q drmedia
I get a lot of volumes with a very old timestamp (older than 2 years).
But when I show the options, it shows o.k.:
tsm: ADSM_OERAG01>q drmstatus
Recovery Plan Prefix: /mgnt/save_data/adsm_db/config/
Plan Instructions Prefix: /mgnt/save_data/adsm_db/config/
Replacement Volume Postfix: @
Primary Storage Pools:
Copy Storage Pools:
Not Mountable Location Name: NOTMOUNTABLE
Courier Name: COURIER
Vault Site Name: VAULT
DB Backup Series Expiration Days: 3 Day(s) Recovery Plan File
Expiration Days: 5 Day(s)
Check Label?: Yes
Process FILE Device Type?: No
Command File Name:
/mgnt/save_data/adsm_db/config/recfileplan-
cmd
What is the reason, that I get a lot of volumes by q drmedia?
Best regards,
Frank Mueller
|
