Hi:
As mentioned previously, this is a storage pool volume, not a copypool. Since I've
never seen this previously I was wondering if this was due to the upgrade to 3.7.2 on
the server:
Volume Name: 000387
Storage Pool Name: AIX3590ARCH
Device Class Name: 3494ATAPE
Estimated Capacity (MB): 17,357.4
Pct Util: 0.0
Volume Status: Full
Access: Read/Write
Pct. Reclaimable Space: 100.0
Scratch Volume?: Yes
In Error State?: No
Number of Writable Sides: 1
Number of Times Mounted: 3
Write Pass Number: 1
Approx. Date Last Written: 10/06/00 10:34:13
Approx. Date Last Read: 10/06/00 17:01:32
Date Became Pending:
Number of Write Errors: 0
Number of Read Errors: 0
Volume Location:
Last Update by (administrator):
Last Update Date/Time: 10/05/00 19:28:27
>>> [EMAIL PROTECTED] 10/11/00 09:45AM >>>
If you do a Q VOL <VOLNAME> F=D this should show if the tape is PENDING or
not. I'm a newbie, so please forgive me if this is rudimentary information.
Dennis Berestecki
Fluor Corp., USA
Ruddy STOUDER <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 10/11/2000
08:17:49 AM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: Error deleting trans for 0 bytes
May be this could help you. I found some documentation about REUSEDELAY
parameter :
REUSEDELAY parameter : This parameter specifies the number of days that
must elapse before a volume can be reused or returned to scratch status,
after all files have been expired, deleted, or moved from the volume.
When you delay reuse of such volumes and they no longer contain any
files, they enter the pending state. Volumes remain in the pending state
for as long as specified with the REUSEDELAY parameter for the storage
pool to which the volume belongs.
Delaying reuse of volumes can be helpful under certain conditions for
disaster recovery. When TSM expires, deletes, or moves files from a
volume, the files are not actually erased from the volumes: the database
references to these files are removed. Thus the file data may still
exist on sequential volumes if the volumes are not immediately reused.
Ruddy
-----Original Message-----
From: Lawrence Clark [mailto:[EMAIL PROTECTED]]
Sent: mercredi 11 octobre 2000 14:56
To: [EMAIL PROTECTED]
Subject: Error deleting trans for 0 bytes
Yet another new error related to an empty volume that did not return to
the scratch pool. This time after reclamation on the volume:
Anyone seen this:
10/11/00 08:00:44 ANR1041I Space reclamation ended for volume 000387.
10/11/00 08:00:44 ANR9999D afmigr.c(2882): Error deleting transaction
for 0 bytes moved reclamation - volume 000387.
tsm: BACKUP>move data 000387
ANR2232W This command will move all of the data stored on volume 000387
to
other volumes within the same storage pool; the data will be
inaccessible to
users until the operation completes.
Do you wish to proceed? (Yes/No) yes
ANR2209W Volume 000387 contains no data.
ANS8001I Return code 11.
Larry Clark
NYS Thruway Authority
-------------------------------------------------------------------------------------------------
The information transmitted is intended only for the person
or entity to which it is addressed and may contain confidential
and/or privileged material. If you are not the intended
recipient of this message you are hereby notified that any use,
review, retransmission, dissemination, distribution, reproduction
or any action taken in reliance upon this message is prohibited.
If you received this in error, please contact the sender and
delete the material from any computer. Any views expressed
in this message are those of the individual sender and may
not necessarily reflect the views of the company.
---------------------------------------------------------------------------------------------------
