When a tape is in the DR pool, the assumption is that the tape is off site, and
therefore not available to be reclaimed. Thus when a DR pool tape becomes a
candidate to be reclaimed, the data that is to be copied is obtained from the
original copies of the data in the "regular" storage pools. When the reclaim is
complete, then the DR tape is marked as "empty", and can be brought back onsite
and scratched.
Jerry Lawson
jlawson AT thehartford DOT com
______________________________ Forward Header __________________________________
Subject: Is there space reclamation between stgpools?
Author: INTERNET.OWNERAD at SNADGATE
Date: 4/1/97 6:56 PM
I thought space reclamation was only used to move data from a
partially empty volume in a storage pool to an empty or filling
volume in the same storage pool. Today, I found the following
process running:
Process Process Description Status
Number
-------- --------------------
-------------------------------------------------
-------------------------------------------------
188 Space Reclamation Offsite Volume(s) (storage pool DR), Moved
188 Space Reclamation Offsite Volume(s) (storage pool DR), Moved
Files:
11941, Moved Bytes: 26,960,435,221,
Unreadable
Files: 0, Unreadable Bytes: 0. Current File
(bytes): 584,636,262
Current input volume: H00022.
Current output volume: H00062.
And here are the two volumes in question:
Volume Name Storage Device Estimated %Util Volume
Pool Name Class Name Capacity Status
(MB)
------------------------ ----------- ---------- --------- ----- --------
H00022 3590BACK TAPE3590 50,855.1 54.6 Full
H00022 3590BACK TAPE3590 50,855.1 54.6 Full
H00062 DR TAPE3590 26,790.5 100.0 Filling
I guess I'm just clueless about what's going on here. Why would a
space reclamation take place between storage pools?
Thanks,
Owen Crow
UNIX System Administrator
|