• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Destroyed Secondary Copy

ryanbsc

Active Newcomer
#1
Hi Guys


I need some urgent help if possible.


IN our setup we take daily incremental backups.
Tivoli produces and offsite copy every day and spits out which ever tapes are to go offsite after the backups are completed. And then in the morning produces a list of tapes it would like back, for reclaimation.

Here's the bad news, while taking one of the tapes out the drive, I dropped it, and now its in pieces.


So now I need to know how to make a replacement secondary copy:(., I'm new to tivoli , so could someone talk me through how to do this? Or point me in the direction of how I can quickly learn how to fix this. ?.



Thank you very much
.
 

heada

ADSM.ORG Moderator
#2
del vol {volume} discard=yes

On the next time you perform a "backup stgpool" it will make a new copy.

-Aaron
 

ryanbsc

Active Newcomer
#3
Hi Heada

Thanks for that, is there no way I can re create the secondary copy there and then without having to wait for it to do the backup next time, as that tape may not get read for a few days depending on whatg its backing up.

Thanks
 

ryanbsc

Active Newcomer
#4
Also wont I need a enw tape to be entered into the tape library for ti to be made a replacement of the damaged tape?

As an update I queried the volume / tape I wish to replace

this was my output

tsm: NODE1_TSM>q vol 004164L4

Volume Name Storage Device Estimated Pct Volume
Pool Name Class Name Capacity Util Status
------------------------ ----------- ---------- --------- ----- --------
004164L4 COPYPOOL LTO_STAND- 1.6 T 16.1 Filling
ARD
 
Last edited:

GregE

ADSM.ORG Senior Member
#5
Hi Heada

Thanks for that, is there no way I can re create the secondary copy there and then without having to wait for it to do the backup next time, as that tape may not get read for a few days depending on whatg its backing up.

Thanks
You could run your backup of the corresponding primary pool manually, using the BACKUP STGPOOL command. It will only copy the data from primary pool that doesn't exist in copy pool. In your case, that would be only the data you deleted from the copy pool tape, unless you have backups currently writing to the corresponding primary pool when you launch the backup of the primary pool.
 

ryanbsc

Active Newcomer
#6
thanks

Thanks guys for your help, sorry if I'm asking so many questions and beign a bit slow here.


I tried to do a update volume 004164L4 access=destroyed but get the message

ANR2116E UPDATE VOLUME: Access mode for volume 004164L4 cannot be changed to
"destroyed" - volume does not belong to a primary storage pool.
ANR2212I UPDATE VOLUME: No volumes updated.


So can someone talk me through what the del vol does? and what the discard = yes does, so I know what will happen, and know the process that it is doing?.


Thanks
 

cjhood

ADSM.ORG Moderator
#7
Yeah you can't make a copy tape 'destroyed', you just have to get rid of it.

'del vol <volume_name> discarddata=yes' will force TSM to delete everything on that tape from the database. Since the tape is a copy, and in pieces then you can do this safely.

del vol will remove a tape if there's no valid data on it, 'discarddata=yes' simply makes tsm delete it irrespective of any data still there.

You'll see it go through deleting the files from the tape (it could take a while depending on how big the tape is and how many objects it had on it. Once complete you can then run 'backup stg <primary_pool> <copy_pool>' which will then create a new copy of all the objects which you just deleted.

Hope this helps.

-Chris
 

ryanbsc

Active Newcomer
#8
thanks

HI chris

Thanks for explaining that to me.

Before I'm about ot do that my boss asked me to run a move data command


move data 004164L4 stgpool=copypool

which produces this

ANR2232W This command will move all of the data stored on volume 004164L4 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 (Y)/No (N)) Y
ANR2209W Volume 004164L4 contains no data.
ANS8001I Return code 11.


tsm: NODEA_TSM>q vol 004164L4 f=d

