DR media not transitioning to vault retrieve

[Elomis]

Hey guys,

I have stuffed up somewhere and my q drmedia looks like the following;

tsm: FP-SYD-02_SERVER1>q drmedia

Volume Name State Last Update Date/Time
---------------- ----------------- -------------------
VGF342L2 Mountable 12/01/2007 02:13:00
VGF345L2 Vault 10/31/2007 15:29:26
VGF364L2 Vault 10/31/2007 15:30:38
VGF365L2 Vault 10/31/2007 15:31:58
VGF363L2 Vault 10/31/2007 15:33:15
VGF362L2 Vault 10/31/2007 15:34:31
VGF361L2 Vault 10/31/2007 15:35:50
VGF349L2 Vault 10/31/2007 15:37:03
VGF343L2 Mountable 10/18/2007 09:26:16
VGF355L2 Mountable 10/17/2007 11:29:06
VGF352L2 Vault 10/31/2007 15:38:19

This is the way it's looked for a while, problem is, my tapes aren't transitioning to "vault retrieve", I have tapes offsite, and there they sit and nothing seem to change. They've been offsite now for nearly two months. Surely they need to come back? What settings should I check?

 

[BBB]

Make sure you are reclaiming the tapes using reclamation.
Are the tapes stgpool tapes or db backup tapes?

 

[tsmpro]

1. Make sure reclamation is running for copy storage pools . If reclamation is not running , then data is not going to expire and tapes won't come to VR state.
2. Also check for reuse delay parameter for copy storage pool.

 

[sgabriel62]

If you have any automated scripts that are in place that manage your DR media rotation process, by cron or AT for that matter - perhaps check to see if there processes have been inadvertently killed or removed from execution.
Take a good look at your TSM DB tape rotation as well within your DRM module.
Sounds to me like something was disabled over time.
Good luck

 

[baloo1]

I have same problem

Database backup tapes are returning to VR state. But DRM with data not. In daily schedule i have rows for reclaim tapes, but not disaster stgpool. My attempt to reclaim DR stgpool not was success, tsm says some as "reclaim for this stgpool is not allowed". I can post exact message. Reuse delay on DR stgpool=0 and tapes still remains in Vault state. What i made wrong ? thanks for any idea

 

[BBB]

If you tried google or ran "help ANR4973I" you would see that you need to specify a reclamation threshold. Try it again with a threshold.

 

[gar]

Hello, I have the same problem with TSM EE 6.2.2.2 server. DRM tapes not going to vaultretrieve state, even after command:
tsm: POBTSM>reclaim stg DRM_LTO th=50
ANR2111W RECLAIM STGPOOL: There is no data to process for DRM_LTO.

I chcecked volume content:
tsm: POBTSM>q cont 000021L4
ANR2034E QUERY CONTENT: No match found using this criteria.

My DRM setting is:
Recovery Plan Prefix: /backup/DRM/plans/
Plan Instructions Prefix: /backup/DRM/instructions/
Replacement Volume Postfix: @
Primary Storage Pools: SERVERS_LTO DB2_LTO
Copy Storage Pools: DRM_LTO
Active-Data Storage Pools:
Not Mountable Location Name: TS3200
Courier Name: COURIER
Vault Site Name: VAULT
DB Backup Series Expiration Days: 0 Day(s)
Recovery Plan File Expiration Days: 6 Day(s)
Check Label?: Yes
Process FILE Device Type?: No
Command File Name:

My DRM status:
tsm: POBTSM>q drm
000021L4 Vault 03/20/11 14:28:47
000022L4 Vault 03/28/11 17:36:53
000023L4 Vault 04/27/11 13:10:55
000024L4 Vault 04/27/11 13:12:12
000025L4 Vault 05/02/11 09:21:47
000026L4 Vault 05/16/11 08:32:45
000027L4 Vault 05/21/11 09:16:09
000028L4 Vault 05/21/11 11:40:37
000041L4 Vault 05/21/11 09:23:59
000040L4 Vault 05/21/11 09:17:28

Any idea?

 

[BBB]

There may still be a bit of data on the tape even though q cont says its empty. What does "q vol xxxx" say?

Try a "move data xxxxx" and/or "audit vol xxxxx"

 

[gar]

Thanks for your reply. I've been checked:
POBTSM>q vol
000021L4 DRM_LTO LIB_LTO4 0.0 M 0.0 Pending
000022L4 DRM_LTO LIB_LTO4 0.0 M 0.0 Pending
000023L4 DRM_LTO LIB_LTO4 0.0 M 0.0 Pending
000024L4 DRM_LTO LIB_LTO4 0.0 M 0.0 Pending
000025L4 DRM_LTO LIB_LTO4 0.0 M 0.0 Pending
000026L4 DRM_LTO LIB_LTO4 0.0 M 0.0 Pending
000027L4 DRM_LTO LIB_LTO4 0.0 M 0.0 Pending
000028L4 DRM_LTO LIB_LTO4 1.6 T 34.6 Filling

Volume Name: 000021L4
Storage Pool Name: DRM_LTO
Device Class Name: LIB_LTO4
Estimated Capacity: 0.0 M
Scaled Capacity Applied:
Pct Util: 0.0
Volume Status: Pending
Access: Offsite
Pct. Reclaimable Space: 0.0
Scratch Volume?: No
In Error State?: No
Number of Writable Sides: 1
Number of Times Mounted: 1
Write Pass Number: 1
Approx. Date Last Written: 03/20/11 14:20:15
Approx. Date Last Read: 03/20/11 14:12:33
Date Became Pending: 05/18/11 13:00:48
Number of Write Errors: 0
Number of Read Errors: 0
Volume Location: Vault
Volume is MVS Lanfree Capable : No
Last Update by (administrator): TSMADMIN
Last Update Date/Time: 03/20/11 14:28:47
Begin Reclaim Period:
End Reclaim Period:
Drive Encryption Key Manager: None


tsm: POBTSM>audit vol 000021L4
ANR2310W This command will compare all inventory references to volume 000021L4 with the actual data stored on the volume and will report any discrepancies; the data will be inaccessible to users until the operation completes.

Do you wish to proceed? (Yes (Y)/No (N)) y
ANR2425E AUDIT VOLUME: Unable to access volume 000021L4 - access mode is set to "offsite".

 

[BBB]

Ok I misunderstood your post but now we now what is happening.

Your tapes are empty.
But they are in pending state.

They will remain in this state until the reuse delay set on their storagepools is over. (See "q stg xxxx f=d" to check the reuse delay. One the reuse delay is over, your tapes will revert to vaultretrieve.

If you really want the tapes back early, you can "del vol xxxx" them, but this isn't best practice in the sense that the reuse delay has been set for a reason.

 

[gar]

Now is OK, but should I do reclamation copy pool weekly? Reclamation copy pool is necessary to proper working of DRM system?

 

[BBB]

Yes of course you need to reclaim your copy pool. If you don't you'll rarely free up offsite tapes to come back.