Tape from Courier to Scratch... How?

Snakes

Active Newcomer
Joined
Jan 28, 2014
Messages
23
Reaction score
0
Points
0
PREDATAR Control23

Hello guys, I have a tape that went to Courier state. I need that tape to go back to scratch. How can I acomplish that?

I tried to checkin the libvol, but I can only do it in status=private. Any clues on how the process goes on?

Thanks to all!
 
PREDATAR Control23

You need to do a move drm volume_name wherest=courier to=onsiter

OnsiteRetrieve state essentially ends the tracking of the volume in the DRM lifecycle.
 
PREDATAR Control23

Hello guys, I have a tape that went to Courier state. I need that tape to go back to scratch. How can I acomplish that?

I tried to checkin the libvol, but I can only do it in status=private. Any clues on how the process goes on?

Thanks to all!

If the tape is in courier status, this normally means that it is destined for offsite storage. The tape is a DR or copy tape.

If a tape is destined to be loaded back as scratch, the state should normally be courierretrieve.

In your case, I would doubt if you can assign it a scratch status IF the DRM cycle has not yet been completed.
 
PREDATAR Control23

Thank you guys, I'll try that and see if it works. I'll keep you posted.
 
PREDATAR Control23

Also, how can I disable this? The TSM server had a DRP, but I am now administering and I want to change it to copy the DBBACKUP to a Copy Storage pool defined by me and no longer use tapes for it.

Current config:

TSM>q drm


Volume Name State Last Update Automated
Date/Time LibName
---------------- ----------------- ------------------- ----------------
D00005L4 Mountable 02/27/2014 09:01:10 T3573
D00004L4 Courier 02/26/2014 10:00:01


TSM>q drm f=d


Volume Name: D00005L4
State: Mountable
Last Update Date/Time: 02/27/2014 09:01:10
Location:
Volume Type: DBBackup
Copy Storage Pool Name:
Active Data Storage Pool Name:
Automated LibName: T3573


Volume Name: D00004L4
State: Courier
Last Update Date/Time: 02/26/2014 10:00:01
Location: COURIER
Volume Type: DBBackup
Copy Storage Pool Name:
Active Data Storage Pool Name:
Automated LibName:

TSM>q drmstatus


Recovery Plan Prefix:
Plan Instructions Prefix:
Replacement Volume Postfix: @
Primary Storage Pools:
Copy Storage Pools: DRMPOOL
Active-Data Storage Pools:
Not Mountable Location Name: NOTMOUNTABLE
Courier Name: COURIER
Vault Site Name: VAULT
DB Backup Series Expiration Days: 60 Day(s)
Recovery Plan File Expiration Days: 60 Day(s)
Check Label?: Yes
Process FILE Device Type?: No
Command File Name:



This is the STGPOOL that I created for the DBBACKUP:

TSM>q stgpool drmpool f=d


Storage Pool Name: DRMPOOL
Storage Pool Type: Copy
Device Class Name: DRM
Estimated Capacity: 0.0 M
Space Trigger Util: 0.0
Pct Util: 0.0
Pct Migr:
Pct Logical: 0.0
High Mig Pct:
Low Mig Pct:
Migration Delay:
Migration Continue:
Migration Processes:
Reclamation Processes: 1
Next Storage Pool:
Reclaim Storage Pool:
Maximum Size Threshold:
Access: Read/Write
Description:
Overflow Location:
Cache Migrated Files?:
Collocate?: No
Reclamation Threshold: 100
Offsite Reclamation Limit: No Limit
Maximum Scratch Volumes Allowed: 300
Number of Scratch Volumes Used: 0
Delay Period for Volume Reuse: 0 Day(s)
Migration in Progress?:
Amount Migrated (MB):
Elapsed Migration Time (seconds):
Reclamation in Progress?: No
Last Update by (administrator): ADMIN
Last Update Date/Time: 12/11/2013 09:40:52
Storage Pool Data Format: Native
Copy Storage Pool(s):
Active Data Pool(s):
Continue Copy on Error?:
CRC Data: No
Reclamation Type: Threshold
Overwrite Data when Deleted:
Deduplicate Data?: No
Processes For Identifying Duplicates:
Duplicate Data Not Stored:
Auto-copy Mode:
Contains Data Deduplicated by Client?: No


Thank you guys!
 
PREDATAR Control23

Any help is greatly appreciated! :up:
 
Last edited:
PREDATAR Control23

I don't completely follow what you want to do.

What I gather is that you want to copy the DBBACKUP to to the Copy pool? No can do!

I use devclass=file and replicate it to have a copy.
 
PREDATAR Control23

Got it... So you need a devclass=file to copy the DBBACKUP to a StoragePool?
 
PREDATAR Control23

I have a devclass=file defined and is drmpool is a copy stgpool using that devclass. What kind of stgpool should I use then? A Primary?
 
PREDATAR Control23

Thank you, moon-buddy. Now that I have the TSM configured as follows, how can I prevent the tape going to Vault, every day? I'm tired of cancelling req # every morning...