Volume Name: 004164L4
Storage Pool Name: COPYPOOL
Device Class Name: LTO_STANDARD
Estimated Capacity: 0.0 M
Scaled Capacity Applied:
Pct Util: 0.0
Volume Status: Pending
Access: Offsite
Pct. Reclaimable Space: 0.0
Scratch Volume?: Yes
In Error State?: No
Number of Writable Sides: 1
Number of Times Mounted: 2
Write Pass Number: 1
Approx. Date Last Written: 05/08/09 08:09:32
Approx. Date Last Read: 05/08/09 04:52:09
Date Became Pending: 06/08/09 08:29:32
Number of Write Errors: 0
Number of Read Errors: 0
Volume Location: VAULT



Does this mean I dont have to move data and can go ahead and run a delete and then run a backup stg?

thanks
 

cjhood

ADSM.ORG Moderator
#9
Ryan,

It looks like someone has already deleted the volume:

Pct Util: 0.0
Volume Status: Pending
From your earlier post that tape was 16.1% utilized, now it's empty...that tells me that it has been deleted (but is still in TSM due to the reuse delay in your copy stgpool).

But yes, now you can simply run the delete vol command, and then the backup stg. After it finishes you'll have a shiny new copy tape.

-Chris
 

ryanbsc

Active Newcomer
#10
thanks

Thanks chris dont know why it was deleted before I done it..the only thing I tried was to destroy it but that failed
Yes I was curious as to why it has gone from 16% to 0%


so do I run the command backup stg primary pool copy pool

my primary pool is called TAPEPOOL and the secondary copy is COPYPOOL


so I would run backup stg TAPEPOOL COPYPOOL

thanks again for your help sorry for al the questions.
 

cjhood

ADSM.ORG Moderator
#11
No worries at all, that's what we're all here for!

So yes, the storage pool backup command is as you wrote. You shouldn't see any more problems from this point (dropped tapes aside!). Let us know how it goes :)

-Chris
 

ryanbsc

Active Newcomer
#12
done

Thanks chris

Ran the del vol command, this was the output, it jus said return code 14, but I can still query the volume.

tsm: NODEA_TSM>q vol 004164L4

Volume Name Storage Device Estimated Pct Volume
Pool Name Class Name Capacity Util Status
------------------------ ----------- ---------- --------- ----- --------
004164L4 COPYPOOL LTO_STAND- 0.0 M 0.0 Pending
ARD

tsm: NODEA_TSM>q vol 004164L4

Volume Name Storage Device Estimated Pct Volume
Pool Name Class Name Capacity Util Status
------------------------ ----------- ---------- --------- ----- --------
004164L4 COPYPOOL LTO_STAND- 0.0 M 0.0 Pending
ARD

tsm: NODEA_TSM>del volume 004164L4
ANR2220W This command will delete volume 004164L4 from its storage pool after
verifying that the volume contains no data.

Do you wish to proceed? (Yes (Y)/No (N)) Y
ANS8001I Return code 14.

tsm: NODEA_TSM>q vol 004164L4

Volume Name Storage Device Estimated Pct Volume
Pool Name Class Name Capacity Util Status
------------------------ ----------- ---------- --------- ----- --------
004164L4 COPYPOOL LTO_STAND- 0.0 M 0.0 Pending
ARD

tsm: NODEA_TSM>del vol 004164L4 discarddata=yes
ANR2221W This command will result in the deletion of all inventory references
to the data on volume 004164L4, thereby rendering the data unrecoverable.

Do you wish to proceed? (Yes (Y)/No (N)) Y
ANS8001I Return code 14.

tsm: NODEA_TSM>q vol 004164L4

Volume Name Storage Device Estimated Pct Volume
Pool Name Class Name Capacity Util Status
------------------------ ----------- ---------- --------- ----- --------
004164L4 COPYPOOL LTO_STAND- 0.0 M 0.0 Pending


Thanks

Ryan
 

cjhood

ADSM.ORG Moderator
#13
Ah. The volume is currently listed as being 'OFFSITE', so you can't delete it. Update the status to reado/readw/unavail and then do the delete.

-Chris
 

cjhood

ADSM.ORG Moderator
#15
No, sorry should have been clearer:

