Re: : TSM Running out of Scratch Tapes
Hello, From the errors, it seems you are getting these against 2 Drives. * You can check through the actlog messages just before and after ANR8355E message to see what ishappening? * You can check those Tape Drive Device names in their paths are correct as seen on from OS? * You can verify if the Firmware of Tape/Drives and Library are on compatible levels with your environment. * You can try to run Audit from ACSLS and from TSM Server to match the inventory on both. * While checking in brand new scratch tapes(volumes), Label Libvol command should be used. Thanks Regards, Faisal Khan On Tue, Jul 9, 2013 at 8:31 AM, Adeel Mehmood ad.mehm...@diyarme.comwrote: Dears , We are receiving below errors and the Scratch tapes goes to ZERO 07/04/2013 22:58:44 ANR8355E I/O error reading label for volume 001736 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32773) 07/04/2013 23:04:23 ANR8355E I/O error reading label for volume 000588 in drive DRIVE4 (mt7.0.0.1). (SESSION: 32799) 07/04/2013 23:04:35 ANR8355E I/O error reading label for volume 000482 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32806) 07/04/2013 23:10:55 ANR8355E I/O error reading label for volume 001058 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:11:01 ANR8355E I/O error reading label for volume 002081 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:15:49 ANR8355E I/O error reading label for volume 000468 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:16:21 ANR8355E I/O error reading label for volume 000828 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:20:33 ANR8355E I/O error reading label for volume 002284 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:21:13 ANR8355E I/O error reading label for volume 002084 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:26:29 ANR8355E I/O error reading label for volume 001367 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:28:24 ANR8355E I/O error reading label for volume 000386 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34215) 07/04/2013 23:36:08 ANR8355E I/O error reading label for volume 001804 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34215) 07/04/2013 23:37:04 ANR8355E I/O error reading label for volume 002323 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34255) 07/04/2013 23:44:47 ANR8355E I/O error reading label for volume 001814 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:45:05 ANR8355E I/O error reading label for volume 002535 in drive DRIVE4 (mt7.0.0.1). (SESSION: 24769) Thanks best regards, Adeel Mehmood From: Adeel Mehmood Sent: Tuesday, July 9, 2013 7:36 AM To: ADSM-L@VM.MARIST.EDU Subject: RE: [ADSM-L] : TSM Running out of Scratch Tapes Dear , Thanks for your response . please find the answers below . It is most useful if you state which version of TSM server you are running. -- TSM 6.2 The OS it runs on and the tape media (LTO3/4/5 etc.) would be helpful Windows 2008 Server , configured with SL3000 Library through ACSLS Software having 14 x HP LTO4 FC Tape Drives. What retention policies are in place for the domain copy groups? If NOLIMIT is in force, then data will never expire and will eventually use all of your tapes Retention Polices seems to be working fine as they are In place for more than two years half years and we started facing this problem couple of weeks back . When you say tapes are becoming 'unavailable', is this the status of the volume within TSM? (Do a 'q vol f=d' to check). If so, this is often because you are trying to use tapes that have been physically removed from the library. If TSM wants to use that tape, it will eventually place the tape in an 'UNAVAILABLE' state because it cannot mount the volume in the library as a result of being removed. - we are 100 % sure that the tapes are physically inside .The NEW/OLD tapes become UNAVAILABLE , whenever the TSM try to use them for backup or restore. but once we make them available , we could use them for some time . till they get unavailable again . In terms of running low on scratch, as the previous poster said, make sure expiration and reclaim is running. In particular, make sure reclaim is running and actually completing. The SUMMARY table will report on expiration and reclaim activity over a period of time (usually 28 days) - we double check the same. How many versions of database backups do you
Re: TDP for Exchange2010 6.4.0.0 Incremental backups not truncating logs
Del, We are set up in a DAG, but the problem only seems to be with the incremental (log) backups. The full backup truncates the logs fine, but the log backups do not. On our Exchange 2007 servers using TDP 5.5 the logs were truncated after either a full or a log backup. has this changed with TDP 6.4 and if not, where should I see indication that TSM is instructing Exchange to perform the truncation? Thanks, -steve -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del Hoobler Sent: Monday, July 08, 2013 10:12 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP for Exchange2010 6.4.0.0 Incremental backups not truncating logs Hi Steve, With Exchange 2010, especially when set up in a Database Availability Group (DAG), the log truncation can be delayed because Exchange must make sure all log updates are sent and committed in all copies (active and passive) before it truncates the logs. A backup product (like TSM) completes a full backup and reports the backup is successful to Exchange. It is then the responsibility of Exchange to perform the actual log file truncation. You should see evidence of this notification to truncate logs in the Windows Event log. We have seen cases when Exchange is still failing to truncate logs. In those cases, customers have needed to engage Microsoft support to find what is preventing Exchange from performing the log truncation. Thanks, Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 07/08/2013 09:42:04 AM: From: Schaub, Steve steve_sch...@bcbst.com To: ADSM-L@vm.marist.edu, Date: 07/08/2013 09:42 AM Subject: TDP for Exchange2010 6.4.0.0 Incremental backups not truncating logs Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Tsm server 6.2.4.0 Tsm client 6.4.0.0 Tdp client 6.4.0.0 I have powershell scripts running our full incremental Exchange 2010 backups. The full backups truncate the logs, but the incremental do not. I've read through the doc and googled, but haven't found any reason. Nothing obvious showing up in the app logs. Any help would be appreciated. Here are the pertinent commands/files: incremental backup command: .\TDPEXCC BACKUP * INCREMENTAL /PreferDAGPassive / MinimumBackupInterval=10 /SkipIntegrityCheck /DAGNode=EXCHANGE2010 / BackupMethod=VSS /BackupDestination=TSM /LogFile=$myTsmSchedLog $myTempFile results: VSS Backup operation completed with rc = 0 Files Examined : 3530 Files Completed : 3530 Files Failed : 0 Files Deduplicated : 0 Total Bytes Inspected: 3620460520 Total Bytes : 3622488810 Total LanFree Bytes : 0 Total Bytes Before Deduplication : 0 Total Bytes After Deduplication : 0 Files Compressed By : 0% Deduplication Reduction : 0.00% Total Data Reduction Ratio : 0.00% The operation completed successfully. (rc = 0) dsm.opt: * * Tivoli Storage Manager - BCBST Win Servers TDP Exchange Clients *Installed Fri 04/19/2013 11:30:58.60 * * * Identification Section * nodename _MAIL tcpserveraddress .bcbst.com tcpport5002 tcpclientaddress .bcbst.com tcpclientport 1510 tcpcadaddress localhost tcpclientport 1510 HTTPport 1581 webports 1503,1504 * * TCP/IP Section * commmethod TCPIP tcpbuffsize512 tcpwindowsize 1024 diskbuffsize 32 * * CAD/Schedule Settings Section * managedservicesschedule errorlogretention 90 schedlogretention 14 schedmode polling queryschedperiod 1 * * Misc Section * clusternodeno passwordaccess Generate tdpexc.cfg: * * IBM Tivoli Storage Manager for Mail * Data Protection for Exchange Configuration File * LogFile tdpsched.log LogPrune 90 MountWaitForData Yes MountWait
Re: : TSM Running out of Scratch Tapes
Hello,
to add
1) Check if there is mismatch between tapes and drives (mean lto3 tapes for
LTO5 tapes)
2) check inf those tapes that you are inserting into library have been
properly labeled (check output from label libvol command)
3) I can not see in your log last 2 symbols about tape LTO generation I
mean xxxyyy*L4*
4) check to see in bar codes for new tapes are check summed or not and
verify library setting about this...
On Tue, Jul 9, 2013 at 9:09 AM, Faisal Khan faisal...@gmail.com wrote:
Hello,
From the errors, it seems you are getting these against 2 Drives.
* You can check through the actlog messages just before and after
ANR8355E message to see what ishappening?
* You can check those Tape Drive Device names in their paths are correct as
seen on from OS?
* You can verify if the Firmware of Tape/Drives and Library are on
compatible levels with your environment.
* You can try to run Audit from ACSLS and from TSM Server to match the
inventory on both.
* While checking in brand new scratch tapes(volumes), Label Libvol
command should be used.
Thanks Regards,
Faisal Khan
On Tue, Jul 9, 2013 at 8:31 AM, Adeel Mehmood ad.mehm...@diyarme.com
wrote:
Dears ,
We are receiving below errors and the Scratch tapes goes to ZERO
07/04/2013 22:58:44 ANR8355E I/O error reading label for volume
001736 in
drive DRIVE15 (mt10.0.0.2). (SESSION: 32773)
07/04/2013 23:04:23 ANR8355E I/O error reading label for volume
000588 in
drive DRIVE4 (mt7.0.0.1). (SESSION: 32799)
07/04/2013 23:04:35 ANR8355E I/O error reading label for volume
000482 in
drive DRIVE15 (mt10.0.0.2). (SESSION: 32806)
07/04/2013 23:10:55 ANR8355E I/O error reading label for volume
001058 in
drive DRIVE4 (mt7.0.0.1). (SESSION: 34240)
07/04/2013 23:11:01 ANR8355E I/O error reading label for volume
002081 in
drive DRIVE15 (mt10.0.0.2). (SESSION: 34242)
07/04/2013 23:15:49 ANR8355E I/O error reading label for volume
000468 in
drive DRIVE15 (mt10.0.0.2). (SESSION: 34242)
07/04/2013 23:16:21 ANR8355E I/O error reading label for volume
000828 in
drive DRIVE4 (mt7.0.0.1). (SESSION: 34240)
07/04/2013 23:20:33 ANR8355E I/O error reading label for volume
002284 in
drive DRIVE15 (mt10.0.0.2). (SESSION: 34242)
07/04/2013 23:21:13 ANR8355E I/O error reading label for volume
002084 in
drive DRIVE4 (mt7.0.0.1). (SESSION: 34240)
07/04/2013 23:26:29 ANR8355E I/O error reading label for volume
001367 in
drive DRIVE15 (mt10.0.0.2). (SESSION: 34255)
07/04/2013 23:28:24 ANR8355E I/O error reading label for volume
000386 in
drive DRIVE4 (mt7.0.0.1). (SESSION: 34215)
07/04/2013 23:36:08 ANR8355E I/O error reading label for volume
001804 in
drive DRIVE15 (mt10.0.0.2). (SESSION: 34215)
07/04/2013 23:37:04 ANR8355E I/O error reading label for volume
002323 in
drive DRIVE4 (mt7.0.0.1). (SESSION: 34255)
07/04/2013 23:44:47 ANR8355E I/O error reading label for volume
001814 in
drive DRIVE15 (mt10.0.0.2). (SESSION: 34255)
07/04/2013 23:45:05 ANR8355E I/O error reading label for volume
002535 in
drive DRIVE4 (mt7.0.0.1). (SESSION: 24769)
Thanks best regards,
Adeel Mehmood
From: Adeel Mehmood
Sent: Tuesday, July 9, 2013 7:36 AM
To: ADSM-L@VM.MARIST.EDU
Subject: RE: [ADSM-L] : TSM Running out of Scratch Tapes
Dear ,
Thanks for your response . please find the answers below .
It is most useful if you state which version of TSM server you are
running. -- TSM 6.2
The OS it runs on and the tape media (LTO3/4/5 etc.) would be helpful
Windows 2008 Server , configured with SL3000
Library
through ACSLS Software having 14 x HP LTO4 FC Tape Drives.
What retention policies are in place for the domain copy groups? If
NOLIMIT is in force, then data will never expire and will eventually use
all of your tapes
Retention Polices seems to be working fine as they are In place
for
more than two years half years and we started facing this problem
couple
of weeks back .
When you say tapes are becoming 'unavailable', is this the status of the
volume within TSM? (Do a 'q vol f=d' to check). If so, this is often
because you are trying to use tapes that have been physically removed
from
the library. If TSM wants to use that tape, it will eventually place the
tape in an 'UNAVAILABLE' state because it cannot mount the volume in the
library as a result of being removed.
- we are 100 % sure
Re: TDP for Exchange2010 6.4.0.0 Incremental backups not truncating logs
Hi Steve, You were most likely using legacy (streaming) backups with Exchange 2007. Exchange 2010 uses VSS backups because Microsoft dropped the legacy backup method starting with Exchange 2010. These two methods of backup use a very different API. The four backup types have not changed, however: - Full = back up database and logs, truncate logs - Copy = back up database and logs, do NOT truncate logs - Incremental = back up logs, truncate logs - Differential = back up logs, do NOT truncate logs From a Data Protection for Exchange perspective the backup operation and log file truncation behavior has not changed. With VSS backups, Data Protection for Exchange does not tell Exchange to truncate the logs, it simply reports that the backup was successful. From that report of a successful backup, Exchange will schedule the log truncation at the most opportune time, depending on DAG database replication health and status. You should see an indication in the Windows Event Log that the backup was completed successfully and another one about log truncation. If you continue to see problems, you could open a PMR. The TSM support team will most likely ask you to also get Microsoft involved since these log truncation issues usually end up being something in Exchange itself. Thanks, Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 07/09/2013 05:09:16 AM: From: Schaub, Steve steve_sch...@bcbst.com To: ADSM-L@vm.marist.edu, Date: 07/09/2013 05:10 AM Subject: Re: TDP for Exchange2010 6.4.0.0 Incremental backups not truncating logs Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Del, We are set up in a DAG, but the problem only seems to be with the incremental (log) backups. The full backup truncates the logs fine, but the log backups do not. On our Exchange 2007 servers using TDP 5.5 the logs were truncated after either a full or a log backup. has this changed with TDP 6.4 and if not, where should I see indication that TSM is instructing Exchange to perform the truncation? Thanks, -steve
Re: : TSM Running out of Scratch Tapes
From the messages, TSM is using 6 character tape labels. Is that your intent and has it always been so? Is your tape library and OS also using 6 character tape labels or might they be using 8 characters? David -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Adeel Mehmood Sent: Tuesday, July 09, 2013 1:32 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] : TSM Running out of Scratch Tapes Dears , We are receiving below errors and the Scratch tapes goes to ZERO 07/04/2013 22:58:44 ANR8355E I/O error reading label for volume 001736 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32773) 07/04/2013 23:04:23 ANR8355E I/O error reading label for volume 000588 in drive DRIVE4 (mt7.0.0.1). (SESSION: 32799) 07/04/2013 23:04:35 ANR8355E I/O error reading label for volume 000482 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32806) 07/04/2013 23:10:55 ANR8355E I/O error reading label for volume 001058 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:11:01 ANR8355E I/O error reading label for volume 002081 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:15:49 ANR8355E I/O error reading label for volume 000468 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:16:21 ANR8355E I/O error reading label for volume 000828 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:20:33 ANR8355E I/O error reading label for volume 002284 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:21:13 ANR8355E I/O error reading label for volume 002084 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:26:29 ANR8355E I/O error reading label for volume 001367 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:28:24 ANR8355E I/O error reading label for volume 000386 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34215) 07/04/2013 23:36:08 ANR8355E I/O error reading label for volume 001804 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34215) 07/04/2013 23:37:04 ANR8355E I/O error reading label for volume 002323 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34255) 07/04/2013 23:44:47 ANR8355E I/O error reading label for volume 001814 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:45:05 ANR8355E I/O error reading label for volume 002535 in drive DRIVE4 (mt7.0.0.1). (SESSION: 24769) Thanks best regards, Adeel Mehmood From: Adeel Mehmood Sent: Tuesday, July 9, 2013 7:36 AM To: ADSM-L@VM.MARIST.EDU Subject: RE: [ADSM-L] : TSM Running out of Scratch Tapes Dear , Thanks for your response . please find the answers below . It is most useful if you state which version of TSM server you are running. -- TSM 6.2 The OS it runs on and the tape media (LTO3/4/5 etc.) would be helpful Windows 2008 Server , configured with SL3000 Library through ACSLS Software having 14 x HP LTO4 FC Tape Drives. What retention policies are in place for the domain copy groups? If NOLIMIT is in force, then data will never expire and will eventually use all of your tapes Retention Polices seems to be working fine as they are In place for more than two years half years and we started facing this problem couple of weeks back . When you say tapes are becoming 'unavailable', is this the status of the volume within TSM? (Do a 'q vol f=d' to check). If so, this is often because you are trying to use tapes that have been physically removed from the library. If TSM wants to use that tape, it will eventually place the tape in an 'UNAVAILABLE' state because it cannot mount the volume in the library as a result of being removed. - we are 100 % sure that the tapes are physically inside .The NEW/OLD tapes become UNAVAILABLE , whenever the TSM try to use them for backup or restore. but once we make them available , we could use them for some time . till they get unavailable again . In terms of running low on scratch, as the previous poster said, make sure expiration and reclaim is running. In particular, make sure reclaim is running and actually completing. The SUMMARY table will report on expiration and reclaim activity over a period of time (usually 28 days) - we double check the same. How many versions of database backups do you retain? -- 14 versions These are common causes of tape problems. -- we are using Brand New Tapes and they are also getting UNAVAILABLE , also we opened a case with Library Vendor and they said all is well . Best regards, Adeel -Original Message- From: ADSM: Dist Stor
Re: Archive WEB UI not showing available Management classes in windows.
Hi Grant, You don't specify your client version, but I am guessing 6.3.1. In which case, the issue you describe is documented by APAR IC90223. Try the 6.3.1.2 client, which just went out last week. I believe that contains a fix for this. - Andy Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | stor...@us.ibm.com IBM Tivoli Storage Manager links: Product support: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager Online documentation: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli Documentation Central/page/Tivoli Storage Manager Product Wiki: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Storage+Manager/page/Home ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2013-07-09 00:43:13: From: Grant Street gra...@al.com.au To: ADSM-L@vm.marist.edu, Date: 2013-07-09 00:43 Subject: Archive WEB UI not showing available Management classes in windows. Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Hello Has anyone seen an issue where the the Java based web client on a windows client does not show anything in the Management class drop down box on the Archive window? Maybe I missing something? Grant
Re: : TSM Running out of Scratch Tapes
David If I remember right, ACSLS only ever uses 6 char labels, Adeel, you need to either buy your tapes pre-labelled or label them yourself before first use using the label libvol command,. Did you do that? If it is only the new tapes that are having the problem, that is what I would suspect. Regards Steve Steven Harris TSM Admin Canberra Australia On 9/07/2013 10:08 PM, Ehresman,David E. wrote: From the messages, TSM is using 6 character tape labels. Is that your intent and has it always been so? Is your tape library and OS also using 6 character tape labels or might they be using 8 characters? David -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Adeel Mehmood Sent: Tuesday, July 09, 2013 1:32 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] : TSM Running out of Scratch Tapes Dears , We are receiving below errors and the Scratch tapes goes to ZERO 07/04/2013 22:58:44 ANR8355E I/O error reading label for volume 001736 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32773) 07/04/2013 23:04:23 ANR8355E I/O error reading label for volume 000588 in drive DRIVE4 (mt7.0.0.1). (SESSION: 32799) 07/04/2013 23:04:35 ANR8355E I/O error reading label for volume 000482 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32806) 07/04/2013 23:10:55 ANR8355E I/O error reading label for volume 001058 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:11:01 ANR8355E I/O error reading label for volume 002081 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:15:49 ANR8355E I/O error reading label for volume 000468 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:16:21 ANR8355E I/O error reading label for volume 000828 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:20:33 ANR8355E I/O error reading label for volume 002284 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:21:13 ANR8355E I/O error reading label for volume 002084 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:26:29 ANR8355E I/O error reading label for volume 001367 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:28:24 ANR8355E I/O error reading label for volume 000386 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34215) 07/04/2013 23:36:08 ANR8355E I/O error reading label for volume 001804 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34215) 07/04/2013 23:37:04 ANR8355E I/O error reading label for volume 002323 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34255) 07/04/2013 23:44:47 ANR8355E I/O error reading label for volume 001814 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:45:05 ANR8355E I/O error reading label for volume 002535 in drive DRIVE4 (mt7.0.0.1). (SESSION: 24769) Thanks best regards, Adeel Mehmood From: Adeel Mehmood Sent: Tuesday, July 9, 2013 7:36 AM To: ADSM-L@VM.MARIST.EDU Subject: RE: [ADSM-L] : TSM Running out of Scratch Tapes Dear , Thanks for your response . please find the answers below . It is most useful if you state which version of TSM server you are running. -- TSM 6.2 The OS it runs on and the tape media (LTO3/4/5 etc.) would be helpful Windows 2008 Server , configured with SL3000 Library through ACSLS Software having 14 x HP LTO4 FC Tape Drives. What retention policies are in place for the domain copy groups? If NOLIMIT is in force, then data will never expire and will eventually use all of your tapes Retention Polices seems to be working fine as they are In place for more than two years half years and we started facing this problem couple of weeks back . When you say tapes are becoming 'unavailable', is this the status of the volume within TSM? (Do a 'q vol f=d' to check). If so, this is often because you are trying to use tapes that have been physically removed from the library. If TSM wants to use that tape, it will eventually place the tape in an 'UNAVAILABLE' state because it cannot mount the volume in the library as a result of being removed. - we are 100 % sure that the tapes are physically inside .The NEW/OLD tapes become UNAVAILABLE , whenever the TSM try to use them for backup or restore. but once we make them available , we could use them for some time . till they get unavailable again . In terms of running low on scratch, as the previous poster said, make sure expiration and reclaim is running. In particular, make sure reclaim is running and actually completing. The SUMMARY table will report on expiration and reclaim
Re: TSM for SAP w/Oracle RMAN
Wanda, Tell them to always run with the exact same multiplexing and restore sessions as they did when backing up (match multiplexing and backup sessions) In the initSID.utl file there is also a MAXBACKSESSIONS and a MAXRESTORESESSIONS etc... your maxsessions and sessions needs to be set at the max expected to run at any given time and then your maxback and maxrestore need to be the same. If it is really really slow and running on windows, look for a nic that's out of whack... and by that I mean a duplex irregularity (full on switch and half on windows side) but you've probably already looked at that... (even now a days some 10+ years after first running into that issue I still see it happening *sigh*) Only last thing would be maxnummp of the client but that would throw an error that would be in their brrestore log when TSM didn't allow a tape mount. Hope this helps, Later, Dwight -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Monday, July 08, 2013 6:08 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM for SAP w/Oracle RMAN TSM 6.3.3 on Windows (server), TDP for SAP on Oracle 6.4, TSM client 6.4.0.0 on Linux. The Oracle DBs are compressed. OK, I'm just the back-end server support. No speakum SAP. DBA did the support to set up SAP/TDP with RMAN, I'm pretty clueless. Backups have been running beautifully, for months. Then he left, alas. Now a new different DBA is trying to get restores to run and they are slow as dirt. One obvious problem is that on backups 2 sessions run in parallel, which back up in 4 total sessions as viewed from the server side. Upon the restore they are running one at a time. I know where to find the api/bin64 directory with the appropriate dsm.sys, and I know where to find the /oracle/SID/112_64/dbs directory and look at the initSID.utl file. That file has maxsessions 2 in it. Where else should I look to see why the restore is only starting 1 session at a time? Is that something controlled via BRtools or RMAN? W Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.com ICF International | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | 410.539.1135 (o)
Re: : TSM Running out of Scratch Tapes
Dear All, below steps has been used to checkin the new or offsite tapes as SCRATCH to the library . Please advise , if they can be improved further to solve this issue checkin libvolume sl3kacslib search=yes status=scratch checklabel=no label libvolume sl3kacslib search=yes overwrite=no checkin=scratch Thx, Adeel -Original Message- From: Richard Sims [mailto:r...@bu.edu] Sent: Tuesday, July 9, 2013 3:47 PM To: Adeel Mehmood Subject: Re: : TSM Running out of Scratch Tapes Those messages, in conjunction with your statement that these are new tapes, indicates that the problem is simply that you have not labeled them, as is fundamental when adding new tapes to a library. See that message number in http://people.bu.edu/rbs/ADSM.QuickFacts. Richard On Jul 9, 2013, at 1:31 AM, Adeel Mehmood ad.mehm...@diyarme.com wrote: Dears , We are receiving below errors and the Scratch tapes goes to ZERO 07/04/2013 22:58:44 ANR8355E I/O error reading label for volume 001736 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32773) 07/04/2013 23:04:23 ANR8355E I/O error reading label for volume 000588 in drive DRIVE4 (mt7.0.0.1). (SESSION: 32799) 07/04/2013 23:04:35 ANR8355E I/O error reading label for volume 000482 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32806) 07/04/2013 23:10:55 ANR8355E I/O error reading label for volume 001058 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:11:01 ANR8355E I/O error reading label for volume 002081 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:15:49 ANR8355E I/O error reading label for volume 000468 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:16:21 ANR8355E I/O error reading label for volume 000828 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:20:33 ANR8355E I/O error reading label for volume 002284 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:21:13 ANR8355E I/O error reading label for volume 002084 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:26:29 ANR8355E I/O error reading label for volume 001367 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:28:24 ANR8355E I/O error reading label for volume 000386 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34215) 07/04/2013 23:36:08 ANR8355E I/O error reading label for volume 001804 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34215) 07/04/2013 23:37:04 ANR8355E I/O error reading label for volume 002323 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34255) 07/04/2013 23:44:47 ANR8355E I/O error reading label for volume 001814 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:45:05 ANR8355E I/O error reading label for volume 002535 in drive DRIVE4 (mt7.0.0.1). (SESSION: 24769) Thanks best regards, Adeel Mehmood D I S C L A I M E R The information in this email and in any files transmitted with it, is intended only for the addressee and may contain confidential and/or privileged material. Access to this email by anyone else is unauthorized. If you receive this in error, please contact the sender immediately and delete the material from any computer. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is strictly prohibited. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of the company.
Re: : TSM Running out of Scratch Tapes
On Jul 9, 2013, at 9:12 AM, Adeel Mehmood ad.mehm...@diyarme.com wrote: Dear All, below steps has been used to checkin the new or offsite tapes as SCRATCH to the library . Please advise , if they can be improved further to solve this issue checkin libvolume sl3kacslib search=yes status=scratch checklabel=no label libvolume sl3kacslib search=yes overwrite=no checkin=scratch Thx, Adeel I would recommend reviewing your Activity Log during the above operations to see how those operations actually did. Take one of the problem tapes and perform a 'dd' or like command to pull in the leading content of the tape, to see if there is actually a standard label there, and compare that to what's on one of your good tapes. Perform an explicit labeling operation on one of the problem tapes and attempt to use it. Richard Sims
Re: : TSM Running out of Scratch Tapes
Do you use library sharing? If you do, make sure the encryption settings on the device classes are the same on all the library clients. The label itself will be encrypted if the device class allows, and a library client with encryption disabled will not try to re-label the volume if it sees an encrypted label. -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine On 07/08/13 22:31, Adeel Mehmood wrote: Dears , We are receiving below errors and the Scratch tapes goes to ZERO 07/04/2013 22:58:44 ANR8355E I/O error reading label for volume 001736 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32773) 07/04/2013 23:04:23 ANR8355E I/O error reading label for volume 000588 in drive DRIVE4 (mt7.0.0.1). (SESSION: 32799) 07/04/2013 23:04:35 ANR8355E I/O error reading label for volume 000482 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32806) 07/04/2013 23:10:55 ANR8355E I/O error reading label for volume 001058 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:11:01 ANR8355E I/O error reading label for volume 002081 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:15:49 ANR8355E I/O error reading label for volume 000468 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:16:21 ANR8355E I/O error reading label for volume 000828 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:20:33 ANR8355E I/O error reading label for volume 002284 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:21:13 ANR8355E I/O error reading label for volume 002084 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:26:29 ANR8355E I/O error reading label for volume 001367 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:28:24 ANR8355E I/O error reading label for volume 000386 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34215) 07/04/2013 23:36:08 ANR8355E I/O error reading label for volume 001804 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34215) 07/04/2013 23:37:04 ANR8355E I/O error reading label for volume 002323 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34255) 07/04/2013 23:44:47 ANR8355E I/O error reading label for volume 001814 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:45:05 ANR8355E I/O error reading label for volume 002535 in drive DRIVE4 (mt7.0.0.1). (SESSION: 24769) Thanks best regards, Adeel Mehmood From: Adeel Mehmood Sent: Tuesday, July 9, 2013 7:36 AM To: ADSM-L@VM.MARIST.EDU Subject: RE: [ADSM-L] : TSM Running out of Scratch Tapes Dear , Thanks for your response . please find the answers below . It is most useful if you state which version of TSM server you are running. -- TSM 6.2 The OS it runs on and the tape media (LTO3/4/5 etc.) would be helpful Windows 2008 Server , configured with SL3000 Library through ACSLS Software having 14 x HP LTO4 FC Tape Drives. What retention policies are in place for the domain copy groups? If NOLIMIT is in force, then data will never expire and will eventually use all of your tapes Retention Polices seems to be working fine as they are In place for more than two years half years and we started facing this problem couple of weeks back . When you say tapes are becoming 'unavailable', is this the status of the volume within TSM? (Do a 'q vol f=d' to check). If so, this is often because you are trying to use tapes that have been physically removed from the library. If TSM wants to use that tape, it will eventually place the tape in an 'UNAVAILABLE' state because it cannot mount the volume in the library as a result of being removed. - we are 100 % sure that the tapes are physically inside .The NEW/OLD tapes become UNAVAILABLE , whenever the TSM try to use them for backup or restore. but once we make them available , we could use them for some time . till they get unavailable again . In terms of running low on scratch, as the previous poster said, make sure expiration and reclaim is running. In particular, make sure reclaim is running and actually completing. The SUMMARY table will report on expiration and reclaim activity over a period of time (usually 28 days) - we double check the same. How many versions of database backups do you retain? -- 14 versions These are common causes of tape problems. -- we are using Brand New Tapes and they are also getting
Re: query archive returns nothing
One also needs to be careful about filespace boundaries - dsmc will not traverse nor even display a filespace in a lower-level directory unless its mountpoint was also backed up as a directory in that lower-level filespace. -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine On 07/08/13 15:15, Erwann Simon wrote: Geoff, Let's try with a trailing /or putting quotes around your file specification. Be careful with the shell interpreting the star and not the TSM Client. I think that a user who archives files becomes the owner of the archives and should be able to queriy them. Erwann Geoff Gill avalnch...@yahoo.com a écrit : I was wondering if perhaps this makes sense to anyone. While logged on as a user, not root, an archive is run. dsmc archive /var/log/test/* with -deletefiles. archive ran, shows 8 files archived and 5 files deleted. dsmc q archive /var/log/test/* -subdir yes, dsmc q archive /var/log/test, dsmc q archive /var/log/test -subdir=yes all return ANS1092W No files matching search criteria were found. So the question: Is it possible a user could archive files and not see anything with the query? Is it possible I have a client level problem, which I'm trying to research now. what else am I missing? I have asked them to log in as root and do the query but won't get a response till tomorrow so I thought I'd see I got any hits here. Thank You Geoff Gill
Re: FW: [ADSM-L] Should CBT be enabled before using TSM for VE to save space?
I don't think this is correct, TSM for Virtual Environments (and even just the BA client with a simple full backup) will only backup the blocks that are in use inside the .vmdk file, this information is provided by the vSphere storage API. On Tue, Jul 9, 2013 at 3:15 AM, Stackwick, Stephen stephen.stackw...@icfi.com wrote: According to this: http://www-01.ibm.com/support/docview.wss?uid=swg21641914myns=swgtivmynp=OCSS8TDQmync=E TSM4VE backs up the whole disk. And that's been my experience. Steve STEPHEN STACKWICK | Senior Consultant | 301.518.6352 (m) | stephen.stackw...@icfi.com | icfi.com ICF INTERNATIONAL | 410 E. Pratt Street Suite 2214, Baltimore, MD 21202 | 410.539.1135 (o) -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Robert Ouzen Sent: Monday, July 08, 2013 8:58 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] FW: [ADSM-L] Should CBT be enabled before using TSM for VE to save space? Hi Wanda No quite sure at least in Vsphere 5 (maybe Vsphere 5.1) , I always check with the command: dsmc show VM all and the parameter : changeTracking: Off About the first backup will take only the USED space , at least in my environment some machines works fine but some others backup the ALL space !!! Best Regards Robert -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Monday, July 08, 2013 3:47 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Should CBT be enabled before using TSM for VE to save space? If your VM's were created in VSphere 5, CBT will be on by default. My understanding is that either way (starting with CBT on or off), you should only get USED space on the first backup. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Michael Roesch Sent: Monday, July 08, 2013 4:29 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Should CBT be enabled before using TSM for VE to save space? Hi there, I've read here http://www-01.ibm.com/support/docview.wss?uid=swg21608413 that TSM for VE is using content-aware backup, if CBT is enabled. It also says that TSM for VE will enable CBT after the first backup. So I'm wondering if enabling CBT before performing the first backup would make TSM for VE backup only the used blocks (i.e. used space) and hence would save space on the storage pool? Or would TSM for VE still backup the full VMDK, including possible lots of unused space inside it on the first backup? Regards, Michael
Re: : TSM Running out of Scratch Tapes
If you first run a checkin libvol before labeling them, TSM won't probably find any tapes to label. Run the following command to checkout all new tapes: Checkout libvol libraryname volumename checkl=n remove=n Now run the following command to label them: Label libv libraryname search=y labels=b checkin=scratch This will put a label on the tapes and check them in as scratch. Kind regards, Eric van Loon AF/KLM Storage Engineering -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Adeel Mehmood Sent: dinsdag 9 juli 2013 15:12 To: ADSM-L@VM.MARIST.EDU Subject: Re: : TSM Running out of Scratch Tapes Dear All, below steps has been used to checkin the new or offsite tapes as SCRATCH to the library . Please advise , if they can be improved further to solve this issue checkin libvolume sl3kacslib search=yes status=scratch checklabel=no label libvolume sl3kacslib search=yes overwrite=no checkin=scratch Thx, Adeel -Original Message- From: Richard Sims [mailto:r...@bu.edu] Sent: Tuesday, July 9, 2013 3:47 PM To: Adeel Mehmood Subject: Re: : TSM Running out of Scratch Tapes Those messages, in conjunction with your statement that these are new tapes, indicates that the problem is simply that you have not labeled them, as is fundamental when adding new tapes to a library. See that message number in http://people.bu.edu/rbs/ADSM.QuickFacts. Richard On Jul 9, 2013, at 1:31 AM, Adeel Mehmood ad.mehm...@diyarme.com wrote: Dears , We are receiving below errors and the Scratch tapes goes to ZERO 07/04/2013 22:58:44 ANR8355E I/O error reading label for volume 001736 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32773) 07/04/2013 23:04:23 ANR8355E I/O error reading label for volume 000588 in drive DRIVE4 (mt7.0.0.1). (SESSION: 32799) 07/04/2013 23:04:35 ANR8355E I/O error reading label for volume 000482 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32806) 07/04/2013 23:10:55 ANR8355E I/O error reading label for volume 001058 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:11:01 ANR8355E I/O error reading label for volume 002081 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:15:49 ANR8355E I/O error reading label for volume 000468 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:16:21 ANR8355E I/O error reading label for volume 000828 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:20:33 ANR8355E I/O error reading label for volume 002284 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:21:13 ANR8355E I/O error reading label for volume 002084 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:26:29 ANR8355E I/O error reading label for volume 001367 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:28:24 ANR8355E I/O error reading label for volume 000386 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34215) 07/04/2013 23:36:08 ANR8355E I/O error reading label for volume 001804 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34215) 07/04/2013 23:37:04 ANR8355E I/O error reading label for volume 002323 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34255) 07/04/2013 23:44:47 ANR8355E I/O error reading label for volume 001814 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:45:05 ANR8355E I/O error reading label for volume 002535 in drive DRIVE4 (mt7.0.0.1). (SESSION: 24769) Thanks best regards, Adeel Mehmood D I S C L A I M E R The information in this email and in any files transmitted with it, is intended only for the addressee and may contain confidential and/or privileged material. Access to this email by anyone else is unauthorized. If you receive this in error, please contact the sender immediately and delete the material from any computer. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is strictly prohibited. Statement and opinions expressed in this e-mail are those of the sender, and do not necessarily reflect those of the company. For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is
Re: query archive returns nothing
Also make sure that the management class to which the archive objects are bound has a sufficient retention period. - Andy Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | stor...@us.ibm.com IBM Tivoli Storage Manager links: Product support: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager Online documentation: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli Documentation Central/page/Tivoli Storage Manager Product Wiki: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Storage+Manager/page/Home ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2013-07-09 10:41:28: From: Skylar Thompson skyl...@u.washington.edu To: ADSM-L@vm.marist.edu, Date: 2013-07-09 10:48 Subject: Re: query archive returns nothing Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu One also needs to be careful about filespace boundaries - dsmc will not traverse nor even display a filespace in a lower-level directory unless its mountpoint was also backed up as a directory in that lower-level filespace. -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine On 07/08/13 15:15, Erwann Simon wrote: Geoff, Let's try with a trailing /or putting quotes around your file specification. Be careful with the shell interpreting the star and not the TSM Client. I think that a user who archives files becomes the owner of the archives and should be able to queriy them. Erwann Geoff Gill avalnch...@yahoo.com a écrit : I was wondering if perhaps this makes sense to anyone. While logged on as a user, not root, an archive is run. dsmc archive /var/log/test/* with -deletefiles. archive ran, shows 8 files archived and 5 files deleted. dsmc q archive /var/log/test/* -subdir yes, dsmc q archive /var/log/test, dsmc q archive /var/log/test -subdir=yes all return ANS1092W No files matching search criteria were found. So the question: Is it possible a user could archive files and not see anything with the query? Is it possible I have a client level problem, which I'm trying to research now. what else am I missing? I have asked them to log in as root and do the query but won't get a response till tomorrow so I thought I'd see I got any hits here. Thank You Geoff Gill
Re: TSM for SAP w/Oracle RMAN
THANKS!! Just what I needed! W -Original Message- From: Dwight Cook [mailto:coo...@cox.net] Sent: Tuesday, July 09, 2013 8:54 AM To: 'ADSM: Dist Stor Manager' Cc: Prather, Wanda Subject: RE: [ADSM-L] TSM for SAP w/Oracle RMAN Wanda, Tell them to always run with the exact same multiplexing and restore sessions as they did when backing up (match multiplexing and backup sessions) In the initSID.utl file there is also a MAXBACKSESSIONS and a MAXRESTORESESSIONS etc... your maxsessions and sessions needs to be set at the max expected to run at any given time and then your maxback and maxrestore need to be the same. If it is really really slow and running on windows, look for a nic that's out of whack... and by that I mean a duplex irregularity (full on switch and half on windows side) but you've probably already looked at that... (even now a days some 10+ years after first running into that issue I still see it happening *sigh*) Only last thing would be maxnummp of the client but that would throw an error that would be in their brrestore log when TSM didn't allow a tape mount. Hope this helps, Later, Dwight -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Monday, July 08, 2013 6:08 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM for SAP w/Oracle RMAN TSM 6.3.3 on Windows (server), TDP for SAP on Oracle 6.4, TSM client 6.4.0.0 on Linux. The Oracle DBs are compressed. OK, I'm just the back-end server support. No speakum SAP. DBA did the support to set up SAP/TDP with RMAN, I'm pretty clueless. Backups have been running beautifully, for months. Then he left, alas. Now a new different DBA is trying to get restores to run and they are slow as dirt. One obvious problem is that on backups 2 sessions run in parallel, which back up in 4 total sessions as viewed from the server side. Upon the restore they are running one at a time. I know where to find the api/bin64 directory with the appropriate dsm.sys, and I know where to find the /oracle/SID/112_64/dbs directory and look at the initSID.utl file. That file has maxsessions 2 in it. Where else should I look to see why the restore is only starting 1 session at a time? Is that something controlled via BRtools or RMAN? W Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.com ICF International | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | 410.539.1135 (o)
Re: : TSM Running out of Scratch Tapes
Hi, From the looks of it (at least) 2 drives got their windows ID changed. Check from windows end if the drive/serial/mt is still matching path defined in tsm. Also make sure persistent binding and persistent naming are turned on otherwise drives will keep on jumping all over the place. After confirming and fixing all hardware config issues tapes should be reusable again. Kind regards, Karel - Oorspronkelijk bericht - Van: Adeel Mehmood ad.mehm...@diyarme.com Verzonden: dinsdag 9 juli 2013 7:31 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: Re: [ADSM-L] : TSM Running out of Scratch Tapes Dears , We are receiving below errors and the Scratch tapes goes to ZERO 07/04/2013 22:58:44 ANR8355E I/O error reading label for volume 001736 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32773) 07/04/2013 23:04:23 ANR8355E I/O error reading label for volume 000588 in drive DRIVE4 (mt7.0.0.1). (SESSION: 32799) 07/04/2013 23:04:35 ANR8355E I/O error reading label for volume 000482 in drive DRIVE15 (mt10.0.0.2). (SESSION: 32806) 07/04/2013 23:10:55 ANR8355E I/O error reading label for volume 001058 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:11:01 ANR8355E I/O error reading label for volume 002081 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:15:49 ANR8355E I/O error reading label for volume 000468 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:16:21 ANR8355E I/O error reading label for volume 000828 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:20:33 ANR8355E I/O error reading label for volume 002284 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34242) 07/04/2013 23:21:13 ANR8355E I/O error reading label for volume 002084 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34240) 07/04/2013 23:26:29 ANR8355E I/O error reading label for volume 001367 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34255) 07/04/2013 23:28:24 ANR8355E I/O error reading label for volume 000386 in drive DRIVE4 (mt7.0.0.1). (SESSION: 34215) 07/04/2013 23:36:08 ANR8355E I/O error reading label for volume 001804 in drive DRIVE15 (mt10.0.0.2). (SESSION: 34215) 07/04/2013 23:37:04 ANR8355E I/O error reading label for volume 002323 in drive DRIV [Het originele bericht is niet volledig opgenomen]
Rename Node and Rename Filespace
I want to verify that I understand node and filespace renaming correctly: I need to rename a node that is backing up under the wrong name; Linux_SRV2 has been backing up as Linux_SRV1. Ultimately I need both SRV1 and SRV2. I don't want to lose the data already backed up when I start the actual SRV1 backing up as SRV1. I don't want to orphaned filespaces out there either, meaning that I want to avoid three sets of filespaces; New SRV1, New SRV2, and Old SRV2/1 I recall having to rename a node about 6 years ago. It was a little different, I just wanted to rename the node, I wasn't playing musical chairs with name, and it was Windows and NAS, not Linux. In that case I ended up with filespaces for the old and new client names. I think in that case, I renamed the client from the dsm.opt file (Windows) without renaming the node at the TSM server. Then backups occurred and it was too late to rename the filespaces. In reading this thread, http://adsm.org/forum/showthread.php?22687-Renaming-a-node , I see that Chad Small states that the filespaces stay with the node when it is renamed. - So...all should be well if I rename the node at the server and at the client in a timely fashion. I do not need to rename the filespaces at all. Hi to those I have annoyed in the past! George Huebschman (George H.) (301) 699-4013 (301) 875-1227 (Cell) The contents of this email are the property of PNC. If it was not addressed to you, you have no legal right to read it. If you think you received it in error, please notify the sender. Do not forward or copy without permission of the sender. This message may contain an advertisement of a product or service and thus may constitute a commercial electronic mail message under US Law. The postal address for PNC is 249 Fifth Avenue, Pittsburgh, PA 15222. If you do not wish to receive any additional advertising or promotional messages from PNC at this e-mail address, click here to unsubscribe. https://pnc.p.delivery.net/m/u/pnc/uni/p.asp By unsubscribing to this message, you will be unsubscribed from all advertising or promotional messages from PNC. Removing your e-mail address from this mailing list will not affect your subscription to alerts, e-newsletters or account servicing e-mails.
Re: Rename Node and Rename Filespace
-George Huebschman wrote: - I want to verify that I understand node and filespace renaming correctly: I need to rename a node that is backing up under the wrong name; Linux_SRV2 has been backing up as Linux_SRV1. Ultimately I need both SRV1 and SRV2. I don't want to lose the data already backed up when I start the actual SRV1 backing up as SRV1. I don't want to orphaned filespaces out there either, meaning that I want to avoid three sets of filespaces; New SRV1, New SRV2, and Old SRV2/1 I recall having to rename a node about 6 years ago. It was a little different, I just wanted to rename the node, I wasn't playing musical chairs with name, and it was Windows and NAS, not Linux. In that case I ended up with filespaces for the old and new client names. I think in that case, I renamed the client from the dsm.opt file (Windows) without renaming the node at the TSM server. Then backups occurred and it was too late to rename the filespaces. In reading this thread, http://adsm.org/forum/showthread.php?22687-Renaming-a-node , I see that Chad Small states that the filespaces stay with the node when it is renamed. - So...all should be well if I rename the node at the server and at the client in a timely fashion. I do not need to rename the filespaces at all. I have never needed to rename file spaces when renaming Unix or Linux nodes. I frequently do need to rename filespaces when renaming Windows nodes. The Windows machine name is embedded in many of the file space names. If the node name change is associated with a machine name change (the usual situation at our site) the file spaces should be renamed to match the new machine name. I have no experience with renaming NAS nodes. Thomas Denier Thomas Jefferson University Hospital