tsm: TSM>q drm


Volume Name State Last Update Automated
Date/Time LibName
---------------- ----------------- ------------------- ----------------
D00009L4 Mountable 03/27/2014 09:03:38 T3573


tsm: TSM>q drmsta


Recovery Plan Prefix:
Plan Instructions Prefix:
Replacement Volume Postfix: @
Primary Storage Pools: DRMPOOL
Copy Storage Pools:
Active-Data Storage Pools:
Not Mountable Location Name: NOTMOUNTABLE
Courier Name: COURIER
Vault Site Name: VAULT
DB Backup Series Expiration Days: 60 Day(s)
Recovery Plan File Expiration Days: 60 Day(s)
Check Label?: Yes
Process FILE Device Type?: Yes
Command File Name:


tsm: TSM>q drm f=d


Volume Name: D00009L4
State: Mountable
Last Update Date/Time: 03/27/2014 09:03:38
Location:
Volume Type: DBBackup
Copy Storage Pool Name:
Active Data Storage Pool Name:
Automated LibName: T3573



tsm: TSM>Q VOLHIST TYPE=DBB


Date/Time: 03/27/2014 09:03:38
Volume Type: BACKUPFULL
Backup Series: 1,097
Backup Operation: 0
Volume Seq: 10,001
Device Class: LTO01
Volume Name: D00009L4
Volume Location:
Command:
Database Backup ID High: 0
Database Backup ID LOW: 0
Database Backup Home Position: 0
Database Backup HLA:
Database Backup LLA:
Database Backup Total Data Bytes (MB) : 0
Database Backup total Log Bytes (MB) : 0
Database Backup Block Num High: 0
Database Backup Block Num Low: 0
Database Backup Stream Id: 1
Database Backup Volume Sequence for Stream: 10,001


I just want to set the DBB go to the Primary Stgpool, on the FILE devclass...

Thanks,
Snakes.-
 
PREDATAR Control23

Thank you, moon-buddy. Now that I have the TSM configured as follows, how can I prevent the tape going to Vault, every day? I'm tired of cancelling req # every morning...

tsm: TSM>q drm


Volume Name State Last Update Automated
Date/Time LibName
---------------- ----------------- ------------------- ----------------
D00009L4 Mountable 03/27/2014 09:03:38 T3573


tsm: TSM>q drmsta


Recovery Plan Prefix:
Plan Instructions Prefix:
Replacement Volume Postfix: @
Primary Storage Pools: DRMPOOL
Copy Storage Pools:
Active-Data Storage Pools:
Not Mountable Location Name: NOTMOUNTABLE
Courier Name: COURIER
Vault Site Name: VAULT
DB Backup Series Expiration Days: 60 Day(s)
Recovery Plan File Expiration Days: 60 Day(s)
Check Label?: Yes
Process FILE Device Type?: Yes
Command File Name:


tsm: TSM>q drm f=d


Volume Name: D00009L4
State: Mountable
Last Update Date/Time: 03/27/2014 09:03:38
Location:
Volume Type: DBBackup
Copy Storage Pool Name:
Active Data Storage Pool Name:
Automated LibName: T3573



tsm: TSM>Q VOLHIST TYPE=DBB


Date/Time: 03/27/2014 09:03:38
Volume Type: BACKUPFULL
Backup Series: 1,097
Backup Operation: 0
Volume Seq: 10,001
Device Class: LTO01
Volume Name: D00009L4
Volume Location:
Command:
Database Backup ID High: 0
Database Backup ID LOW: 0
Database Backup Home Position: 0
Database Backup HLA:
Database Backup LLA:
Database Backup Total Data Bytes (MB) : 0
Database Backup total Log Bytes (MB) : 0
Database Backup Block Num High: 0
Database Backup Block Num Low: 0
Database Backup Stream Id: 1
Database Backup Volume Sequence for Stream: 10,001


I just want to set the DBB go to the Primary Stgpool, on the FILE devclass...

Thanks,
Snakes.-

You can't prevent TSM from telling you to move the DB Backup on tape to go to the vault. This is a mandatory procedure to safeguard your data.

With DEVCLASS=FILE, I don't get this prompt. I just make sure I have a copy of the DB Backup elsewhere either through replication or snapshots.
 
PREDATAR Control23

You can't prevent TSM from telling you to move the DB Backup on tape to go to the vault. This is a mandatory procedure to safeguard your data.

With DEVCLASS=FILE, I don't get this prompt. I just make sure I have a copy of the DB Backup elsewhere either through replication or snapshots.

Thank you all for all the help. I finally solved the issue. Bassicaly I had a default MAINTENANCE_PLAN that was created some months ago, when I upgraded from 5.5.0.0 to 6.3.4.0. The plan automatically selected the LTO device for DRM operations, so that was the main problem.

Selected a devclass=FILE and now I'm backing up the DB directly to disk, no library involved. Our environment is very small, so using a tape daily for DBB is nonesense.
 
Top