update vol 004164L4 access=unavail

you could also update to either 'reado' or 'readw'. Either of those three will remove the offsite flag from the tape.
 

ryanbsc

Active Newcomer
#16
not at all

HI chris

no not at all your helping me in a JAM here, so I really appreciate it

Ok I deleted it without runing to discard data and then done a q vol and its now gone

I then ran the backup stg but says nothing to do?

tsm: NODEA_TSM>q vol 004164L4
ANR2034E QUERY VOLUME: No match found using this criteria.
ANS8001I Return code 11.

tsm: NODEA_TSM>backup stg TAPEPOOL COPYPOOL
ANR2111W BACKUP STGPOOL: There is no data to process for TAPEPOOL.
ANS8001I Return code 11.


Thanks

Ryan
 

cjhood

ADSM.ORG Moderator
#17
Have your daily housekeeping tasks run since you started this thread? Your copypool appears to be up to date...

Run this select, it'll tell you if there's been a storage pool backup in the last 24 hours:

select * from summary where start_time >= current_timestamp - 24 hours and activity='STGPOOL BACKUP'

-Chris
 

ryanbsc

Active Newcomer
#18
output

Hi chris I ran your command, this was the out put
There was one ran at 10:49 but that was me, of which said no data to process.


ACTIVITY: STGPOOL BACKUP
NUMBER: 1338
ENTITY: SQLPOOL -> SQLCOPYPOOL
COMMMETH:
ADDRESS:
SCHEDULE_NAME:
EXAMINED: 67
AFFECTED: 67
FAILED: 0
BYTES: 606778688622
IDLE: 0
MEDIAW: 19
PROCESSES: 1
SUCCESSFUL: YES
VOLUME_NAME:
DRIVE_NAME:
LIBRARY_NAME:
LAST_USE:
COMM_WAIT: 0
more... (<ENTER> to continue, 'C' to cancel)

NUM_OFFSITE_VOLS:

START_TIME: 2009-08-05 15:15:55.000000
END_TIME: 2009-08-05 15:15:57.000000
ACTIVITY: STGPOOL BACKUP
NUMBER: 0
ENTITY: TAPEPOOL -> COPYPOOL
COMMMETH:
ADDRESS:
SCHEDULE_NAME:
EXAMINED: 0
AFFECTED: 0
FAILED: 0
BYTES: 0
IDLE: 0
MEDIAW: 0
PROCESSES: 0
SUCCESSFUL: YES
VOLUME_NAME:
DRIVE_NAME:
LIBRARY_NAME:
LAST_USE:
more... (<ENTER> to continue, 'C' to cancel)

COMM_WAIT: 0
NUM_OFFSITE_VOLS:

START_TIME: 2009-08-05 15:15:58.000000
END_TIME: 2009-08-05 15:15:59.000000
ACTIVITY: STGPOOL BACKUP
NUMBER: 0
ENTITY: ORAPOOL -> ORACOPYPOOL
COMMMETH:
ADDRESS:
SCHEDULE_NAME:
EXAMINED: 0
AFFECTED: 0
FAILED: 0
BYTES: 0
IDLE: 0
MEDIAW: 0
PROCESSES: 0
SUCCESSFUL: YES
VOLUME_NAME:
DRIVE_NAME:
LIBRARY_NAME:
more... (<ENTER> to continue, 'C' to cancel)

LAST_USE:
COMM_WAIT: 0
NUM_OFFSITE_VOLS:

START_TIME: 2009-08-05 16:10:46.000000
END_TIME: 2009-08-05 16:18:02.000000
ACTIVITY: STGPOOL BACKUP
NUMBER: 1339
ENTITY: ORAPOOL -> ORACOPYPOOL
COMMMETH:
ADDRESS:
SCHEDULE_NAME:
EXAMINED: 16
AFFECTED: 16
FAILED: 0
BYTES: 41318161104
IDLE: 0
MEDIAW: 69
PROCESSES: 1
SUCCESSFUL: YES
VOLUME_NAME:
DRIVE_NAME:
more... (<ENTER> to continue, 'C' to cancel)

