[ADSM-L] 答复: [ADSM-L] backup stgpool - command issue

2012-05-17 20:49:14
Subject: [ADSM-L] 答复: [ADSM-L] backup stgpool - command issue
From: Victor Shum <victorshum AT CADEX.COM DOT HK>
Date: Fri, 18 May 2012 08:39:14 +0800
Dear Shawn:

Thanks for reply.

The ANR12281 is refer to one of the tape in the primary pool.

So is backup-stgpool use to create another set of tape same as the primary
pool ?  Since the existing tape library slot (48 slot)is not enough to hold
all backup of primary pool; 14 version of user data (each version require 4
to 6 LTO5).  So we try to implement the backup like;

1.  daily schedule backup data to primary pool (daily selective / full
2.  backup stgpool to copypool
3.  backup TSM DB
4.  checkout all tape in the library
5.  check in new tape in the library
6.  checking any expired tape
recycle the daily job

the copypool' tape will be transport to DR site, while the primary pool tape
will be store at the safe and reuse for after 14 day

We think we just daily duplicate the primary pool to copypool (using backup
stgpool), and check out all active tape.  Manually trace when the tape shall
be expire; then reuse (cycle) those tape again to make the things work...

So if we need to have the data retention period of 14 but don't have enough
tape slot in the tape library to hold all primary pool tape media.  We have
no way out !!

OR Shall we just shorter the retention period like: from 14 to 10 day, so
that the tape library can hold all the tape inside.  Use DRM to generate and
manage offsite tape form us ??

Best regards,

Victor Shum

发件人: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] 代表 Shawn
发送时间: 2012年5月18日 3:00
主题: Re: [ADSM-L] backup stgpool - command issue

He mentioned "Due to tape library slot limitation" and "Check out all tape
(current cycle)" I think he is checking out all tapes (including primary
I believe he is trying to manage around primary tapes being requested and
wondering why it was needed in this case.   Also, I think ANR1228I only
refers to primary volumes

backup-stg backs up ALL files that are not already in the copypool.  not
just active files.  Nothing that happened on the client could have caused
this tape to be requested.  The only thing that could have caused an older
primary tape to be requested in a backup-stg process is that, for some
reason, the files that were on that tape were not in the copypool.

This could happen from either:
1 the copy failed the first time.  either the tape was marked unavailable or
destroyed or the backup-stg failed for another reason.  you would receive
log messages about the tape not being available but the process may not have
explicitly failed.  If these tapes were changed to readw/reado in the last
couple days, this could have caused the backup-stg process to request the
old tape.
2 something happened to a copypool volume so that TSM decided that the
data needed to be recopied.   Did you delete any copypool volumes
recently? Any failed reclamations or any processes that could have detected
a fault in a copypool volume?

As mentioned before TSM is designed to work with all the primary volumes
available in the library.  Failing that, it's assumed an operater is
monitoring the activity log to satisfy mount requests.  If you are checking
tapes out every day like this, how are you handling reclamation ?

Shawn Drew


05/17/2012 09:10 AM
Please respond to


Re: [ADSM-L] backup stgpool - command issue


Assuming it is a copy pool volume (since primary storage volumes should
always be available in your library).

Investigate the volume status on your TSM server:
Use the "query drmedia" command determine the volume's current state, if in
fact it should be out of the library it's state would be either "offsite,
courier, vault, etc.". This tells TSM that the volume should not be in the
library and do not attempt to mount it.
If the volume's state is "mountable" then the TSM server thinks the volume
is in the library. Use the "move drmedia" command to apply the correct
status to the volume.

Additionally, check the access status of the volume by using the query
volume command to make sure it is still readwrite, and not readonly or
unavailable, as the server could have altered its access status when it was
unable to use it.

For a complete explanation of the DRM process refer to the admin guide.

Jax, FL.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Victor Shum
Sent: Thursday, May 17, 2012 7:13 AM
Subject: [ADSM-L] backup stgpool - command issue

Dear all :

Due to tape library slot limitation, we implement TSM 6.3 with the following
scenarios :


TS-3200 with 4 x LTO5, 48 slots

TSM configure

3 x primary pool ( A, B, C) for 1 x copy pool (for offsite - off_data)

4 cycle x 7 day of tape media

Daily backup : 4 ~ 8TB


1.       Different hosts running different backup job, so that all the
Drive will be occupy during the daily backup.

2.       At the end of day, we use backup stgpool to make a copy of
primary pool

3.       Check out all tape (current cycle)

4.       Insert a new set of tape

5.       Audit tape library, check in tape..etc

6.       Repeat 1

But we found the backup stgpool cannot be completed last-night.  From the
actlog, it keep report : ANR1228I Removable volume AAA208L5 is required for
storage pool backup. (SESSION: 10245, PROCESS: 199).  While this media was
used for backup in previous cycle (2 weeks ago).

So I am thinking is some of the files has been deleted on the hosts side
yesterday, so the existing tape (inside the tape library) does not content
those files.  But the "backup stgpool" has to copy all "active" files to the
copy-pool; that is why TSM try to mount other tape has the files on it??
Or I just hit a bug of TSM ??

Best regards,

Victor Shum

This message and any attachments (the "message") is intended solely for the
addressees and is confidential. If you receive this message in error, please
delete it and immediately notify the sender. Any use not in accord with its
purpose, any dissemination or disclosure, either whole or partial, is
prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that
certain functions and services for BNP Paribas may be performed by BNP
Paribas RCC, Inc.