LIBRARY_NAME:
LAST_USE:
COMM_WAIT: 0
NUM_OFFSITE_VOLS:

START_TIME: 2009-08-05 17:01:35.000000
END_TIME: 2009-08-05 17:02:15.000000
ACTIVITY: STGPOOL BACKUP
NUMBER: 1340
ENTITY: ORAPOOL -> ORACOPYPOOL
COMMMETH:
ADDRESS:
SCHEDULE_NAME:
EXAMINED: 13
AFFECTED: 13
FAILED: 0
BYTES: 2753379414
IDLE: 0
MEDIAW: 0
PROCESSES: 1
SUCCESSFUL: YES
VOLUME_NAME:
more... (<ENTER> to continue, 'C' to cancel)

DRIVE_NAME:
LIBRARY_NAME:
LAST_USE:
COMM_WAIT: 0
NUM_OFFSITE_VOLS:

START_TIME: 2009-08-05 17:04:27.000000
END_TIME: 2009-08-05 17:04:27.000000
ACTIVITY: STGPOOL BACKUP
NUMBER: 0
ENTITY: TAPEPOOL -> COPYPOOL
COMMMETH:
ADDRESS:
SCHEDULE_NAME:
EXAMINED: 0
AFFECTED: 0
FAILED: 0
BYTES: 0
IDLE: 0
MEDIAW: 0
PROCESSES: 0
SUCCESSFUL: YES
more... (<ENTER> to continue, 'C' to cancel)

VOLUME_NAME:
DRIVE_NAME:
LIBRARY_NAME:
LAST_USE:
COMM_WAIT: 0
NUM_OFFSITE_VOLS:

START_TIME: 2009-08-05 17:04:27.000000
END_TIME: 2009-08-05 17:06:15.000000
ACTIVITY: STGPOOL BACKUP
NUMBER: 1341
ENTITY: DISKPOOL -> COPYPOOL
COMMMETH:
ADDRESS:
SCHEDULE_NAME:
EXAMINED: 20
AFFECTED: 20
FAILED: 0
BYTES: 2557607936
IDLE: 0
MEDIAW: 19
PROCESSES: 1
more... (<ENTER> to continue, 'C' to cancel)

SUCCESSFUL: YES
VOLUME_NAME:
DRIVE_NAME:
LIBRARY_NAME:
LAST_USE:
COMM_WAIT: 0
NUM_OFFSITE_VOLS:

START_TIME: 2009-08-05 17:48:40.000000
END_TIME: 2009-08-05 18:14:25.000000
ACTIVITY: STGPOOL BACKUP
NUMBER: 1347
ENTITY: SQLPOOL -> SQLCOPYPOOL
COMMMETH:
ADDRESS:
SCHEDULE_NAME:
EXAMINED: 43
AFFECTED: 43
FAILED: 0
BYTES: 309655104160
IDLE: 0
MEDIAW: 28
more... (<ENTER> to continue, 'C' to cancel)

PROCESSES: 1
SUCCESSFUL: YES
VOLUME_NAME:
DRIVE_NAME:
LIBRARY_NAME:
LAST_USE:
COMM_WAIT: 0
NUM_OFFSITE_VOLS:

START_TIME: 2009-08-05 21:12:37.000000
END_TIME: 2009-08-05 21:16:12.000000
ACTIVITY: STGPOOL BACKUP
NUMBER: 1349
ENTITY: ARCHIVEPOOL -> ARCHIVECOPYPOOL
COMMMETH:
ADDRESS:
SCHEDULE_NAME:
EXAMINED: 16451
AFFECTED: 16451
FAILED: 0
BYTES: 1006016273
IDLE: 0
more... (<ENTER> to continue, 'C' to cancel)

MEDIAW: 131
PROCESSES: 1
SUCCESSFUL: YES
VOLUME_NAME:
DRIVE_NAME:
LIBRARY_NAME:
LAST_USE:
COMM_WAIT: 0
NUM_OFFSITE_VOLS:

START_TIME: 2009-08-05 23:58:44.000000
END_TIME: 2009-08-06 00:33:00.000000
ACTIVITY: STGPOOL BACKUP
NUMBER: 1351
ENTITY: ORAPOOL -> ORACOPYPOOL
COMMMETH:
ADDRESS:
SCHEDULE_NAME:
EXAMINED: 138
AFFECTED: 138
FAILED: 0
BYTES: 663652761950
more... (<ENTER> to continue, 'C' to cancel)

IDLE: 0
MEDIAW: 61
PROCESSES: 2
SUCCESSFUL: YES
VOLUME_NAME:
DRIVE_NAME:
LIBRARY_NAME:
LAST_USE:
COMM_WAIT: 0
NUM_OFFSITE_VOLS:

START_TIME: 2009-08-06 01:12:10.000000
END_TIME: 2009-08-06 01:37:24.000000
ACTIVITY: STGPOOL BACKUP
NUMBER: 1355
ENTITY: TAPEPOOL -> COPYPOOL
COMMMETH:
ADDRESS:
SCHEDULE_NAME:
EXAMINED: 293480
AFFECTED: 293480
FAILED: 0
more... (<ENTER> to continue, 'C' to cancel)

BYTES: 108276398965
IDLE: 0
MEDIAW: 430
PROCESSES: 1
SUCCESSFUL: YES
VOLUME_NAME:
DRIVE_NAME:
LIBRARY_NAME:
LAST_USE:
COMM_WAIT: 0
NUM_OFFSITE_VOLS:

START_TIME: 2009-08-06 01:37:24.000000
END_TIME: 2009-08-06 02:14:21.000000
ACTIVITY: STGPOOL BACKUP
NUMBER: 1356
ENTITY: SQLPOOL -> SQLCOPYPOOL
COMMMETH:
ADDRESS:
SCHEDULE_NAME:
EXAMINED: 63
AFFECTED: 63
more... (<ENTER> to continue, 'C' to cancel)

FAILED: 0
BYTES: 366538264946
IDLE: 0
MEDIAW: 308
PROCESSES: 1
SUCCESSFUL: YES
VOLUME_NAME:
DRIVE_NAME:
LIBRARY_NAME:
LAST_USE:
COMM_WAIT: 0
NUM_OFFSITE_VOLS:

START_TIME: 2009-08-06 02:14:22.000000
END_TIME: 2009-08-06 02:14:56.000000
ACTIVITY: STGPOOL BACKUP
NUMBER: 1358
ENTITY: SQLDISKPOOL -> SQLCOPYPOOL
COMMMETH:
ADDRESS:
SCHEDULE_NAME:
EXAMINED: 9
more... (<ENTER> to continue, 'C' to cancel)

AFFECTED: 9
FAILED: 0
BYTES: 5471600640
IDLE: 0
MEDIAW: 0
PROCESSES: 1
SUCCESSFUL: YES
VOLUME_NAME:
DRIVE_NAME:
LIBRARY_NAME:
LAST_USE:
COMM_WAIT: 0
NUM_OFFSITE_VOLS:

START_TIME: 2009-08-06 03:30:51.000000
END_TIME: 2009-08-06 03:35:16.000000
ACTIVITY: STGPOOL BACKUP
NUMBER: 1361
ENTITY: TAPEPOOL -> COPYPOOL
COMMMETH:
ADDRESS:
SCHEDULE_NAME:
more... (<ENTER> to continue, 'C' to cancel)

EXAMINED: 9960
AFFECTED: 9960
FAILED: 0
BYTES: 12642920284
IDLE: 0
MEDIAW: 20
PROCESSES: 1
SUCCESSFUL: YES
VOLUME_NAME:
DRIVE_NAME:
LIBRARY_NAME:
LAST_USE:
COMM_WAIT: 0
NUM_OFFSITE_VOLS:

START_TIME: 2009-08-06 03:35:18.000000
END_TIME: 2009-08-06 03:38:14.000000
ACTIVITY: STGPOOL BACKUP
NUMBER: 1362
ENTITY: SQLPOOL -> SQLCOPYPOOL
COMMMETH:
ADDRESS:
more... (<ENTER> to continue, 'C' to cancel)

SCHEDULE_NAME:
EXAMINED: 10
AFFECTED: 10
FAILED: 0
BYTES: 9254249295
IDLE: 0
MEDIAW: 21
PROCESSES: 1
SUCCESSFUL: YES
VOLUME_NAME:
DRIVE_NAME:
LIBRARY_NAME:
LAST_USE:
COMM_WAIT: 0
NUM_OFFSITE_VOLS:

START_TIME: 2009-08-06 03:38:15.000000
END_TIME: 2009-08-06 03:38:15.000000
ACTIVITY: STGPOOL BACKUP
NUMBER: 0
ENTITY: SQLPOOL -> SQLCOPYPOOL
COMMMETH:
more... (<ENTER> to continue, 'C' to cancel)

ADDRESS:
SCHEDULE_NAME:
EXAMINED: 0
AFFECTED: 0
FAILED: 0
BYTES: 0
IDLE: 0
MEDIAW: 0
PROCESSES: 0
SUCCESSFUL: YES
VOLUME_NAME:
DRIVE_NAME:
LIBRARY_NAME:
LAST_USE:
COMM_WAIT: 0
NUM_OFFSITE_VOLS:

START_TIME: 2009-08-06 10:49:14.000000
END_TIME: 2009-08-06 10:49:15.000000
ACTIVITY: STGPOOL BACKUP
NUMBER: 0
ENTITY: TAPEPOOL -> COPYPOOL
more... (<ENTER> to continue, 'C' to cancel)

START_TIME: 2009-08-06 10:53:01.000000
END_TIME: 2009-08-06 10:53:01.000000
ACTIVITY: STGPOOL BACKUP
NUMBER: 0
more... (<ENTER> to continue, 'C' to cancel)

ENTITY: TAPEPOOL -> COPYPOOL
COMMMETH:
ADDRESS:
SCHEDULE_NAME:
EXAMINED: 0
AFFECTED: 0
FAILED: 0
BYTES: 0
IDLE: 0
MEDIAW: 0
PROCESSES: 0
SUCCESSFUL: YES
VOLUME_NAME:
DRIVE_NAME:
LIBRARY_NAME:
LAST_USE:
COMM_WAIT: 0
NUM_OFFSITE_VOLS:
 

cjhood

ADSM.ORG Moderator
#19
Ok there was also one at 3:30am which did a fair bit of work. Looks as though it's all up to date. If you want to be absolutely sure, run this select:

select char(stgpool_name,22) as stgpool,cast(sum(physical_mb)/1024 as decimal(10,1)) as Physical_GB,cast(sum(logical_mb)/1024 as decimal(10,1)) as logical_gb,sum(num_files) as objects from occupancy group by stgpool_name order by 1

This will display the number of objects in each storage pool, and their sizes. Compare TAPEPOOL and COPYPOOL to be sure the numbers match up, and you're done. If your copypool is larger than the tapepool that might be because DISKPOOL backs up to COPYPOOL, and it may not have migrated to TAPEPOOL yet.

Be aware this select will take a while if you've got a lot of objects in your database.

-Chris
 

ryanbsc

Active Newcomer
#20
thanks

Thank you SO much chris I will run that now and get back to you.


So I guess as that tape is empty, ocudl have been cause we run reclaimation in the early mornig?, but when i posted the value saying the tape was 16% utilised was before reclaim began?

so didnt have to copy over any data?
but will run the command now.


Thanks


Ryan
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 8 23.5%
  • Keep using TSM for Spectrum Protect.

    Votes: 17 50.0%
  • Let's be formal and just say Spectrum Protect

    Votes: 5 14.7%
  • Other (please comement)

    Votes: 4 11.8%

Forum statistics

Threads
30,927
Messages
131,579
Members
21,207
Latest member
Nur03